I’m so excited to see this resource making it out into the public. Congrats to the U.S. Digital Service and 18F folks for their awesome work and for their focus on accessibility!
The Best of the Internets
An interesting proposal from LG regarding design tools for addressing non-rectangular screens.
A bit of fun, but there’s some good stuff in here. One particularly crucial fact: “Answers are often obvious in design if you are asking the right questions, but sometimes finding the question is the tricky bit.”
Fantastic post from Eric on how the mass appeal of content blockers has given the web a mulligan. There’s a lot of great content in his post, but I’ll just share this one emblematic passage:
An excellent (and exhaustive) overview of what’s new in iOS 9 as it pertains to web design.
This was a fascinating dive into console browser stats. You did know people use console browsers, right? And yes, for more than porn.
[A] revolutionary way of making websites so they look good in iOS 9 with external fonts turned off, work well for Opera Mini’s 250+ million users, and in Chrome, Opera, Firefox, IE, Edge, whether you’re using a computer, a phone, a tablet, a phablet (you’re not, are you?), with or without assistive technology.
Thank you Bruce!
I could not have said it better myself:
A successful plan for web accessibility addresses many areas of your organization and projects: training, quality assurance, recruiting, purchasing, marketing, content development, visual design, and more. As with other important aspects of website development, such as performance, accessibility is best approached as an integral and ongoing activity.
Screen reader compatibility is complex because it relies on a browser and a screen reader to work in tandem. As browsers can be combined with different screen readers, it makes testing a challenge. This matrix goes through a few key ARIA options and approaches, identifying which ones work and which ones don’t using a bunch of combinations. Narrator is sadly missing from the matrix, but this is still a useful resource that I hope continues to grow and get updated. In fact, to that end, I’d love to see it move to Github for more contributions.
This is a drum I’ve been beating for a while: Not all smartphones are created equal. You should be testing on low-spec smartphones.