Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify title of Failure F108 #1211

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

detlevhfischer
Copy link
Contributor

@detlevhfischer detlevhfischer commented Jul 14, 2020

The title "Failure of Success Criterion 2.5.X Dragging due to not providing a single pointer method for the user to operate a function that does not require a dragging movement" is ambiguous since the last part, "that does not require a dragging movement" invites the interpretation that the single pointer operation alternative has to be provided for a function that does not use dragging - which is clearly nonsense.

Simplest solution: Delete "that does not require a dragging movement".

Base automatically changed from master to main March 5, 2021 20:42
@gundulaniemann
Copy link

What about "Failure of Success Criterion 2.5.X Dragging due to not providing an alternative single pointer method for the user to operate a function" ?

@kfranqueiro
Copy link
Contributor

We should also update the same wording in the h1 element in the same file

@bruce-usab
Copy link
Contributor

Discussed on call `11/25, worth incorporating. Question about Title versus H1 in build process.

@kfranqueiro
Copy link
Contributor

kfranqueiro commented Oct 25, 2024

Discussed on call `11/25, worth incorporating. Question about Title versus H1 in build process.

The build process synchronizes the h1 and title, but does so based on the h1 element rather than the title, so updating the h1 is actually even more important.

(What technically happens is technique information is parsed from the HTML files, with the title sourced from the h1 element; then when output files are built, both the title and h1 elements use this information)

The title "Failure of Success Criterion 2.5.X Dragging due to not providing a single pointer method for the user to operate a function that does not require a dragging movement" was ambiguous since the last part, " that does not require a dragging movement" invites the interpretation that the single pointer operation alternative has to be provided for a function that does not use dragging - which is clearly nonsense.
Copy link

netlify bot commented Oct 25, 2024

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 8c1831f
🔍 Latest deploy log https://app.netlify.com/sites/wcag2/deploys/672e370ccac9fd0008440f91
😎 Deploy Preview https://deploy-preview-1211--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@kfranqueiro
Copy link
Contributor

kfranqueiro commented Oct 25, 2024

I have rebased the branch to synchronize it with main, and have also changed the h1 to match. Note that subsequent to this PR, the title of this technique had been updated from "2.5.X Dragging" to "2.5.7 Dragging Movements"; that change is retained.

Gundula's suggestion of possibly adding "alternative" before "single pointer method" is still open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants