Coding for Accessibility
You’re most likely here because you need to make sure your coding practices are accessible to people with disabilities.
You might have a specific problem, like:
- how to ensure code for a new site is accessible
- how to review existing code to make sure it complies with requirements
- how to fix or replace existing code that you know has accessibility problems
- how to use tabindex, longdesc or doctypes to enhance accessibility
- what implications iframes, blink and marquee have for accessibility
Perhaps you need a comprehensive list of likely accessibility issues associated with specific coding techniques – and how to address them. Or maybe you just want to ask a direct question and get a clear, expert response.
You’re in the right place.
OzWiki will tell you what you need to know to make sure the code you use is consistent with accessibility requirements. The Coding section details 51 accessibility problems and how to address them, demonstrating compliance with 37 WCAG Level A success criteria, eight Level AA and six Level AAA success criteria.
As a subscriber, you’ll also be able to request further or more detailed information relating to your specific situation.
OzWiki is an accessible resource that provides best known methods to achieve A & AA level design and interaction for web content in areas such as Audio, Video, Link, Captcha, Maps, Navigation and more. These outlined accessibility errors, examples and solutions help you become 508 compliant by demonstrating associated WCAG 2.0 success criteria and techniques.
Gain access to more detailed information on all OzWiki categories for only $39/month by purchasing a subscription today! You can cancel your subscription at any time.