Techniques for WCAG 2.0

Skip to Content (Press Enter)


G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes


Programming technologies that have standard components programmed to interface with accessibility APIs.

This technique relates to:


The objective of this technique is to allow assistive technology to understand Web content so that it can convey equivalent information to the user through an alternate user interface.

Sometimes content is not created using markup language but rather using a programming language or tools. In many cases, these technologies have interface components that are already programmed to interface with accessibility APIs. If and author uses these components and fills in the properties (e.g. name, etc) the resulting user interface components in the content will be accessible to assistive technology.

However, if an author wants to create a user interface component that is new and they cannot use standard components, then they need to be sure to add the accessibility provisions themselves - and implement them in a way that is compatible with the accessibility API.




  1. Render content using an accessible User Agent.

  2. Use an Accessibility Tool designed for the Accessibility API of the User agent to evaluate each user interface component.

  3. Check that name and role for each user interface component is found by the tool.

  4. Change the values on the component.

  5. Check that the Accessibility tool is alerted.

Expected Results