An Intro to Web Accessibility
Did you know that there are currently only 13 themes that show up in results when you filter by the “accessibility-ready” tag in the WordPress Theme Directory? (Checked in October, 2014)
Of course, this doesn’t necessarily mean that there are only 13 themes out of the 2000+ that are accessible, they may just be missing their theme tags. However, there is also a high chance that a theme you’re using, or one that you’re building, is not accessible (uh oh)!
Well, how do we know if our theme meet’s the accessibility guidelines and if it doesn’t, what steps can we take to resolve that problem? This the first post in a series that will guide us through those steps. If you have a couple of minutes a day, we can work on making your WordPress theme accessible together – a few easy steps at a time.
Before we dive into code, I’d like to briefly review what web accessibility is, who it’s for, how it’s used and what to expect in future posts for this series. Let’s get started.
First, What is Web Accessibility?
According to Wiki:
Web accessibility refers to the inclusive practice of removing barriers that prevent access to websites by people with disabilities. When sites are correctly designed, developed and edited, all users have equal access to information and functionality.
This means that a user, regardless of age and/or disability should be able to access your site and absorb the same information as others users do.
Who is Web Accessibility for?
Using the Web Accessibility Initiative section on W3.org as a reference, there is a diversity of people that benefit from sites that practice accessibility standards. A few examples of who these people might be are:
- People that have auditory disabilities, ranging from mild hearing loss to deafness. Just as an FYI, I am hard of hearing in both ears and have been that way since childhood. I’ve included a short summary about it on my “about” page if anyone’s interested. ( More about auditory disabilities… )
- People that have disorders involving the nervous system like ADHD or memory impairments. ( More about cognitive/neurological disabilities… )
- People with physical disabilities that would prevent them from using a traditional mouse/keyboard. ( More about physical disabilities… )
- People with speech disabilities such as muteness or cluttering. ( More about speech disabilities… )
- People with visual disabilities, ranging from color blindness to blindness in general. ( More about visual disabilities… )
And let’s not forget the elderly or those that may have a combination of disabilities or impairments. Just as some food for thought:
“About 20 percent of adults in the United States, 48 million, report some degree of hearing loss.” ( hearingloss.org )
That’s a lot of people, and this is just auditory disabilities alone. Combine that with everyone else in our list above, and you can already see all the potential users your site can be missing out on if it’s not meeting accessibility standards.
What Tools Enable These People to Access the Web?
Some examples of tools that are used to access the web by those with disabilities are:
- Screen Readers
- Voice Browsers
- Specialized hardware that replaces or enhances a keyboard/mouse
- Text to Speech hardware/software or visa-versa
- Perhaps only a mouse or only a keyboard
For more information on how the web is accessed depending on a user’s disability, check out the Tools and Preferences section on W3.org.
Finally, How Can We Make Our WordPress Theme Accessible?
In the posts following this introduction, we’ll go over some plugins that may help as well as what we can do code-wise to edit/enhance our WordPress themes right that moment. Some examples of what we’ll go over are heading tags, skip links, the alt attribute on images, html structure and so on. Each post will be dedicated to a particular aspect of accessibility so we can focus on applying one change at a time. Making your theme accessible shouldn’t have to feel like tearing down the entire house and re-building.
My WordPress theme, Hexa, could also use some improvements as far as accessibility goes. Therefore we’re in this together and I’m looking forward to learning with you post by post. Until next time…