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

Clarification requested for 3.2.4 Consistent Identification #4216

Open
jamieherrera opened this issue Feb 6, 2025 · 2 comments
Open

Clarification requested for 3.2.4 Consistent Identification #4216

jamieherrera opened this issue Feb 6, 2025 · 2 comments

Comments

@jamieherrera
Copy link

Please confirm, Is 3.2.4 intended to be specifically about consistent identification for screen reader users and the non-visual experience, or also include the visual experience of functional components?

Much of the language of the Understanding Document linked below, including Examples and Sufficient Techniques, center around the accessible name and text alternatives. The In Brief section, however, and the Predictive Guideline this SC, more broadly provide examples of where this guideline and what "consistent" means in a broader sense, could apply to people with cognitive, low vision, and motor disabilities.

I do see that the first paragraph of the Intent section includes cognitive and screen reader considerations, but would suggest to include more language in the Understanding document to support this messaging.

3.2.4 Consistent Identification:

Components that have the same functionality within a set of Web pages are identified consistently.

@A11yTea
Copy link

A11yTea commented Feb 7, 2025

I think their use of the word "label" implies the visual label because in this phrase: "If identical functions have different labels (or, more generally, a different accessible name) on different Web pages, the site will be considerably more difficult to use." They go broader "more generally a different accessible name".

And their example: "Example 7: Example of a Failure
A submit "search" button on one Web page and a "find" button on another Web page both have a field to enter a term and list topics in the Web site related to the term submitted. In this case, the buttons have the same functionality but are not labeled consistently." is about the visual label.

I think the word to focus on for this criteria is the word "identified". So start with how a component is "identified" and then check if its consistent.

@JAWS-test
Copy link

I have always understood the SC to mean both the visual labeling and the programmatic labeling (accessible name).

Incidentally, I think the phrase “more generally” is wrong in the sentence:

If identical functions have different labels (or, more generally, a different accessible name) on different Web pages

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

No branches or pull requests

3 participants