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

SC4.1.2: Clarify it for designers, use plainer language #45

Open
jfhector opened this issue Oct 29, 2019 · 1 comment
Open

SC4.1.2: Clarify it for designers, use plainer language #45

jfhector opened this issue Oct 29, 2019 · 1 comment
Labels

Comments

@jfhector
Copy link
Contributor

The headline summary of this success criterion currently reads:

Name, Role and State of interactive controls: Make sure the code of each page enables assistive technologies to discover the purpose of every feature, the way that feature is identified, and the state it is currently in.

Designers rated its clarify 4/5, so it's not bad. But they also wrote "add example"?

Overall, reading that sentence again, I feel that it could be written in a clearer way.

@jfhector
Copy link
Contributor Author

jfhector commented Dec 3, 2019

Updated wording to:

Name, Role and State of interactive components: The code should enable assistive technologies to understand the name, role and state of every interactive UI component.

It remains to be seen whether this is better understood.

@jfhector jfhector added the good first issue Good for newcomers label Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant