Testing & Tools

Automated scanners, manual testing, and assistive technology.

• Automated vs Manual Accessibility Testing

  Automated scanners detect failure patterns for under half of WCAG's success criteria; the rest genuinely require human judgment. Here's the honest breakdown of what each approach can and can't do.

• axe-core Accessibility Testing: Examples and Results

  Learn how to run axe-core with Playwright, interpret violations and incomplete checks, fix findings and decide when ongoing monitoring helps.

• HTML_CodeSniffer Explained: The Secondary Accessibility Scanning Engine

  HTML_CodeSniffer is an older, broader accessibility rules engine that catches a different, complementary set of issues than axe-core - including WCAG AAA-level checks.

• APCA vs WCAG Contrast: What's Different, and Which One Actually Applies

  APCA is a newer, more perceptually accurate contrast model being developed for a future WCAG version. It's informative today, but WCAG 2.x's ratio-based formula is still the enforceable standard.

• Screen Readers Overview: NVDA, JAWS, and VoiceOver

  The three most common screen readers behave differently enough that testing with only one can miss real issues. Here's what each one is, and when to test with which.

• Keyboard-Only Testing: A Practical Guide

  Unplugging your mouse and navigating with only a keyboard is one of the fastest, cheapest, highest-value manual accessibility tests available. Here's exactly how to do it.

• Fixing and Rechecking Accessibility Issues on a WordPress Client Site

  A worked example on a WordPress 6.8 demo site: three automated findings, two problems the scan could not see, the editor changes that fixed them, and the recheck.

• Fixing and Rechecking Accessibility Issues on a Webflow Site

  A worked example on a published Webflow page: what an AllyProof scan found, the Webflow behaviours behind each finding, the fixes, and the rechecks.