Accessiblity for the Masses

I was recently reminded while working on our panel for SXSW that accessibility isn’t just about screen readers, markup guidelines, or alt tags. Unfortunately, that’s about as far as most of us ever get with accessibility. It’s good that most of us are making an effort, but it’s time to start consistently thinking bigger.

Screen Readers

This is generally the dominant audience that we think about with accessibility, and while it’s an important audience, there are plenty of others out there that can have difficulty with a site even if it is perfect on a screen reader. Following the level 1, 2, and 3 guidelines is a good start, but it’s only the basic foundation.

Keyboard (and Presumably Voice) Navigation

Another common accessibility challenge is for users who cannot use a mouse. Either they have lowered mobility or they may not have arms or hands. Whatever the reason, the ability to navigate by keyboard is extremely important to this audience. While most browsers do a decent job of allowing users to tab through the page, sometimes it takes a bit more to really make your site accessible for these individuals.

I won’t pretend to be an expert on how to accomplish this as it’s an area that I, myself, am just starting to dive into. However, it’s worth mentioning and reminding everyone that it’s something to consider when building for accessibility.

Low Sight

This is an area that can be fairly contentious, but we should all be striving to enable our visitors to view our site at whatever font size is comfortable for them. This means using fewer graphics with small fonts, sizing fonts without using px, and making sure that the design scales gracefully. Not everybody wants to have to go find their glasses to read something online briefly.

We all complain about how stupid businesses are for not putting their customers first, yet, so many of us refuse to take the time to put our visitors first and enable them to view our sites the way in which they are most comfortable.

Other Devices

Clearly we all want our information to be available to as many people as possible. That means we want our sites to be accessible by as many devices as possible. There are numerous ways to handle this, and I don’t want to dive in too deep with the details, but just wanted to remind everyone that accessibility isn’t just about disabilities. Can someone view your site on their phone, PDA, PSP, or other portable device? Are there people that would need to do so?


Since Google maps were an important part of what we were doing for the panel, we had additional accessibility challenges. While we didn’t have time to implement them, I found the process of thinking about them to be a truly eye-opening experience.

While working on the panel, I spoke with Derek Featherstone looking for some inspiration on how we could really improve the accessibility of our implementation beyond the basics. Naturally, he had plenty of ideas, but his input helped me refine my ideas and really think about accessibility and how to enable visitors.

Text Equivalents

Clearly, using a map is creating an experience that relies heavily on vision in order to benefit or gain value from a site. With Plazes, the map consolidated some of the most important information. Naturally, without a plain text equivalent, the experience would be inherently inaccessible and virtually worthless to anyone who couldn’t view the map version.

However, we’re not just talking about alienating users who can’t see. Individuals on pocket devices probably aren’t going to be receiving the full experience either. So, how do you translate a map into plain text?

While we didn’t get a chance to implement it, the decision was to provide distance and direction to the place relative to your position. With some basic calculations, we could simply insert text with each friend that said “4.3 km northeast at Starbuck’s.” So even on a PDA you could still uses Plazes to see if you have friends nearby and find out where they are.

Keyboard Navigation

Another feature, while not extremely easy to use on Google Maps is the ability to navigate with the keyboard and view the details of the given location. Unfortunately, it was slightly more challenging for us to maintain this functionality given our timeline, but the desire and thought was there.

Take a moment and try to use Google Maps without a mouse. It’s a bit more challenging, isn’t it? If you can’t click on a location and view the details, the experience becomes virtually worthless. Enabling users to access and view your data regardless of their input devices is another great way to improve accessibility. So, next time you build a site, try navigating with just your keyboard. After you’ve “walked” a mile in someone else’s shoes, you’ll have a new perspective.


Accessibility isn’t simply about blind users or going through a checklist. It’s about understanding the challenges that others face and realizing that “others” is actually a large group of people that includes those with disabilities, as well as those with different devices. This was the first time I really started thinking about accessibility from a higher level, and I found it challenging and rewarding at the same time. Having a higher level understanding of accessibility is imperative for us to move forward. Using alt attributes just isn’t enough.