(Week: 5) I: Snippet Audit

Last revised date: 9/17/2026

View / submit on Canvas

Overview

Learn to evaluate web/app accessibility using WCAG guidelines, manual testing, and screen readers

When you turn in this homework you will be assessed on these competencies: Accessible Implementation.

Assignment Details

• Individual Competency Check
• Writeup and Handin
  • VPAT Table

Individual Competency Check

After working through the Teach Access “Writing Code” tutorial, you’ll get 2 short inaccessible html snippets. We’ll ask you to identify the WCAG success criterion each violates and suggest an improvement.

Writeup and Handin

You’ll need to turn in a VPAT table (see below).

VPAT Table

| Criteria | Severity | Conformance Level | Brief Explanation | |—|—|—|–| | 1.4.4 (Resize Text) | | || | 1.4.10 (Reflow) | | || | 2.4.3 (Focus Order) | || | | 4.1.2 (Name, Role, Value) | | || | … (all categories in the WCAG beginner’s guide) | | ||

What do these mean?

• Severity: You should be able to justify this in terms of impact, persistence and frequency.
  • Impact: how badly does this barrier block the task, for the user, right now?
  • Persistence: how hard is it for the user to work around the barrier, not how hard it would be for a developer to fix it later. Example: if a screen reader user has no way to skip this and must listen to the whole menu every time, this is a persistent issue.
  • Frequency: How often are they likely to encounter this issue when using a system
• Conformance Level: A, AA, AAA, or not conforming (defined in WCAG)
• Explanation: What is the problem you found? How does it impact users

See Canvas