Designing and developing for web accessibility has become a requirement of modern computing. Depending on the content and complexity of your project requirements, it can also be a very difficult pursuit.
We’ve talked about how to start following the principles of accessibility. Now we’re going to dig into the nuts and bolts with a real-life example of one of the simplest ways to save time and tedium for users working with assistive technologies. Today, we’re talking about skip links.
The Web Content Accessibility Guidelines (WCAG) offer a short list of focal areas for website design that can also be applied to software design in general. Here, I’ll break down the four categories of guidelines in WCAG 2.0 and offer some suggestions on how to plan for and evaluate them when designing software.
Imagine, for a moment, that you are a computer user with a disability. You might have impaired vision or hearing, or limited motor control. How do you go about using your computer? How would the way that you use technology be affected if you didn’t see your laptop screen, or didn’t hear notification sounds?
It’s a widely accepted truth that accessibility on the web is important. Of course, everybody should have equal access to technology! However, when it comes down to it and project timelines and budgets are at stake, it can be more difficult to put this belief into practice. As technology continues to emerge and best […]