//Note, this is still a placeholder task, will be refined.//
== Background
While we've been putting years of learning from components in production (#OOUI), user feedback on large scale and newest best-practices ([[ https://www.w3.org/WAI/ARIA/apg/patterns/ | ARIA Authoring Practices Guide ]], short APG) into place for Codex components development, there are a small number of vague corners that would benefit from real-user testing on our newer component suite.
== Goal
Evaluate these areas with help of American Foundation for the Blind (AFB).
We are not only interested in technical implementation details, but also in user flow for people with different assistive technology (e.g. keyboard flow, verbosity in screenreaders…) to optimize their experience.
=== Components in question
Must-haves for a consultation:
- Dialog
- ButtonGroup: keyboard handling satisfying – should arrow keys be considered? T314446
- Select: keyboard handling satisfying? ARIA exposure clear?
-- Verify our Menu approaches T343275 & T344538 and also {T324794}
Consider:
- {T140812}
- {T314446}
- {T341357}
== Acceptance criteria
[] Prepare a document with the context of questions to AFB
[] Put outcomes into existing or new tasks