RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://a11ysupport.io/tech/aria/menu_role below:

menu_role (aria) | Accessibility Support

menu role (aria)

Screen Reader support level: partial (28/33)

On this page

About this feature

A type of widget that offers a list of choices to the user.

Age of results

Results across all tests for this feature range from 4 years ago to 5 years ago. Detailed dates and version information can be found in associated tests.

Caution

Failing or partial results may be out of date. The oldest result is from 4 years ago. Consider running the associated tests and contributing results.

Expectations

What are expectations?

Screen Reader support by expectation Expectation JAWS Narrator NVDA Orca TalkBack VoiceOver (iOS) VoiceOver (macOS) Chrome Edge Firefox Edge Chrome Edge Firefox Firefox Chrome Safari Safari MUST convey its role supported supported supported supported supported supported supported supported supported none supported MUST convey the name if named supported supported supported supported none none supported supported supported none none MUST convey the boundaries of the menu supported supported supported supported supported supported supported supported supported supported supported Expectation: convey its role Rationale:

A screen reader user needs to be aware that elements are within a menu

Strength of this expectation for different types of assistive technologies:

Screen Readers: MUST
Voice Control: NA

Examples:

Some screen readers will explicitly convey the menu role as something like "<name> menu"
The role may be implied by the presence of menuitem children

Expectation: convey the name if named Rationale:

A screen reader user needs to be aware of the name of menu

Strength of this expectation for different types of assistive technologies:

Screen Readers: MUST
Voice Control: NA

Examples:

The accessible name of the menu is announced when entering the menu.

Expectation: convey the boundaries of the menu Rationale:

A screen reader user needs to be aware when they enter and exit a menu

Strength of this expectation for different types of assistive technologies:

Screen Readers: MUST
Voice Control: NA

Examples:

Boundaries may be implied by posinset information
Boundaries may be implied by no longer conveying the menu item role (if the role is explicitly conveyed)
Boundaries may be implied by looping back to the top of the menu
Boundaries may be explicitly conveyed by announcing something like "<name> menu" when entering and "exiting menu" when leaving

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4