This document discusses web accessibility and provides an overview of key topics including what web accessibility is, the impact of accessibility, and how to get started with accessibility. It defines web accessibility as designing websites to ensure content is accessible to all users regardless of ability. It discusses the history and guidelines around accessibility, including the Web Content Accessibility Guidelines (WCAG). It notes that while the guidelines tell us what to do for accessibility, they do not tell us how to do it. The document recommends planning an accessibility approach, learning about the guidelines, advocating for accessibility, and including accessibility in all aspects of web design and development.
6. WEB ACCESSIBILITY
Designing and developing to ensure that a website’s
content is accessible to all users, irrespective of ability.
Achieved by adhering to established guidelines.
7. WEB ACCESSIBILITY
Started gaining traction in 1999 with the release of the
first web content accessibility guidelines.
Gained more attention through a series of lawsuits.
• Target
• Bank of America, HSBC, Fleet Bank, Bank One
• Marriott
• EdX
9. BLAME THE WCAG
WCAG = Web Content Accessibility Guidelines
WCAG 1.0 wasn’t particularly clear
WCAG 2.0 is better, but difficult to parse
10. BLAME THE ADA
The ADA does not explicitly mention websites as
required to be accessible.
This is likely going to change next year.
11. BLAME HUMAN NATURE
People are generally not aware of the WCAG
Companies have viewed accessibility as an additional
cost that threatens project budgets
People don’t like making tough choices
25. WHAT IS THE WCAG?
Created by the W3C / WAI
Four principles. 12 Guidelines. 61 testable criteria.
Covers a range of disabilities and assistive technologies
Three levels: A, AA, AAA
26. WHO IT’S FOR
Useful for designers, developers and QA
Helps ensure a wide range of disabilities and assistive
technologies are covered
Enables automated testing for most criteria, but testing
with real users is also required