21–23 of 23 posts
[1] [shameless self-promotion] http://jakub-g.github.com/accessibility/onclick/ - comprehensive cross-browser study of 'onclick' handling from JavaScript
Earlier quoted context omitted.
Not really misleading: most screen readers aren't yet using the HTML5 Document Outline algorithm, so for accessibility you still have to rely on proper h1-6. Ideally, you'd use them in combination for future proofing. It takes a little work, but you can arrive at the same general outline from both algorithms, since the new one ignores the ordinality of the h tag.
Screen readers will use whatever document outline that the browser renders, no?
The mention of Fangs alone made this article valuable to me. Accessibility has had lots of lip service for years but it is essentially impossible to do any legitimate work optimizing for screen readers if you don't have access to them (being prohibitively expensive.) It's like writing for a browser you never get to test in. If anyone was serious about accessibility they should get simply get screen readers in the han…