-
Notifications
You must be signed in to change notification settings - Fork 28
November 14, 2024 Agenda
- Requests for changes to agenda?
- Next Community Group Meeting: Wednesday November 20
- No meeting Thursday November 28
- Next AT Driver Subgroup meeting: Monday December 9
Goals:
- 6 recommended plans by September 30.
- Total of 10 Recommended + 10 in Candidate Review by December 31.
Status: Behind schedule
| Plan | Vispero | Apple |
|---|---|---|
| Alert | Approved | In Review |
| Action Menu Button Example Using aria-activedescendant | In Review | In Review |
| Color Viewer Slider | in review | Not started |
| Command Button | Approved | In review |
| Link Example 1 (span element with text content) | Approved | In review |
| Modal Dialog | Approved | Not started |
| Radio Group Example Using aria-activedescendant | in Review | Not started |
| Toggle Button | approved | In review |
- Disclosure Navigation Menu Example
- Navigation Menu Button
- Action Menu Button Example Using element.focus
Impact of hint text/help messages on test results · Issue #365 · w3c/aria-at
Proposal for discussion (included as comment in issue):
Hint: Supplemental output provided by a screen reader that is intended to help users understand an element or how to use it. Hints are distinct from base output that includes required information, such as name, role, value, state, and properties. Hints may repeat information that is included in base output. hints that are conveyed with speech are spoken after base output.
Why AARIA-AT does not test hints, i.e., test assertions do not apply to hints?
- Hints are supplemental output. While it is very important that hints do not interfere with interoperability, hints are not essential functionality. The scope of ARIA-AT is limited to fostering interoperability of essential functionality.
- Because users of certain screen readers commonly disable hints, base output must satisfy interoperability requirements. If a hint could satisfy an interoperability requirement, hints would have to be consider essential instead of supplemental.
why leave hints on during testing?
- Testing with default settings is an important principle.
- It is important to capture negative side effects caused by hints, e.g., a hint conflicts with base output.
testing requirements:
- Because hints are sometimes part of an AT response, they are included in the AT response recorded for a command. The goal is for response collection to be comprehensive; it must include both positive and negative side effects of the command. Good hints an be considered a positive side effect while inaccurate hints can be considered a negative side effect.
- Hint output is not analyzed to determine an assertion verdict. Thus, testers must have the skills and knowledge necessary to distinguish hints from base output.
Test plan for Action Menu Button Example Using element.focus
Test plan for Disclosure Navigation Menu Example
Issues to resolve:
- Conflicts in Disclosure Navigation Menu Example V24.10.10 | ARIA-AT
- Conflicting results for test 11 "Navigate to an expanded disclosure button from a link in the associated dropdown" (Disclosure Navigation Menu Example, V24.07.31) · Issue #1100 · w3c/aria-at
- Conflicting VoiceOver results for test 12 "Navigate from a collapsed disclosure button to a link in a dropdown" (Disclosure Navigation Menu Example, V24.08.12) · Issue #1116 · w3c/aria-at
- Conflicting results for test 15 "Activate a link in a dropdown" (Disclosure Navigation Menu Example, V24.07.31) · Issue #1101 · w3c/aria-at
Test Plan for Navigation Menu Button
Issues to resolve: