Common accessibility blunders
Are you responsible for maintaining your company’s Website? Or responsible for the design and build of your companies new Web site? New to the whole design and build game in general?
Have you heard of the W3C, Tim Berners-Lee, WAI or Web Content Accessibility Guidelines? No! not to worry.
Heres the skinny…
The World Wide Web Consortium (W3C) develops interoperable technologies (specifications, guidelines, software, and tools) to lead the Web to its full potential.
Tim Berners-Lee is the Director of the W3C and inventor of the World Wide Web.
The Web Accessibility Initiative (WAI) works with organizations around the world to develop strategies, guidelines, and resources to help make the Web accessible to people with disabilities.
The Web Content Accessibility Guidelines (WCAG) developed by the WAI are guidelines widely regarded as the international standard for Web accessibility. They are also referred to as best practice guidelines
Over the years Segala has conducted many many independent audits of Web sites for accessibility compliance. This means we have manually checked if a Web site passes or fails the WCAG check points. Companies have engaged Segala to ensure their Web sites are compliant on the fear that they maybe excluding some users from accessing information within their Web site.
Below is a list of common issues found during some of those accessibility audits:
- Images have inappropriate alternative text
- Page sections don’t have their own headings
- Headings are incorrectly nested (H2 should follow H1, H3 should follow H2 etc)
- Link text does not make sense when read of out context
- A Focus state is not provided for links
- Form labels are missing or incorrectly positioned
- On-page items are incorrectly marked up in HTML
- Skip to main content link not provided
- Decorative elements are marked up in HTML code
To any developer well versed in the world of accessibility these issues are easy to over come. If the world of accessibility is new, you can sit down with a very large cup of coffee and try digest all the WCAG documents and working examples. It is possible and I would advise reading them and when finished read them again and again. After that take one guideline and apply it to your own Web site, baby steps.
Over the next few posts I’ll cover each bullet point above in more detail. Its very easy to pick up a bad habit, all I’m asking is that you develope the habit of considering accessibility when building a Web site.
I’m not going to quote guideline check point after check point. Instead I’m going to cover what is considered best practice and how people implement them in the real world.
4 Responses to “Common accessibility blunders”
Leave a Reply
I am NOT solely responsible for the University of Cincinnati’s website, but have some input about how it looks and functions. The team is just beginning to look at a revamp, so finding this blog is timely for me.
As a public institution, we must keep accessibility issues in mind all the time, but to date, our web presence is not doing that very well. I am interested in finding out more about how we can do a better job of that. Suggested readings?
@Sine A University the Web site should be compliant. Most Universities have Ability Officers assigned to manage both online and offline access for all.
Accessibility is something that is often over looked. It should be built in, not bolted on. If done right the site ends up being easier to manage.
A revamp is the perfect time to address the Web sites accessibility. Sit down with the team to discuss the benefits of accessibility. If the University has an officer get them involved.
Start out by looking at the current issues people face with the existing site, run a poll or survey. Both students and other users may highlight usability and accessibility issues the team may have over looked. The amount of effort put in now will be a huge benefit to the final revamped Web site.
If the Web site is CMS managed, the University could have the new templates and designs independently audited. This is a service we offer.
Lastly, assign someone on the team to be responsible for the accessibility of the new site. This person does not have to be an expert as the delivery is a joint effort but it is always good to have at least one person asking questions.
Granted, some research my be required on their behalf but we’re always happy to help. If only to answer a few questions or offer advice.
Please feel free to contact me adrian[at]segala[dot]com
Thanks for taking care of this issue.
Accessibility is something that is often over looked. It should be built in, not bolted on. If done right the site ends up being easier to manage.