Without Doing It All by Yourself Angela M Hooker QuickA11yTesting AccessForAll AHG13 angela hookercom Hello Angela Hooker ID: 814814
Download The PPT/PDF document "Quick Ways to Test for Accessibility …" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Quick Ways to Test for Accessibility … Without Doing It All by Yourself
Angela M. Hooker#QuickA11yTesting @AccessForAll#AHG13 angelahooker.com
Slide2Hello!
Angela Hooker@AccessForAll#QuickA11yTesting | #AHG13#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
2
Slide3So, what’s up? …
3#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide4P
lan and prioritize4#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide5What are you testing?A video gallery?
A site? Is it responsive?A page?A mobile app?Is it for an official review or just a quick check for potential problems?5#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide6How much time
do you have?6#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide7Prioritize again
Do you only have to test or are you responsible for remediating the problems?Do you need to tell people how to fix the problems?7#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide8Use checklists and other resources
Create or find a checklist for your specific needs:25 Ways to Make Your Website Accessible (check for the items listed), by Dennis LembreeAccessibility Quick Check, Tom JewettWCAG 2.0 Checklist, WebAIM
Video and Audio Accessibility Checklist
Course Accessibility Checklist
Mobile: In “Resources” section in this document
8
#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide9Get help … for now
Colleagues (we’ll discuss them more later)StudentsVolunteersSurvey (depends on time)9#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide10After you test
…Think about what tools you like best—what appeals to me may not appeal to you.10#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide11How about a quick test now?
Just for a few minutes, let’s see what we accessibility problems we can find on a popular site.I’m going to use a few tools that I like:WAVE ToolbarWeb Developer Toolbar, by Chris PederickJuicy Studio Accessibility ToolbarPaciello Group Web Accessibility ToolbarNo assistive technologies (?!)11
#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide12Accessibility
remix!12#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide13Consider another
perspective and approach …13#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide14Consider another
perspective and approach … create an accessibility team from people you already have on staff.14
#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide15Share the
work based on roles instead of correcting your colleagues’ work.15#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide16This makes your entire team
responsible and accountable for their own work.16#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide17Talk with
management. (See Carol Smith’s Negotiate for the User.)17#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide18Canadian Government’s resources
Accessibility Responsibility BreakdownCanadian GovernmentBased on WCAG 2.0Coopérative AccessibilitéWeb18
#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide194
keys to building in accessibility19#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide20Understand
disabilities20#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide21Train your colleagues
according to each of their roles.21#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide22Teach them …
… that we need to test and plan for accessibility throughout each project's lifecycle.... how to choose technology that's accessible.... the importance of accessible platforms.... to not just do what the cool kids are doing for the sake of doing it.… development principles (good, clean, accessible code).22#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide23Teach them …
... accessible design principles.... how people who have low-English proficiency, dyslexia, cognitive impairments, etc. need plain language and other principles.… that we need to conduct usability testing with people with disabilities.… how people with disabilities use their assistive technologies—and that successfully using one assistive technology on a project doesn't mean blanket accessibility.23#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide24Divvy up the
standards24#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide25Give them tools
.25#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide26The roles overlap.
26#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide27Create a policy
Write an in-house policy (not an accessibility statement for the public).Developing Organizational Policies on Web Accessibility, W3C-WAIGet management support to make it stick.27#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide28It won’t
all happen overnight.28#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide29What doesn’t work
Putting the work before relationshipsDisinterest from upper managementThinking our process won’t evolveAllowing the accessibility program to be personality driven—it must outlive you29#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide30What you’ll gain
Save money by not making costly accessibility fixes later.You’ll have a solid process that fights the “accessibility is time consuming and expensive” issues.You’ll have a fluid process—stands despite staff changes, work demands, etc.30
#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide31Now, back to
you …31#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide32Keep calm and test quickly
32#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide33Thank you!
Angela Hooker@AccessForAllSlideShareange@angelahooker.comangelahooker.com
33
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide34Resources
34#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide35Sample process
Tailor this to your needs and to each project.Document this entire process and testing.Choose who should work on the project, and assign tasks/roles to everyone according to their
skills and strengths
.
Plan/gather requirements with the
decision makers
,
stakeholders
,
designers
,
developers
,
content providers
,
etc
.
35
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide36Sample process
Determine which standards and guidelines are appropriate for your project (WCAG 2.0, Mobile Best Practices, ATAG, CVAA, iOS Accessibility Standards, etc.).Put
accessibility requirements
in any vendor
requests for proposals
and/or
contracts
.
Determine your users’
top tasks
.
36
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide37Sample process
Review the information architecture.Analyze the resulting wireframes.Conduct usability testing with paper prototypes (wireframes).Choose and test the color scheme.
Assess the
design mockups
.
Review the final
written content
.
37
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide38Sample process
Conduct more informal user testing (test the mockups, content, information architecture).Review the templates (including ARIA); validate/remediate the (semantic) code.Just because your code validates doesn’t mean your project is accessible—validate anyway!
Just because your site doesn’t validate doesn’t mean it’s inaccessible—validate anyway!
38
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide39Sample process
Review the style sheets; validate/remediate the styles.Test with automated accessibility tools.Review the scripting (JavaScript,
AJAX
,
jQuery
,
YUI
,
whatever
); add more
ARIA
, if needed.
Test again with
automated tools
.
39
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide40Sample process
Test with assistive technologies.Test on mobile devices and e-readers.Test with real people, including several people with different disability types
—don’t forget to
test the written content, too
.
Continue to
improve and test after the launch
(since browsers and software change).
40
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide41WCAG 2.0 and general *a11y
Government of Canada Web Experience Toolkit (WET)—above all else, see the Accessibility Responsibilities Breakdown; it will help you create your process and define roles.Constructing a POUR Website, WebAIMBBC’s Future Media Standards and GuidelinesA11y Buzz* accessibility
41
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide42MobileMobile Accessibility Guidelines
, BBCMobile Accessibility Tests, Henny SwaniOS Accessibility – A Useful Guide For Testing, Rosie SherrySetting Up iOS and Android for Accessibility Testing, Kathy WahlbinWhy Mobile Accessibility Matters: Best Practices to Make Your Mobile Site Accessible, mobiForge
42
#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide43DisabilitiesDisability types/issues
Visual, cognitive, motor, and hearing impairments; neurological/seizure disorders; elderly and agingWhat Is Assistive Technology? – ATIAVideos of people using assistive technologies, from AssistiveWareHow Assistive Technology Works (demonstrations), University of Dundee
43
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide44Project managementIntegrating Accessibility in the Organization’s Web Development Life Cycle
, Denis BoudreauAccessibility for Project Managers, Henny SwanManaging Accessibility Compliance in the Enterprise, Karl GrovesPlan for Accessibility, Option Keys44#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide45Project managementPlanning Accessibility, Government of Canada
Just Ask: Integrating Accessibility Throughout Design, Shawn Lawton Henry45#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide46Writing contentAccessibility for Web Writers, by 4 Syllables
Content and Usability: Web Writing, Web CredibleMake it Plain: Accessibility and Usability Through Plain Language, Angela Hooker (hey!)Plain Language: Accessibility for Information, Whitney QuesenberyPlain Language Checklist, PlainLanguage.gov46
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide47DesignWeb Accessibility for Designers,
WebAIMJust Ask: Integrating Accessibility Throughout Design, Shawn Lawton HenryDesign Considerations, WebAIMColor Contrast Checker, WebAIM Accessibility Color WheelTrace Photosensitive Epilepsy Analysis Tool (PEAT) – tests flashing content
47
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide48DevelopmentWeb Accessibility for Developers
(videos), BBCBuild a code library!Use code generators (see Accessify’s tools).Web Developer Toolbar, Chris PederickFirebug, MozillaWCAG 2.0 Checklist, WebAIMWeb Accessibility Gone Wild, WebAIM
48
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide49DevelopmentW3C Mobile Web Best Practices
Juicy Studio Accessibility Toolbar —for ARIA, data tables, color contrastaChecker, Inclusive Design Institute at OCAD UniversityWAVE Toolbar, WebAIMFavelets for Checking Web Accessibility, Jim Thatcher49
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide50Quality assuranceTemplate for Accessibility Evaluation Reports
, W3C-WAIAccessibility Evaluation Resources, W3C-Web Accessibility InitiativeEvaluation, Testing, and Tools, WebAIMWCAG 2.0 Checklist, WebAIMWickline Color Blind Web Page FilterWeb Developer Toolbar, Chris Pederick
50
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide51Quality assuranceFirebug, Mozilla
Favelets for Checking Web Accessibility, Jim ThatcherTrace Photosensitive Epilepsy Analysis Tool (PEAT) – tests flashing contentWeb Accessibility Initiative (WAI), Evaluating Websites for Accessibility51#QuickA11yTesting | #A11y | @AccessForAll | #AHG13
Slide52Quality assuranceCentral Office of Information (COI),
Delivering Inclusive WebsitesEstablishing a Screen Reader Test Plan, Henny SwanHow to Use NVDA and Firefox to Test for Accessibility, Marco ZeheWeb Accessibility Gone Wild, WebAIM52
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide53UsabilityUsability Testing and
Conducting Usability Testing, Just Ask: Integrating Accessibility Throughout Design, Shawn Lawton-HenryUsability Testing for People with Disabilities, Kathy Wahlbin and Mary Hunter UttSteve Krug, Rocket Surgery Made Easy53
#QuickA11yTesting
| #A11y | @AccessForAll | #AHG13
Slide54Photo creditsMaking a List and Checking It Twice
, by KylesteedBig Ben, by SimpologistDJ Spinning, by Dan TentlerOld Keys, by Jakeliefer54#QuickA11yTesting | #A11y | @AccessForAll | #AHG13