search

theappbusiness / accessibility-guidelines

Plain language summary of the Web Content Accessibility Guidelines
https://theappbusiness.github.io/accessibility-guidelines/
MIT License
47 stars 9 forks source link

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

Open jfhector opened 4 years ago

jfhector commented 4 years ago

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 commented 4 years ago

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.