0Pricing
Web Accessibility Academy · Lesson

Building a Manual Audit Workflow

Combine keyboard, screen reader, and zoom checks.

Building a Manual Audit Workflow is a free Web Accessibility Academy lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Accessibility Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Why Manual Beats Automated Alone

Automated scanners catch maybe 30% of issues. A manual audit is how you find the broken experiences a robot can never feel. 🔍

Audit With Real Tools, Not Guesses

A solid manual audit leans on three pillars: the keyboard, a screen reader, and browser zoom. Together they reveal what real users hit.

Start With the Keyboard

Unplug your mouse and press Tab through the page. Every link, button, and field should be reachable in a sensible order.

<!-- Tab should reach this, Enter should fire it -->
<button type="button">Save changes</button>

Watch the Focus Ring

As you Tab, you must always see where you are. A missing focus indicator leaves keyboard users completely lost on the page.

Listen With a Screen Reader

Turn on NVDA, VoiceOver, or TalkBack and navigate by heading and landmark. Does what you hear match what you see?

Zoom to 200 Percent

Press Ctrl or Cmd plus to reach 200% zoom. WCAG requires no loss of content or function, with no horizontal scrolling on a normal page.

Check Color and Contrast

Sample real text against its background. Body text needs a contrast ratio of at least 4.5 to 1 to pass WCAG AA.

Inspect the Accessibility Tree

Open DevTools and read the accessibility tree. It shows the name, role, and state that assistive tech actually receives for each element.

Follow a Repeatable Checklist

Work from a fixed checklist every time. A consistent list means you cover the same ground and never skip a critical check by accident.

Quick Check

Pick the trio that anchors a thorough manual audit.

Record What You Find

Capture each issue as you go with a screenshot or note. A clear record turns a messy audit into a fixable, trackable list.

Audit One Flow at a Time

Scope each pass to a single user flow, like sign-up or checkout. Small, focused passes find more than skimming the whole site at once.

Recap: Your Audit Workflow

You now run a manual audit with keyboard, screen reader, and zoom, read the a11y tree, and log findings flow by flow. 🎯

Frequently asked questions

Is the “Building a Manual Audit Workflow” lesson free?

Yes — the full text of “Building a Manual Audit Workflow” is free to read here on the web, and the Web Accessibility Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Accessibility Academy course, upgrade to CoddyKit PRO.

What will I learn in “Building a Manual Audit Workflow”?

Combine keyboard, screen reader, and zoom checks. You practise Web Accessibility Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Web Accessibility Academy?

No prior experience is required. Web Accessibility Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Building a Manual Audit Workflow” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Web Accessibility Academy lesson?

Yes. Every Web Accessibility Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Building a Manual Audit Workflow
  2. Severity and Impact Triage
  3. Writing Bug Reports Developers Can Act On
  4. Remediation Without Regressions
← Back to Web Accessibility Academy