When talking about (web) accessibility, we’re talking about ensuring your web project is usable by as many people as possible, on as many different devices as possible.
It really is about putting the user first.
This doesn’t only include people with a permanent disability, but also a temporary, situational or constantly changing disability.
For example:
- A young web developer who uses a laptop with a keyboard and a mouse.
- A blind person who uses a desktop computer, keyboard and a screen reader.
- A blind and deaf user, who uses a desktop computer, keyboard, screen reader and braille display.
- A traveler who uses a smartphone on a train with a bad WiFi connection.
- An elderly person who uses an iPad in bright sunlight.
- A child who broke an arm and uses only the keyboard.
Web accessibility means that visitors using various ways to interact with the website, can operate the functionality and understand the content. With eyes and ears, fingertips, a screen reader, voice recognition software, a keyboard only, on a smartphone or desktop and what other interfaces the future may bring us.
Is it doable? Totally. As long as you build with accessibility in mind from the start.
