It is not uncommon for someone to message, call, email, or carrier pigeon me to ask if something is accessible. They almost invariably want a “yes” or “no.” However, I need to understand what the heck they mean and what the other-heck prompted them to ask. Yes, I would be…
Nine things automated accessibility tests can’t test
With Luro, I’ve found myself in the accessibility tooling space. I’m bullish on the need for automated accessibility testing to help designers and developers do a minimum viable good job, establish a baseline experience, and diagnose problems before they are giant problems. Even though automated tests cover 20-30% of WCAG Success Criteria, Deque data suggests those issues are representative of 57.38% of the most common issues found. In my mind, automated accessibility tests have four key tangible benefits:
A developer's perspective: the problem with screen reader testing | Jake Tracey
Screen readers are an essential part of using the web for people who are vision impaired, illiterate or have a learning disability. Today’s screen readers traverse web pages and applications and read out user interface elements, content and allow users to navigate and interact with the web. There are many screen readers available for different devices and platforms, each with differing levels of…