Accessibility overview

"The impact of disability is radically changed on the Web because the Web removes barriers to communication and interaction that many people face in the physical world." - W3C Standards for Web Design and Applications: Accessibility

The World Health Organization defines disability as "a mismatch in interaction between the features of a person's body and the features of the environment in which they live". Disabilities range from situational disabilities, like limited mobility while holding a baby or bright sunlight on a phone, to other physical, auditory, visual, or age-related impairments.

Designing websites and other technologies for inclusion creates an experience enjoyable by every person. Inclusive design and web accessibility empowers and assists everyone to use the web.

Here are some best practices, code samples, and further resources for you to learn more about Designing, Building, and Testing accessible websites in Microsoft Edge.

Accessibility in Microsoft Edge

In Microsoft Edge, we introduced the UI Automation API (UIA API). This change to UI automation was a major investment in browser accessibility. The UI Automation API lays the foundation for a more inclusive web experience for users who depend on assistive technology in Windows 10 or later.

The Microsoft UI Automation API is an accessibility framework that enables Windows applications to provide and consume programmatic information about user interfaces (UIs). It provides programmatic access to most UI elements on the desktop. It enables assistive technology products, such as screen readers, to provide information about the UI to end users and to manipulate the UI by means other than standard input. UI Automation also allows automated test scripts to interact with the UI.

The Microsoft Windows UI Automation blog has posts about the Windows Automation API.

The accessibility system in Microsoft Edge inherently supports modern web standards including ARIA, HTML5, and CSS3. The following diagram of the simplified browser pipeline follows webpage content into an accessible presentation layer.

Content transformed to the engine model is projected into visual and accessibility views that are presented either as visual or accessible presentation

The Microsoft Edge team works with the W3C and other browser vendors on an ongoing basis to ensure that new web platform features have sufficient built-in accessibility.

For information on which new HTML features are accessibly supported by Microsoft Edge, navigate to HTML5Accessibility.

See also

W3C articles: