A RetroSearch Logo

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

Search Query:

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

aria-controls_attribute (aria) | Accessibility Support

aria-controls attribute (aria)

Screen Reader support level: partial (10/42)

On this page About this feature

Identifies the element (or elements) whose contents or presence are controlled by the current element. See related aria-owns.

Age of results

Results across all tests for this feature range from 2 years ago to 6 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 6 years ago. Consider running the associated tests and contributing results.

Expectations

What are expectations?

Important: The aria-controls attribute has expectations that are not directly testable by end users. Continue to use it if it is required by the specification, even if user-facing expectation support is poor. For more information, see FAQ: What about expectations that are not directly testable by users?.

Screen Reader support by expectation Expectation: convey the presence of the aria-controls attribute Rationale:

Users need to be aware that an element has aria-controls functionality. If the presence of the attribute is not explicitly conveyed, then users may not be aware of the functionality. However, some screen readers may choose to not convey the presence by default since the controlled element is usually directly after the controlling element in the reading order and easily findable. In these situations, explicitly conveying the presence could be unnecessarily verbose.

Strength of this expectation for different types of assistive technologies: Notes:

This is not a MUST requirement, because the functionality could still be discoverable via the screen reader's command to jump to the controlled element. If the command fails, the attribute is not present.

Examples: Expectation: allow the user to jump to the controlled element Rationale:

The controlled element might not be close to the element with aria-controls and the user might find it convenient to jump directly to the controlled element.

Strength of this expectation for different types of assistive technologies:

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