2.5 Use accessibility testing tools effectively Flashcards
What is a flaw of automated accessibility testing tools?
They cannot provide human context.
Example- they can find if images have alts but they cannot evaluate if the alt text meets guidelines
What two things should a tester identify in the results?
Accessibility problems
Optimal accessible results
No accessibility software tool can find all the accessibility issues on a web site.
True or False?
True
What does a basic manual test involve?
Verify correct navigation and functionality using the mouse and the keyboard:
• Interactive elements must receive focus (links, data input or buttons)
• The location of focus is visualized
• The screen reader announces adequate tags or alternative texts
• The functions of the components, such as menu and submenu, accordion,
tabpanel, carousel, etc., can be browsed or performed correctly. In such
components, the roles and states notification should be verified.
What software tools can be used during Design?
Development?
Test?
Tenion.io, axe DevTools, ANDI works during development
aXe API runs on a page and returns JSON file
SiteImproveAccessibility- enter site name, email, get report
ARC Toolkit (CynthiaSays replacement) is Chrome extension, can find errors, test rems in DOM
ANDI tells you what will be announced
iOS has Accessibility Inspector and Accessibility Verifier
What are two good vision simulators to test for low-vision/color blindness?
Color Oracle- color blindness
No Coffee vision simulator
What tool can check color contrast?
WebAim’s Contrast Checker
What are some accessibility issues only found with manual testing?
(think of the things on the BUGS versus WCAG rems)
keyboard navigation
keyboard focus is visible
tab order
Form data retained on refresh or time out
Empty required form field gets focus on error
Multi media is accessible
Descriptive text for links
Decorative images have alt = “”
Images and buttons have descriptive text
Fonts zoom in and out, no crowding or pixelating
Documents linked to sites also must be accessible. What are some things to tests PDFs for?
PDFs are searchable (OCR’d)
they read in logical order
not text content is labeled
Documents linked to sites also must be accessible. What are some things to test WORD docs for?
Hierarchical headings
Alt text on non-text items
Documents linked to sites also must be accessible. What are some things to test PowerPoint for?
Logical reading order
Alt text on non-text items
Sufficient contrast
For scientific text and math symbols, what do you test for?
That a screen reader can read them
Testing for non-audio access to audio content such as podcasts and videos
Users control start and stop
Videos have accurate captions
Captions have sufficient contrast
All audio files have link to a transcript
For people with brain injury or cognitive issues, what can we do?
Clear and simple content: Fonts are easy to read Viewing area not crowded or chaotic Lots of white space No Flashing, blinking or moving text or content Menus consistent across site Visual navigation is logical
How to deal with color?
Contrast must pass the tests
Color only is not used for meaning
Hover state depicted with good contrast or underline
CAPTCHA needs what?
Audio captcha needs what?
Keyboard accessible
everything is read by SRs
Audio needs alt for deaf people
Audio is read by SRs with no overlap between the SR voice and the audio captcha voice
iframes are accessible how?
Descriptive title attribute
Refreshing stays on current frame
SR can navigate between the frames
SR announces purpose of each frame
Data Tables need what?
Header and/or column rows
Caption
Not nested
Proper Scope labels
Tables used for layout are accessible how?
They do NOT have header rows Reading order of the cells is logical User customization and text scaling is allowed Not nested No spacer cells
Forms, what to test?
Can be filled out using SR
Fields have labels read by SR
Buttons labeled and read by SR
Required field left blank SR reads error and that field receives focus
When error dialog dismissed, focus to that field
What might a good test report include?
Which URLs were tested
What tools were used to test
the current standing (meets or is close to meeting A, AA)
Features where site is strong
Recommended priorities for addressing the rest
Recommendation for on-going evaluations
Analysis of web authoring tools if an issue
