Web Accessibility has always been an important topic within the Drupal community. Having a fully accessible website has many benefits in addition assisting people with disabilities. But now that AODA (the Accessibility for Ontarians with Disabilities Act) has come into effect for all organisations in Ontario with over 20 people, for many of us it's the law.
This session is primarily targeted towards Designers, Developers, and Content Producers, but it will also be of great interest to Project Managers and Product Owners.
In this session I offered guidance on how to:
- Audit your website (for AODA compliance)
- Test your code (for WCAG 2.0 A, AA, and AAA ratings)
- Understand and interpret the WCAG 2.0 guidelines
- Develop processes for Accessible Content and Feature Development
In addition I tried to answer the following questions (among others):
- What is AODA?
- How does this affect me?
- Why now? Why should I care?
- What’s covered? What's not?
- Isn't Drupal already accessible?
- What do I have to do to make my site accessible? Is this a one-time thing?
- Where can I find more info? Where can I get help?
Clipping is a handy way to collect important slides you want to go back to later.