WordPress developers spend so much of their time thinking about site optimization. Is it fast enough? Is the layout intuitive? Are the images the right size and resolution? Is the content interesting?
And while all of this is certainly important, not nearly enough attention is paid to site accessibility. Can everyone you want to gain access to your site do so easily? Once there, can they navigate without any problems? Do you offer solutions for those with disabilities?
There’s a lot to think about, so I won’t waste anymore time with intro fluff. Let’s get right to the meat.
Also known as the WCAG, the Web Content Accessibility Guidelines outline everything you should be doing to make your site accessible to as many people as possible. Why would you want to do that? As per the guidelines’ abstract:
Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.
Makes sense, doesn’t it? If you take the extra effort to make your site usable by those with disabilities, you broaden your reach considerably. In short, more people will land on your site and have a positive experience. And if that’s not good for your bottom line, I don’t know what is.
The first version of the WCAG were published in May 1999. It’s now on version 2.0, which was published in December 2008. It’s currently broken down into four key “principles” including:
These broad principles can be applied to any website online, not just those using WordPress, of course. And while I may speak generally about some measures you can take to improve any site’s accessibility, I’m going to do my best here to make my suggestions as WordPress-specific as possible.
With that in mind, the remainder of this article will be divided by the four principles listed above and offer specific ways you can achieve that principle for your WordPress site using plugins, external services, and more. While it may not be possible to hit every single guideline recommended in the WCAG, I’m doing my best to fit in as many as I can here.
Can your site visitors perceive all the elements on your site, regardless of disability? The WCAG offers these guidelines for ensuring you’re accommodating everyone:
So, photos can be described. Text can be turned into speech. And alternate text forms can be supported like large print and braille.
The Accessibility Widget lets you add a widget to your sidebar exclusively for changing the text size on your site. And the GSpeech plugin adds text-to-speech to any text on your site. You can even set an audio greeting for your visitors.
To add text descriptions to each of your images, you just need to make use of the “alt” tag. You can do this manually, but the SEO Friendly Images plugin adds the right title and alt attributes to all of your images for greater accessibility, of course, and greater search engine optimization.
Audio and video recordings can be supported with text transcripts, captions, and/or an audio-only track describing video content. Audio content is supplemented with sign language.
Don’t just rely on color to denote an element you want users to pay particular attention to. Also, offer high contrast color schemes to aid those who are visually impaired. This can be accomplished using the WP User Stylesheet Switcher. All the site visitor has to do is click on a dropdown menu to select a high contrast stylesheet and the content will be easier to read.
You can also use a plugin like EsAudioPlayer to add a simple accessible audio player to your site so you can embed audio content and let those using text browsers download audio files. It’s also designed to work with screen readers, whose users can select the play and stop buttons easily.
From large text options to the ability to resize text up to 200% without compromising function, this ensures users can read everything clearly. Avoid using images of text. Plain ol’ text will suffice.
The Zoom plugin makes it simple for users to resize predefined areas of your site. With it, you can set minimum and maximum resizing percentages and apply it to specific classes, IDs, and tags.
Does your site work well in a variety of different ways? Can it be accessed from a number of different devices and does it account for assistive technology?
That is, you can perform just about every task on your site using a keyboard. You also ensure that there are no keyboard traps, or spots on your site where input via keyboard can’t be navigated away from using a keyboard. You can install Accessible Dropdown Menus to allow site visitors can access your menus via the keyboard alone. And you can use Accessibility Access Keys to create site-wide access keys to make for easier user navigation. This is particularly helpful for bypassing those keyboard traps mentioned above.
If time limits are in place, let users turn them off or allow for adequate extensions, unless there’s a real time component in play — an auction, for example. Also, moving content (auto-scroll or auto-updates) are to be presented either in conjunction with non-moving content or the function can be turned off.
Since autoscroll isn’t a feature that’s built into WordPress, you don’t have to worry about this one that much. In the name of accessibility, it might just be best to avoid plugins that offer this feature altogether. Infinite scroll — a feature that automatically loads new content when you reach a page’s footer — is sometimes built into themes. The auto update feature could possible throw off screen reader functionality, so be on the lookout for that as well.
Content on your site shouldn’t flash more than three times per second. So steer clear of manic animated gifs — though you should probably do that anyway!
This includes clear titles, sequential ordering, contextual linking, multiple link paths, and descriptive headings. An SEO plugin can actually be really helpful in achieving these accessibility points. You see, SEO requires that your content be clear and offer logical navigation, too.
Try installing something like WordPress SEO by Yoast or All-in-One SEO Pack to add prompts to your post editor for customizing page titles, descriptions, metadata, and more. You’ll also want to create a sitemap, which the search engine will love, of course. But screen readers can also use them to allow for quicker site navigation. Use a plugin like Google XML Sitemaps to generate one on the fly.
Is your site’s content and navigation clear? Can it be comprehended with little to no explanation?
It should be written in a clear and concise manner with the language clearly identified and word choice that could easily be read aloud by a computer voice. It’s also a good idea to define jargon, difficult terms, and abbreviations.
You can quickly add a glossary to your site using the CM Tooltip Glossary plugin, though you may need to do some CSS fiddling to get the tooltips large enough to meet accessibility standards.
Site content fits its headlines and links. Navigation is predictable and looks the same on every page. Thankfully, WordPress is equipped to support logical navigation to start with. Though you can also play with custom menus to ensure you’re offering the most clear link options as possible.
If spelling or typing errors are made, offer suggestions or automatic corrections. Provide clear instructions for areas that require user input and implement a fool-proof “error prevention” system that lets users reverse, double check, and confirm submissions — especially when they contain financial or legal data.
You might want to use something like Submittable in this case — along with its WordPress plugin to let site visitors submit a variety of file types. The automated system asks for confirmation before the submission is sent.
A robust site is one that has thought of everything. Does yours meet the needs of as many people as possible in as many ways as possible?
Offer compatibility with assistive technologies. That means your HTML is beyond clean with start and end tags, no duplicate attributes, and unique IDs. You need clear headers and paragraph elements so the content appears as it should on screen readers. Basically, fancy HTML should be avoided. Want to add style? Use CSS. Otherwise, let basic formatting serve your content well.
This plugin merited its own section here because it covers so many of the guidelines mentioned above and only takes one plugin to it. WP Accessibility offers a wide variety of features, all designed to make a site meet the WCAG by modifying your WordPress theme.
For starters, this plugin fixes several accessibility issues that are inherently present in WordPress. Many of these fixes are deep down in the code, but they make a real difference in how your site is presented to those using assistive technologies. For instance, it removes the tabindex from focusable elements, adds post titles to “Read More” links, and removes the target attribute from links.
It also adds several features like letting users skip links, adding an outline to the keyboard focus state, adding descriptions to images, and adding a toolbar specifically designed to give site visitors the option to switch between high contrast, large print, and grayscale theme views.
WP Accessibility includes several other features but it’s an all around great plugin that can help you fix several accessibility problems all at once.
Making your WordPress site accessible might seem like a lot of work at first, but the benefits are multi-faceted. For starters, you’re doing the right thing by making your content viewable and usable by the largest number of people possible. And second, you’ll automatically improve your SEO, which means increased site traffic. And both of those factors combined means a greater likelihood of site success.
The Web Content Accessibility Guidelines might feel overwhelming on first glance, but hopefully this will help you get started and start checking a few of those modifications off your to-do list.
Are you making efforts to make your site more accessible? Or are you a total rockstar and it’s already WCAG compliant? I’d love to hear your thoughts on the subject, including any challenges you’ve faced in the comments below!
Source: Elegant Themes