Skip to content

Flutter Web: aria-describedby must be an available property on all component types (Accessibility) #162140

@jcollins-disney

Description

@jcollins-disney

Use case

The WAI-ARIA property aria-describedby must be available on all Flutter component types/widgets to provide more information about an element that the user might need.

Proposal

Add the WAI-ARIA property aria-describedby to the list of semantics flags on all Flutter component types/widgets. Its value must only be the ID of another text string element on the page (text strings are not a valid value for aria-describedby). Multiple ID's can be listed (each separated by a single space) in order to form a single accessible description.

Examples:

aria-describedby="text1"
aria-describedby="text1 text2 text3"

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work lista: accessibilityAccessibility, e.g. VoiceOver or TalkBack. (aka a11y)c: new featureNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to Fluttercustomer: castawayplatform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-accessibilityOwned by Framework Accessibility team (i.e. responsible for accessibility code in flutter/flutter)triaged-accessibilityTriaged by Framework Accessibility teamworkaround availableThere is a workaround available to overcome the issue

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions