chore: Field accessibility review #26604
Labels
Component: Field
Fluent UI react-components (v9)
Resolution: Soft Close
Soft closing inactive issues over a certain period
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.
Testing Notes
Issues found
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.
The text was updated successfully, but these errors were encountered: