As web developers, a large part of what we can do to improve the accessibility of our sites and apps, is in markup. In this talk, you’ll learn how the markup we write impacts the Document Object Model (DOM) and Accessibility APIs. We’ll look at specific examples and how to optimise them for end users. Lastly, we’ll peak into upcoming changes: how will the Accessibility Object Model (AOM) help us in the future?
Léonie shows how titles, landmark regions and headings make it easier for her to browse the web
Issue for creating relationships without IDREFs in HTML Spec
Alex Russell’s introduction to the idea of Web Components at Fronteers 2011.
At Sanity we want to make content easier to work with for content creators, developers and, ultimately businesses… so that they can have more remarkable experiences.
WebAIM’s research that showed 59% of websites they checked had unlabeled form elements
My notes on linking to translations
Video in which Rob Dodson and Domenic Mizzoni show what’s new in web accessibility.
HTMHell collects examples of how not to use HTML
The spec that defines how accessible names are computed
The Headings component in Tenon UI’s accessible pattern library lets you automatically have the right heading hierarchy.
Which includes stats on browser support
In which Brian Kardell takes a look at HTTPArchive data, specifically ‘dasherised’ elements. One of his findings: most custom elements are advertising related.
More on why heading structures could be seen as tables of contents
Bruce Lawson’s presentation on the AOM, from which I took this excellent advice: “built-in beats bolt-on”
It’s very cool that Web Components let us create our own custom things, but often we can actually reuse existing elements, so that we can benefit from existing semantics.
An explanation of the Accessibility Object Model on my blog