What changed, what it means for your code, and what to do this week. Every statistic links to its primary source, and every article carries the date it was written.
WCAG 3.0 is still a draft, and W3C says it is years from finished. What to do now so today's accessibility work carries over.
Old microsites, staging servers, and PDF archives still carry your name. How to find them and decide what to keep, fix, or retire.
Tags that fire before a visitor chooses undercut your consent banner. How to test for it in an afternoon, and how to fix it.
If you sell to consumers in the EU, the European Accessibility Act may apply to you. Scope, enforcement, EN 301 549, and first steps.
Screen readers and AI agents read the same accessibility tree. How to inspect it, and the fixes that help both readers at once.
A demand letter starts a technical clock next to the legal one. What to preserve, test, fix, and hand your attorney in three days.
DOJ and HHS each added a year to their web rules, and the standard is unchanged. Here is a quarter-by-quarter plan for that year.
Reviewers trust ACRs that are specific and honest. How to choose the edition, gather evidence, write useful remarks, and avoid red flags.
Long tasks that hurt INP also delay focus moves and screen reader announcements. One set of fixes helps both groups of users.
Automated checks catch many issues by volume but miss judgment calls. How to design CI checks and the manual layer that covers the rest.
Each third-party script costs bytes, main-thread time, privacy exposure, and accessibility. How to measure, budget, load, and govern them.
Not every PDF deserves remediation. A triage framework for remediating, converting to HTML, or retiring documents, with source-level fixes.
Kentucky's privacy law is in effect. A technical checklist for tags, data flows, notices, opt-outs, request forms, and vendor contracts.
The six new WCAG 2.2 A and AA criteria, ranked by user impact and cost, with code for sticky headers, targets, autofill, and one-time codes.
The FTC order targeted claims, not overlays. What injected scripts can't fix, how to remove one safely, and what to tell your board.
Send a link and a sentence about your deadline. You will hear back from a person within one business day, usually with a short list of questions and a proposed scope.
