The enabled accessibility panel looks like so: The Accessibility Inspector also uses this information to provide valuable accessibility debugging capabilities in the DevTools. This is a bit like the DOM tree, except that it contains a more limited set of elements and slightly different information about them.Īssistive technologies like screenreaders use this information to find out what’s on a web page, tell their users what’s there, and enable them to interact with the page. Roles and other information exposed by browser accessibility APIs are presented in a hierarchical structure called the accessibility tree.
In such a situation, you can use WAI-ARIA role attributes to provide your own roles. Sometimes, however, you need to use some non-semantic markup (e.g., div s) to build a complex custom control, and the control won’t have a default role that reflects its purpose. Semantic DOM elements have roles assigned to them by default that hint at what their purpose is. Here we are mainly talking about exposing information to people with visual disabilities - this is done via the accessibility APIs available inside web browsers, which expose information on what roles the different elements on your page play (e.g., are they just text, or are they buttons, links, form elements, etc.?). You can find more extensive information in the Accessibility section of MDN Web Docs. This means trying your best to not lock anyone out of accessing information because of any disability they may have, or any other personal circumstances such as the device they are using, the speed of their network connection, or their geographic location or locale. Getting Set Up To Work On The Firefox CodebaseĪccessibility is the practice of making your websites usable by as many people as possible.
0 kommentar(er)
