Closed YuanboXue-Amber closed 2 weeks ago
A11y issues:
Contrast issue - sharing this issue from combobox #29367 - fixing it with #30101
Reported bug which was found during the validation:
[Bug]: [DatePicker] [A11y] grid navigation would be expected for "year" table #30036
[Bug]: [DatePicker] [A11y] combobox should be opened by down arrow key #30042
Bug 48135935 : Narrator scan mode is not turned off for the combobox
Chromium - Issue 1510855: Narrator doesn't narrate aria-describedby for combobox
[Bug]: [DatePicker] [A11y] NVDA navigates just to "clickable" in browse mode #30120
We discovered multiple issues from Combobox (base component of TimePicker) with @kolaps33:
I am observing following issues:
- VoiceOver/Safari (affected components: combobox, datePicker, timePicker) 1.1 Control+Option+Space doesn't open listbox 1.2 When navigate in the listbox with up/down arrows, then VoiceOver is silent. No narration. Looks like serious.
Both these issues above are fine with Chrome.- Android/Talkback/Chrome (affected components: combobox, datePicker, timePicker) Combobox was opened fine from the button next to input. But then, I was not able to navigate through the listbox. Not sure I am missing here maybe some basic navigation pattern? because even on the APG pattern it behaves similarly.
- Chrome/Narrator (affected components: datePicker) When user navigate to the row, then it start to narrates the row from the beginning instead of the current gridcell. Attaching screenshot (in this case instead of narration 29 it narrated all numbers in the is row, started with 24):
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
This accessibility review checklist is primarily geared towards evaluating the accessibility of new components, or major design changes or new features in existing components. Detailed steps are included in the section for each high-level item. Skip any tests or sub-tests that you do not feel comfortable evaluating, and either pair with or hand off the issue to an accessibility SME for any remaining items.
@YuanboXue-Amber :
@kolaps33:
Testing Notes
For each component tested, write out any specific notes per-step here. Use this section to communicate any non-standard approaches, ambiguous test results, or fully skipped sections.
Color contrast
Steps
Checks
References
High Contrast Mode
Steps
Checks
References
Zoom and Reflow
Steps
Checks
References
Pointer access
Steps
Checks
If a touchscreen isn't available, use common sense/maybe devtools? to mimic a lack of hover.
Note -- this is not only about touch access. A number of assistive tech devices function like a pointer, but lack hover (e.g. eye control or switch control).
Keyboard access
Steps
Checks
<span tabindex="0">some text</span>
should not have a tabindex and should not get focus, even if it has a tooltip or a click event (that would be a separate issue).References
Code conformance
Steps
Checks
To check for valid semantics, look at the following:
role=""
attribute, or implicit based on the HTML element)To check for visually-hidden text:
aria-label
s set within the component code, and any freeform string props that do not visually show uparia-label
or other native attribute.References
Screen reader access
Screen reader combinations:
Steps
For Windows screen readers:
For VoiceOver on macOS:
Touch screen readers:
Checks
For all screen readers, within all screen-reader-specific tests, check the following:
Specific per-screen-reader checks:
References
This test requires a broad knowledge of screen readers; specific references won't be too helpful. This should generally be done with or by someone who is confident in using and interpreting screen readers.