Accessibility/WebAccessibilityAPI: Difference between revisions

There's number of objectives on the web to improve accessibility and usability support. The web applications want to provide special support for their users, helping them navigate and perceive the content. The browser has number of add-ons serving to improve accessibility support, for example, the app letting to navigate landmarks on the web page. These tasks requires accessibility API similar to what desktop assistive technologies have.

Also web accessibility API allows in-browser automated accessibility testing of web content, i.e. helpful to check HTML and other standards in the browser is accessible to all users.

On the another hand there's growing need of making graphical content accessible. These are charts, graphs and other various visual stuff that are drawn by HTML canvas or SVG. Also there's tendency to use HTML canvas element in place of DOM because of performance matter, here's an [http://engineering.flipboard.com/2015/02/mobile-web/ example]. They used to define all markup right in JavaScript and they need non-DOM accessibility solution to make the content accessible.