Tags: screenreaders

18

sparkline

Software development 450 words per minute - Vincit

Tuukka Ojala is a programmer working on the web. He’s also blind. Here are the tools of his trade.

Results of the 2016 GOV.UK assistive technology survey | Accessibility

The Government Digital Service have published the results of their assistive technology survey, which makes a nice companion piece to Heydon’s survey. It’s worth noting that the most common assistive technology isn’t screen readers; it’s screen magnifiers. See also this Guardian article on the prevalence of partial blindness:

Of all those registered blind or partially sighted, 93% retain some useful vision – often enough to read a book or watch a film. But this can lead to misunderstanding and confusion

bitsofcode | Tools for Developing Accessible Websites

Ire rounds up a bunch of tools you can use to test accessibility, from dev tools to Tenon.

Aria-Controls is Poop | HeydonWorks

I wrote a while back about how I switched from using a button to using a link for progressive disclosure patterns. That looks like it was a good move—if I use a button, I’d need to use aria-controls and, as Heydon outlines here, the screen reader support is pants.

Aesthetics of the invisible | Francesco Schwarz

Hidden little details that make a big difference for screen readers.

A website is only as beautiful as the underlying markup.

Aural UI of HTML elements

This is such an incredibly useful resource by Steve and Léonie: documenting how multiple screen readers handle each and every element in HTML.

It’s a work in progress, but it’s definitely one to remember the next time you’re thinking “I wonder how screen readers treat this markup…”

The Tink Tank » Understanding screen reader interaction modes

Léonie gives a great, clear description of how screen readers switch modes as they traverse the DOM snapshot.

Advancements in the accessibility of Facebook on Marco’s accessibility blog

It’s great to see the changes that Facebook’s four-person accessibility team have managed to push through.

HTML5 semantics and accessibility | The Paciello Group Blog

This is a great response to my recent post about semantics in HTML. Steve explores the accessibility implications. I heartily concur with his rallying cry at the end:

Get involved!

Accessibility and HTML5 Block Links — Simply Accessible

Derek runs some tests on how screenreaders behave when block-level elements are wrapped in links, which is now legal in HTML5.

HTML5, ARIA Roles, and Screen Readers in May 2010 — Research — Accessible Culture

Test results for screen readers navigating content that uses new HTML5 elements and ARIA roles.

WebAIM: Screen Reader User Survey Results

The results of the second screen reader survey from WebAIM are, once again, required reading.

WebAIM: Screen Reader Survey Results

This list of screenreader survey results is required reading. Conclusion: "there is no typical screen reader user."

Using WAI ARIA Landmark Roles - The Paciello Group Blog

A guide to using ARIA roles from the mighty Steve Faulkner.

northtemple - JavaScript and screen readers

An in-depth look at the intersection of JavaScript and screen readers, concentrating on events in particular.

AJAX and Screen Readers - Content Access Issues - The Paciello Group Blog

Steve Faulkner gives a rundown of the current state of play between screen readers and Ajax.

Empty Links and Screen Readers » Yahoo! User Interface Blog

Excellent research into how screen readers respond to empty links (i.e. A elements with no text between the opening and closing tags).

18 Questions for Niqui Merret and Aral Balkan on Flash and Accessibility - Wait till I come!

Christian talks to Aral and Niqui about Flash and accessibility.