Build all elements for accessibility
Everything that’s on your website needs to work to defined standards. Where you’re writing code that’s not HTML, it must conform to HTML-like standards. This means that it will work with various assistive technologies.
The key things to consider are advertising widgets, forms from third parties, things you’ve coded yourself and anything that you add that you can’t be sure how it was coded.
What to do
- Use HTML specifications for any script you author for your website.
- If you use a plugin or other element authored by a third party, make sure it uses valid HTML markup.
- A good – though not foolproof – way to test your website is a HTML validator tool. A validator gives you an idea of how well technology can parse your website. Use it to create a list of priorities.
- The majority of your potential issues will come from third-party code.
- Speak to the developers of any plugins you use and make sure that they’re writing good code.
- Make sure that everything on your website parses correctly.
- Pay close attention to things like names and labels.
- Guideline 1.1.1 – Non-text Content
- Guideline 4.1.1 – Parsing
- Understanding Success Criterion 4.1.2 (W3C)
Free Developer Resources
Join over 3,500 accessibility fans and get free developer resources like WCAG 2.0 Checklists and a sample from my book.
Over 250 people just like you have learned more about WCAG 2.0 with my guidebook.