== 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:
- **ButtonGroup**: keyboard handling satisfying – should arrow keys be considered? T314446
- **Dialog**: Are our approaches and assumptions for keyboard/AT flows correct? Originally captured in T344178
-- Add `aria-modal="true"` to the `role="dialog"` element.
-- Focus on initial dialog open should work in a predictable way.
-- Putting dialogs at end of `body` on above behalf
-- Users should not be able to interact with content behind the dialog when open.
-- Remain with `aria-hidden="true"` for its wider support than only aria-modal on background elements incl script
-- Add `inert` as future-facing attribute for non-interactable background elements as well
-- The user always has a way to exit the dialog using keyboard navigation.
- **Combobox**, **Lookup**, **Select** and **TypeaheadSearch**: keyboard handling satisfying? ARIA exposure clear?
- **Field**: Questions on the component and its various features with a variety of inputs and input groups.
-- A Field with a label, description, and help text, a single input, and error handling/error message. Does the focus handling, the keyboard handling and the markup and ARIA markup, specifically around error interaction work sufficiently?
-- A Field that's a fieldset with a radio group
-- A Field that's a fieldset with two inputs (see the examples on the Field page)
-- **Menu**: Verify our approaches T343275 & T344538 and also {T324794}
- **Tabs**:
-- Followed {key Tab} (Tab) + Arrow key [[ https://www.w3.org/WAI/ARIA/apg/patterns/tabs/#examples | best practices in APG ]]. Does this meet expectations?
Consider:
- {T140812}
- {T314446}
- {T341357}
== Acceptance criteria
[x] DST members provide feedback on this task with accessibility questions
[x] Prepare a document with the context of questions to AFB – https://docs.google.com/document/d/1IPo1E3Waph9a6OtdDKWFf3blYKmEZdUnhXNeZ8PjNtA/
[x] Submit a request to AFB for review, see also T353179