Simple recommendations for more obvious form fields.
The Best of the Internets
This is an excellent collection of accessible widgets. You can learn a lot from this code.
“All caps” text gets abused pretty regularly. This article gets into the details of why proper letter spacing is crucial for the legibility of text in all caps.
I’m so incredibly excited about this! Highlights:
- The accessibility tree is no longer a subtree of the DOM;
- ARIA Landmarks and document structure navigation;
- Proper computing of accessible name & description;
- Improved error validity states;
select, and improvements to all list type elements;
- Keyboard controls for the number field;
- Improved high contrast mode (no more removing background images, instead, the image stays and a solid color is placed behind the text);
- Speech synthesis API;
- An improved caret on Windows Phone when using an external keyboard; and
- So much more.
Couple this with the F12 dev tools enhancements and Narrator’s Developer Mode and it’s pretty clear how committed Microsoft is to accessibility. I’m so glad I work here!
This post has so much gold. To wit:
While they are very important for testing, screen readers are not testing tools. To be honest, people with disabilities are not running around with AT checking to make sure websites and software work correctly. They’re using it as a means to overcome a technological barrier that would normally keep them from doing something you and I take for granted.
Oh, the number of times I’ve had to fight this battle…
This is a pretty sweet guide to authoring accessible SVG icons. Thanks Hugo!
This is a handy cheet sheet from Léonie Watson.
I’ve said it before and I’ll say it again: Every experience is a conversation and those who design for that now will be well-positioned to succeed in the future of “headless UIs”.