Web Accessibility presentation for Big Sky DevCon
•Als KEY, PDF herunterladen•
1 gefällt mir•233 views
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Web Accessibility presentation for Big Sky DevCon
Ähnlich wie Web Accessibility presentation for Big Sky DevCon (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Web Accessibility presentation for Big Sky DevCon
- 1. Web Accessibility "The dignity of the human being is inviolable." The Montana Constitution, Article 2, Section 4 adopted 1972
- 2. Fear • Am I exposed to legal risk? • How do I make it accessible? • Won’t it drastically limit what functionality I can add?
- 3. Confusion • WAI-ARIA • ADA • WCAG 2.0 • Section 508
- 4. 1990 Americans with Disabilities Act
- 5. Section 508 of US Rehabilitation Act
- 6. What if I get a complaint? • Don’t panic. • Fix it right away or engage in a dialog. • Treat all complaints seriously. • People don’t sue as a first resort.
- 8. Who needs web accessibility? • More than blind users. • Includes users with older technology. • 8.5% to 20% of population. • Eventually, we all become disabled or dead.
- 10. Google is the archetype of a disabled user
- 11. The path to accessibility
- 14. The pitch for buy-in
- 15. The pitch for buy-in • It’s good for users, and broadens the user base.
- 16. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans.
- 17. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk.
- 18. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk. • SEO.
- 19. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk. • SEO. • Avoid potential future bad PR, get good PR.
- 20. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk. • SEO. • Avoid potential future bad PR, get good PR. • Follows standards/best practices.
- 21. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk. • SEO. • Avoid potential future bad PR, get good PR. • Follows standards/best practices. • It’s easier to do up front.
- 22. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk. • SEO. • Avoid potential future bad PR, get good PR. • Follows standards/best practices. • It’s easier to do up front. • Freelancers can make more money on user training.
- 23. The pitch for buy-in • It’s good for users, and broadens the user base. • Help veterans. • Reduce exposure to legal risk. • SEO. • Avoid potential future bad PR, get good PR. • Follows standards/best practices. • It’s easier to do up front. • Freelancers can make more money on user training. • Moral imperative.
- 24. Dan Bowling dan@northlander.org @danbowling
Hinweis der Redaktion
- About me\n-Work at UM\n-Been teaching accessibility to content authors for 7 years\n-In about 30 years I’ll be a disabled user\n\nPeople fear web accessibility\nPeople are confused about web accessibility\n\n
- \n
- Touch on WAI/ARIA/WCAG\n\nADA & 508 next\n
- Civil Rights Act\n Applies to places of pubic accommodation, employers, and state/local governments\n Are websites places of public accommodation?\n sufficient nexus to such physical places of public accommodation\n DOJ is in public comment to say Web applies\n Enforced through complaints and civil suits\n NFB vs. Target ($6m settlement)\n Florida blind citizens vs. Southwest (technical dismissal)\n\n
- Requires Federal agencies to make electronic and information technology accessible\n Includes private sites receiving Federal funds or under contract with a Federal agency\n Computers, Multimedia, Web\n Has ways out via Undue Hardship, or fundamental changes\n DOJ actively enforces... 200 cases so far. Penn State hit hard.\n DOJ taking public comment on using WCAG 2.0 as enforcement measures.\n
- Target ignored the initial complaints, it cost them $6m\n
- Which of these users are disabled?\n\n
- \n
- Visual - blind, colorblind, narrow vision, cataracts\nMotor/Mobility - different input devices, low accuracy\nAuditory - Multimedia/ClosedCaption\nSeizures - Screen refresh rates, repeating background flicker\nCognitive - TBI, Attention issues, cognitive load\n\nVeterans, Elderly\n
- Google is the archetype of a disabled user.\nDoesn’t do well with flash and images\nNeeds alternative text\nLink text matters\nReads tables linearly\nCares about font size and color contrast\nDoesn’t work well with all javascript\nDoesn’t trigger :hover or click events\n
- Templates/design\n Web standards\n Run auto scans\n Separate content/presentation\n Train content editors (this can be a money maker for freelancers and shops!)\n Don’t forget to check your links out of context\n Make it easy to report barriers\n Better to bake-in than add-on\n Accessibility is another way to meet the needs of your users\n
- Good baseline.\nNot 100% accurate.\n\nWAVE, Cynthia Says, Validators.\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n