Revise understanding for SC 3.2.4 Consistent Identification - #5251
Revise understanding for SC 3.2.4 Consistent Identification#5251giacomo-petri wants to merge 17 commits into
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Nice work @giacomo-petri ... I'll spend some time giving this a once-over before moving it to drafted |
patrickhlauke
left a comment
There was a problem hiding this comment.
This is very nicely done. A big cleanup of a previously quite muddled/handwavy understanding document. There's a few tweaks I'd suggest, but overall this looks very solid.
| In contrast, recurring components such as global navigation links, search controls, account controls, | ||
| or footer links are encountered repeatedly across a set of web pages and are the types of components for which consistent identification most directly supports user recognition.</p> | ||
| <p>Users often rely on consistent identification to predict the purpose of interface components. | ||
| For example, people who use screen readers frequently navigate websites by recognizing familiar controls announced by assistive technologies, |
There was a problem hiding this comment.
| For example, people who use screen readers frequently navigate websites by recognizing familiar controls announced by assistive technologies, | |
| For example, people who use screen readers frequently navigate websites by recognizing familiar controls (as announced by assistive technologies), |
There was a problem hiding this comment.
I don't think this changes much. I personally prefer the original version without the parentheses
|
i believe the merge conflict was caused by 6e8bd03 - but as this completely rewrites all examples anyway, it can be resolved just by overwriting that whole section with what's in the PR here. |
|
Nice work! But what about #1778 ? |
Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>
Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>
Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>
Co-authored-by: Baldino Morelli <baldino.morelli@usablenet.com>
Co-authored-by: Baldino Morelli <baldino.morelli@usablenet.com>
Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>
Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>
Co-authored-by: Baldino Morelli <baldino.morelli@usablenet.com>
Co-authored-by: Adam Page <adamfpage@gmail.com>
|
Discussed on previous calls and finalized on 21 August Backlog call. |
This PR substantially revises the understanding doc of SC 3.2.4 Consistent Identification to improve clarity and reduce common ambiguities in the interpretation of the SC.
Closes:
Note: the changes are editorial only and do not modify the normative meaning of SC 3.2.4. Instead, they aim to remove significant ambiguities in the current understanding doc, including examples that can be interpreted as contradictory or that blur the intended scope of the SC.
Main changes
The goal of these changes is to make the understanding doc more closely reflect the wording and intent of SC 3.2.4 while providing clearer guidance for authors, auditors and implementers.
Preview: https://deploy-preview-5251--wcag2.netlify.app/understanding/consistent-identification
Diff: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FWAI%2FWCAG22%2FUnderstanding%2Fconsistent-identification.html&doc2=https%3A%2F%2Fdeploy-preview-5251--wcag2.netlify.app%2Funderstanding%2Fconsistent-identification