Skip to content

Flutter Web: Landmark roles are required to identify regions of a page (Accessibility) #162138

@jcollins-disney

Description

@jcollins-disney

Use case

WAI-ARIA landmark roles provide a powerful way to identify the organization and structure of a web page. By classifying and labelling sections of a page, they enable structural information that is conveyed visually through layout to be represented programmatically. Screen readers exploit landmark roles to provide keyboard navigation to important sections of a page. Landmark regions can also be used as targets for "skip links" and by browser extensions to enhanced keyboard navigation.

Proposal

Add the following landmark roles to the the available semantics roles in existing widget libraries:

  • banner (when in context of the body element)
  • complementary
  • contentinfo (when in context of the body element)
  • main
  • navigation
  • region (when it has an accessible name using aria-labelledby or aria-label)
  • sectionhead

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projecta: 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 team

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions