There are 3 types of relationships in a web page: explicit, implicit, and content-based relationships. Read this to see what they are and why they’re critical to ensure accessibility for everyone.
The latest and greatest Dragon Naturally Speaking (version 13) finally catches up, at least partially, with a critical web standard: WAI-ARIA.
You too can be a keyboard accessibility super hero if you do these three simple things really well. The best part is, you don’t even have to work that hard to do them and they make you look brilliant!
Automated infinite scrolling is a popular web design technique even though it creates difficult accessibility problems for keyboard users.
Hoping to increase awareness for accessibility, I posted this note over on FaceBook—to try and reach out to a different audience than the technology industry.
If you’re not considering content strategy, creation, and writing an essential part of web accessibility, you’re failing.
Most often the focus of accessibility training is design and development techniques for creating accessible web sites and applications. That’s almost too late, though, isn’t it? Today we’ll look at the procurement piece of the puzzle. We talk with Ron Lucey about how the state of Texas uses procurement policies, contract language and remedies to help deliver on the promise of making the web accessible to everyone.
Hiding URLs in the browser is like hiding anything. For accessibility, things are usually best left out in the open.
There’s an emotional aspect to accessibility that makes it difficult to determine exactly how we should design for a particular persona.
With HTML5 came the great and mighty data- attribute. There was much rejoicing and application of data- attributes with much fervour and pride. Yet it is often used when it shouldn’t be: when a much simpler solution exists.