Blog

Accessibility, without the ceremony.

Practical writing on WCAG 2.2, AI-assisted remediation, and building accessible software the way modern teams actually ship.

wcagwcag-2-2react

Dragging Movements: the WCAG 2.2 criterion hiding in your kanban board

A deep dive on WCAG 2.2 success criterion 2.5.7, Dragging Movements — what counts as essential, the five patterns that fail it, and how to add a single-pointer path without ripping out the drag.

September 22, 20268 min read

wcagwcag-2-2focus-management

Focus Not Obscured: the WCAG 2.2 criterion your sticky header keeps breaking

A practical guide to WCAG 2.2 success criterion 2.4.11, Focus Not Obscured (Minimum) — what it requires, the four UI patterns that break it, and the CSS that fixes them.

September 14, 20268 min read

pricingaccessibility-toolingvendor-evaluation

What accessibility tool pricing models tell you about the product

Per-page, per-seat, per-scan, retainer, token-based: how an accessibility vendor charges you reveals what the product is optimized to do. A buyer's guide to reading the pricing page.

September 7, 20268 min read

wcagwcag-2-2authentication

Accessible Authentication: the WCAG 2.2 criterion your login page probably fails

SC 3.3.8 bans cognitive function tests in login flows. Here is what that means for password fields, OTP inputs, CAPTCHAs, and security questions — with the code.

August 31, 20268 min read

reactfocus-managementspa

Focus management in single-page apps: what happens after the route changes

Client-side routing breaks the one thing browsers used to do for free — moving focus on navigation. Here is how to fix it in React, and how to announce it.

August 24, 202610 min read

remediationaccessibilitymarket

The audit is not the fix: closing the accessibility remediation gap

Teams buy accessibility audits and end up with a PDF nobody can action. Here is why findings stall in the backlog, and what changes when remediation ships as code.

August 17, 20268 min read

wcagwcag-2-2target-size

Target Size (Minimum): the 24-pixel rule that fails on real phones

A developer's guide to WCAG 2.2 success criterion 2.5.8, Target Size (Minimum) — what the 24px rule requires, the five exceptions, and how to fix it in CSS and JSX.

August 10, 20267 min read

reactdata-tableswcag

Accessible Data Tables in React: The Patterns That Actually Pass

Sortable columns, responsive layouts, and complex headers break screen readers in ways axe won't always catch. Here is how to build data tables that pass WCAG 2.2.

August 3, 20268 min read

ada-title-iieducationcompliance

Accessibility compliance for schools, colleges, and edtech

Public schools and universities are now on an ADA Title II clock, and edtech vendors inherit the pressure. Here is what actually applies to education and where source-code scanning fits.

July 27, 20268 min read

reactaccessibilitywcag

The Accessible Modal: Getting React Dialogs Right

Modals are where accessibility quietly breaks in most React apps. Here's what actually has to work — focus, escape, labeling, and the WCAG 2.2 rule nobody knew about.

July 20, 20269 min read

healthcarecomplianceada

Healthcare Web Accessibility: Section 504, ADA Title II, and What Changed in 2026

A practical guide for healthcare engineering teams on Section 504, ADA Title II, and the newly extended digital accessibility deadlines — and how to fix violations in code.

July 13, 20268 min read

ariaaccessibilitywcag

ARIA Best Practices: When to Use It, and When to Delete It

Most ARIA in the wild makes accessibility worse, not better. A practical guide to the five rules of ARIA, the traps in React, and how to know when to reach for a native element instead.

July 11, 20268 min read

accessibilityproductmarket

Accessibility as a product differentiator, not a compliance tax

Most teams treat accessibility as a cost center bolted on before a deadline. The teams that win treat it as a feature. Here is the difference and how to make the switch.

June 29, 20268 min read

fintechcomplianceeaa

Fintech Accessibility: What EAA and ADA Compliance Actually Require

A practical guide for fintech engineering teams on EAA, ADA, and AODA accessibility rules — what's in scope, what regulators expect, and how to fix it in code.

June 22, 20268 min read

keyboard-navigationfocus-managementwcag

Keyboard navigation: the accessibility work your mouse hides from you

Most keyboard accessibility bugs are invisible until you put the mouse down. Here are the focus patterns we look for in PR review and the code that fixes them.

June 15, 20269 min read

accessibility-toolingwcagdeveloper-workflows

The state of web accessibility tooling in 2026

A measured tour of the accessibility tooling landscape — linters, scanners, browser devtools, overlays, manual audits, and source-code fixes — and what each one actually catches.

June 8, 20269 min read

design-systemscolor-contrastwcag

Color contrast in design systems: why your tokens keep failing WCAG

Most design systems ship a color ramp that passes contrast in Figma and fails in production. Here is why it happens, and the token patterns that prevent it.

June 1, 20267 min read

business-caseaccessibilitycompliance

Writing a business case for accessibility that actually gets funded

Engineering leaders keep asking how to justify accessibility spend to finance. Here is the framework we walk customers through — cost avoidance, revenue protection, engineering time saved.

May 25, 20269 min read

reactformswcag

Accessible forms in React: patterns that survive code review

Most React forms fail accessibility checks for the same five reasons. Here are the patterns we look for in PR review — and why each one matters for real users.

May 18, 20269 min read

wcagwcag-2-2accessibility

The nine new WCAG 2.2 success criteria, decoded for engineers

A working developer's read on the nine success criteria WCAG 2.2 added on top of 2.1 — what they require, how they fail, and what the fix looks like in code.

May 11, 202610 min read

procurementvendor-evaluationaccessibility

How procurement teams actually evaluate accessibility vendors

The questions legal, IT, engineering, and design ops keep asking accessibility vendors — and how to tell a straight answer from a hand-wavy one.

May 4, 202610 min read

adaada-title-iiwcag

ADA Title II just hit its first deadline: what public-sector web teams should do this week

The April 24, 2026 ADA Title II web accessibility deadline has passed for state and local governments serving 50,000 or more. Here is what to do if you are behind.

April 28, 20268 min read

ci-cdgithub-actionswcag

Accessibility in CI/CD: catching WCAG violations before they hit main

Most a11y bugs are found after release, by customers or lawyers. Move the check left with GitHub Actions so broken contrast and missing labels never reach production.

April 20, 20268 min read

eaaeuropean-accessibility-actwcag

The European Accessibility Act one year in: what non-EU companies still get wrong

The EAA enforcement deadline passed in June 2025. Here is what US and Canadian teams selling into Europe are still missing, and what to do about it.

April 17, 20268 min read

accessibilityoverlayssource-code-fixes

Overlay widgets vs source-code fixes: what actually makes your site accessible

Accessibility overlays promise quick compliance. Source-code fixes address the root cause. Here is what engineering and procurement teams should understand before choosing an approach.

April 16, 20268 min read

reactjsxwcag

Seven WCAG violations hiding in your React components right now

Most React apps ship with the same accessibility bugs. Here are the seven WCAG 2.2 violations we see constantly in JSX codebases, with concrete code fixes for each one.

April 16, 20269 min read

aodawcagcompliance

AODA compliance and engineering teams: what Ontario businesses need to know

Ontario's accessibility law has teeth, and enforcement is tightening. Here is what engineering teams building web apps need to understand about AODA, WCAG 2.2, and the cost of doing nothing.

April 15, 20266 min read