Testing & Remediation
Greg McNeilOverlay, Remediation, or Conformance: Which Do You Need?
Three tiers of accessibility vendor, priced an order of magnitude apart and sold as the same thing. What each actually changes, and which one your situation needs.
Greg McNeilWhat to Look for in a Web Accessibility Vendor
Every accessibility vendor says the same things in the same words. Ten questions that actually separate them — plus two answers that should end the conversation.
Greg McNeilHow to Revive Web Accessibility After a Plateau
Most accessibility programs don’t fail suddenly. They stall. At first, you see progress you can point to. But slowly, fewer people get trained, bug fixing slows down, and the accessibility dashboard plateaus once leadership stops looking at it. In some organizations, accessibility slips from a progr
Greg McNeilGoogle Lighthouse 100? Automated Testing Still Falls Short
A 100 score from automated testing feels good. Your dashboard turns green. The report says you passed every check. It looks complete. On paper, everything looks compliant. It is the kind of result that gets shared in Slack, checked off in a ticket, and filed away as “resolved.” But that score does n
Greg McNeilWhy Accessibility Costs Feel So Unpredictable
Budgeting for accessibility often feels like a moving target. One release looks manageable. Then a new feature ships, a vendor tool updates without warning, or a marketing push adds a batch of new pages. The estimate shifts, and the same question returns in planning discussions: What is this going t
Greg McNeilWhy Accessibility Belongs in Your CI/CD Pipeline
Teams that ship often know how a small change can ripple through an application. A refactor that seems harmless can shift focus, hide a label, or break a keyboard path in a dialog that once felt dependable. Users notice it later, or support does, and by then the code has moved on. Fixing that one [&
Greg McNeilHow to Test Mobile Accessibility using TalkBack
It is easy to rely on your eyes when reviewing a mobile site. A quick glance, a few taps, and the page seems fine. But that view is incomplete. Many users experience mobile content through audio, and their path through a page can sound very different from what you expect. Android’s screen reader, Ta
Greg McNeilWhat a WCAG Audit Should Really Tell You
Web Content Accessibility Guidelines (WCAG) provide a shared language for evaluating digital accessibility. WCAG 2.1 Level AA is the most widely accepted benchmark for audits today, and it gives teams a clear way to identify barriers that affect people with disabilities. But the presence of a standa
Greg McNeilWeb Accessibility Tools Worth Using in 2025
Web accessibility tools are becoming part of everyday work for many teams. Scanners run in the background, browser extensions sit ready during reviews, and screen readers are easier than ever to test with. The challenge is rarely whether to use these tools, but how to understand the results they pro
Kayla LaganiereHow Developer-Led Accessibility Breaks the Fix Cycle
Accessibility issues tend to surface in the same areas over and over again. Custom components. JavaScript-driven UI states. Forms and dialogs that behave differently depending on the input method. When these issues are addressed late, teams often fall into a familiar pattern: audit findings, rushed