Testing and Remediation Strategies

Question 1

On touch devices, what are some examples of where you would need an alternate method of activation?

Answer 1

Custom Gesture Events

Motion-activated Events (e.g. shaking)

Question 2

What are some things to test for in terms of keyboard accessibility?

Answer 2

All actionable elements are focusable and can be interacted with in the same way as with a mouse
All focusable elements have a visible focus indicator
Logical tab order
No keyboard trap

Question 3

What are some unique consideration for touch devices?

Answer 3

Sufficiently large touch target size
Allowing different screen orientation without losing content
All actions are still available with a screen reader turned on

Question 4

axe Monitor, Tenon.io, WAVE API, and AMP are examples of what kind of testing tools?

Answer 4

Automated - site-wide scanning and reporting

Question 5

wave.webaim.org, Cynthia says, and SiteImprove Accessibilty are examples of what kind of testing tools?

Answer 5

Automated - Server-based page analysis

Question 6

axe DevTools, WAVE browser add-on, and Google accessibility developer tools are examples of what kind of testing tools?

Answer 6

Automated - Browser plug-ins

Question 7

axe API and Tenon API provide which kind(s) of testing?

Answer 7

Automated - Unit testing (?), Integration testing

Question 8

Color Contrast Analyser (CCA), JAWS Access, and Headings Map are examples of what kind of accessibility testing tools?

Answer 8

Manual testing tools

Question 9

What are some of the factors that influence how you might prioritize fixing accessibility issues?

Answer 9

• User Impact
• Time to Remediate: (scope) how quickly can the issue be fixed?
• Business Priority: Is this part of a core user flow like purchase > checkout?
• Location of Issues: How much traffic does this page get?
• Volume: Will fixing one global issue handle multiple individual instances (like a global CSS update, or a commonly used component)?
• Secondary Benefit: Will fixing this issue benefit those without disabilities as well?

Question 10

What are the levels of user impact that an accessibility issue might have, and what do they mean?

Answer 10

1. Critical: This issue results in blocked content for individuals with disabilities. Until a solution is implemented content will be completely inaccessible, making the organization highly vulnerable to legal action.
2. Serious: This issue results in serious barriers for individuals with disabilities. Until a solution is implemented, some content will be inaccessible, or significant a work-around is required, making the organization vulnerable to legal action. Users with disabilities may experience significant frustration when attempting to access content.
3. Moderate: This issue results in some barriers for individuals with disabilities but would not prevent them from accessing fundamental elements or content. Users with disabilities may experience moderate frustration when encountering this issue.
4. Minor: This is an issue that may inconvenience a user but would not cause significant frustration in accessing content or accomplishing tasks.

Question 11

What are some of the things you should include in a bug report for an accessibility issue?

Answer 11

Descriptive Title
Impact/Severity
Issue Description
Platform and AT used
Steps to Reproduce
Expected Results
Visual or Video
Remediation recommendations