ARIA and UI Automation in Microsoft Edge

The W3C defines Accessible Rich Internet Applications (ARIA) as a syntax for making dynamic web content and custom UI accessible. Microsoft Edge recognizes the ARIA role, state, and property information and exposes it to assistive technologies, which in turn can use the Microsoft UI Automation APIs to retrieve the information.

Visit HTML5Accessibility for information on which new HTML5 features are accessibly supported by Microsoft Edge.

The Microsoft Edge rendering engine (EdgeHTML) builds an accessible projection of web pages, conforming to the following W3C specifications:

  1. The HTML Accessibility API Mappings specification defines how HTML elements and attributes map to ARIA and UI Automation objects.

    • Working draft - stable version of the specification
    • Editor’s draft - work in progress. Note that while this spec has the latest changes, the changes may not be available in Microsoft Edge yet.
  2. The Core Accessibility API Mappings specification defines general principles for building the accessibility tree and mapping ARIA elements and attributes to UI Automation objects.

    • Working draft - stable version of the specification
    • Editor’s draft - work in progress. Note that while this spec has the latest changes, the changes may not be available in Microsoft Edge yet.
  3. The Accessible Name and Description: Computation and API Mappings specification defines how to compute the name and description of accessible objects given the HTML and the ARIA elements and attributes values available for the accessible elements.

    • Working draft - stable version of the specification
    • Editor’s draft - work in progress. Note that while this spec has the latest changes, the changes may not be available in Microsoft Edge yet.

For more information about the accessibility architecture in Microsoft Edge, check out the Building a more accessible web platform blog post. For examples of how the new architecture improves the end user’s experience, and specifically how markup defines the experience of navigating with assistive technologies like screen readers, visit Building a more accessible user experience with HTML5 and UIA.