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

How do we want to make decisions about the acceptability of screen reader output discoverable? #647

Open
mcking65 opened this issue Mar 17, 2022 · 0 comments
Assignees
Labels
Agenda+App Development For discussion during the next teleconference related to development of the ARIA-AT App documentation Related to documentation about the ARIA-AT project or its deliverables process Related to processes for governing and managing the ARIA-AT project question Further information is requested

Comments

@mcking65
Copy link
Contributor

In issue #638 , we decided:

On today's call we agreed that NVDA announcing "List" was acceptable for the assertion "Role of the popup ('listbox') is conveyed".

The test report is the "official record" that that NVDA output of "list" appropriately conveys the role listbox. We use the word convey in assertions intentionally to help people understand that the screen reader doesn't necessarily have to parrot the technical names of roles and properties. They can do translation and simplification as long as they consistently convey the meaning.

Do we need to make it easy to review and share specific decisions about the acceptability of such translation? If so, how might we do this? Maintain a dictionary of them? Make the issues where such decisions are made easily findable?

Another example ... -when does not saying "selected" convey the state selected?

@mcking65 mcking65 added question Further information is requested documentation Related to documentation about the ARIA-AT project or its deliverables process Related to processes for governing and managing the ARIA-AT project Agenda+App Development For discussion during the next teleconference related to development of the ARIA-AT App labels Mar 17, 2022
@mcking65 mcking65 self-assigned this Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agenda+App Development For discussion during the next teleconference related to development of the ARIA-AT App documentation Related to documentation about the ARIA-AT project or its deliverables process Related to processes for governing and managing the ARIA-AT project question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant