In WAI-ARIA 1.1, the aria-roledescription attribute has been added to give web authors the ability to further describe the function of a widget. Here are a few tips for usage.
In recent months, I have discovered a tendency within myself that longs for more focused, hassle-free environments or niches, where distractions are reduced to a minimum, and I can immerse myself in one thing, and one thing only. And that has lead to rediscovering the merits of some blindness-specific products.
The built-in Firefox Developer Tools just received a new family member. The Accessibility Inspector allows you to inspect your website’s exposure to assistive technologies.
For the past 18 years, screen readers on Windows have had a particular way of presenting web content to their users. This model no longer scopes well in light of modern web applications and dynamically changing web sites. The model, therefore, needs to be reimagined and modernized.<!— more —>
As you may or may not have heard, Firefox 49 supports the HTML5 <details> and <summary> elements. Both full keyboard support and support for assistive technologies is also available right from the start.
A few months ago, I wrote about the efforts to make the built-in Firefox developer tools more accessible. That work started in January and is now carrying first far-reaching fruits. Here’s an update!
On March 29, 2016, Twitter announced that description of images is now available when tweeting photos. This helps first and foremost the blind and visually impaired who cannot see images, but may also help people with certain cognitive disabilities who cannot interpret photos, but can make use of descriptions. Here’s how describing your tweeted images works!
Have you also noticed an increased buzz around Microsoft’s accessibility efforts lately? You probably have if you, like me, are on Twitter and other social media channels and are following the MSFTEnable Twitter account. But in case you haven’t, here are some exciting pointers for you to keep an eye on.
In the first quarter of 2016, Yura, who is part of the accessibility team at Mozilla, and I are starting on a journey to make the firefox developer tools accessible. The majority of the tools are currently a very mouse-driven environment, and our goal is to make them equally accessible for keyboard users and those using assistive technologies such as screen readers. This blog post marks the beginning of that journey.