ARIA, the good parts
The slides from Hidde’s presentation at Paris Web—a great overview of using and misusing ARIA.
There is a doctype for HTML4 + ARIA but "This DTD is made available only as a bridging solution for applications requiring DTD validation but not using HTML 5."
The slides from Hidde’s presentation at Paris Web—a great overview of using and misusing ARIA.
A demonstration of how even reinventing a relatively simple wheel takes way more effort than it’s worth when you could just use what the brower gives you for free.
On the surface this is about the pros and cons of minting a new HTML search
element to replace div role="search"
but there’s a deeper point which is that, while ARIA exists to the plug the gaps in HTML, the long-term goal is to have no gaps.
ARIA is not meant to replace HTML. If anything, the need to use ARIA as ‘polyfill’ for HTML semantics could be considered as a sign and a constant reminder of the fact that HTML falls short on some semantics that benefit users of assistive technologies.
A good tutorial on making password fields accessible when you’ve got the option to show and hide the input.
I really like the approach that Carie takes here. Instead of pointing to specific patterns to use, she provides a framework for evaluating technology. Solutions come and go but this kind of critical thinking is a long-lasting skill.
Do websites need to sound the same in every screen reader?
Abstracting common interaction patterns as a starting point for accessible components.
The latest installment in the long tradition of calling for this pseudo-element.
Two accessibility alternatives.
A look at some of the accessibility options.