Flutter Web: aria-controls must be an available property on all component types (Accessibility) #162125
Description
Use case
The WAI-ARIA property aria-controls must be available on all Flutter component types/widgets to identify the element (or elements) whose contents or presence are controlled by the current element.
Proposal
Add the WAI-ARIA property aria-controls to the list of semantics flags on all Flutter component types/widgets. Its value must be the ID of the element on the page that it controls. Multiple ID's can be listed (each separated by a single space).
Examples:
aria-controls="panel1"
aria-controls="panel1 panel2 panel3"
Metadata
Metadata
Assignees
Labels
High-priority issues at the top of the work listAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)Nothing broken; request for a new capabilityA detailed proposal for a change to FlutterWeb applications specificallyIssue is closed as already fixed in a newer versionOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)Triaged by Framework Accessibility team
Type
Projects
Status