Skip to main content
RAWeb 1.1RAAM 1.1

Compatible with assistive technologies

This term is defined by more than one standard, and the wording differs. Each definition below is the one that applies to that standard’s criteria.

Definition in RAWeb 1.1

Content or feature must be compatible with assistive technologies and with the accessibility functions of browsers and other user agents via an accessibility API.

This concerns both the technology and its features and uses:

  • The way in which web technology is used must be compatible with assistive technologies. This means that the way the technology is used has been tested for interoperability with users of assistive technologies in the language(s) of the content;
  • The technology runs natively in widely available user agents that are, themselves, compatible with accessibility (such as HTML and CSS) or with a widely available plug-in that is, itself, compatible with accessibility.

Verifying compatibility with assistive technologies requires carrying out a number of tests specific to the technology used, for example

  • Checking the name, role, value, properties and changes of state of user interface components;
  • Checking that a user interface component is correctly rendered (by assistive technologies).

Criteria in RAWeb 1.1

Definition in RAAM 1.1

Content or functionality must be compatible with assistive technologies and software accessibility features via an accessibility API.

This concerns the technology, its functions and its uses:

  • The way the technology is used must be compatible with assistive technologies. This means that the way in which the technology is used has been tested for interoperability with users of assistive technologies in the software content.
  • The technology runs natively on the platform and uses the platform's accessibility API.

Criteria in RAAM 1.1