
Planning for WCAG 3 without the panic
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.
Screen readers. Keyboards. A phone on one bar of signal on a county road. Search crawlers, AI agents, and the plaintiff’s scanner that found you first. Baclion audits, fixes, and monitors the code they all depend on.

Every tab below is generated from this page’s own code when we publish it. Nothing is a mock-up. Pick a reader.
What most design reviews check: hierarchy, color, and a clear next step.
What a screen reader announces, in order, from the top of this page to the illustration.
Every stop the Tab key visits before reaching the illustration. Each one shows a two-tone focus ring.
Estimated transfer time for this page, fully scrolled, at three connection speeds.
Weak rural 3G (0.4 Mbps, 400 ms round trip): about 9.2 s
Typical 3G (1.6 Mbps, 150 ms round trip): about 2.5 s
4G (9 Mbps, 60 ms round trip): about 0.6 s
Estimate: bytes ÷ bandwidth plus four round trips for connection setup. The heading and buttons render before the illustrations finish.
What an AI agent can extract from this page’s markup and structured data without looking at a single pixel.
{
"organization": {
"name": "Baclion",
"type": "ProfessionalService",
"location": "Bowling Green, KY",
"telephone": "(270) 791-9433",
"email": "info@baclion.com"
},
"page": {
"title": "Baclion | Web Accessibility & Performance, Kentucky",
"mainHeading": "Your website has readers you've never met."
},
"actions": [
{
"name": "Get a scoped quote",
"href": "https://baclion.com/contact/"
},
{
"name": "Take the 3-minute risk check",
"href": "https://baclion.com/risk-check/"
}
],
"offers": [
{
"service": "WCAG 2.2 Accessibility Audit",
"from": "$4800"
},
{
"service": "Source-Code Remediation",
"from": "$6500"
},
{
"service": "VPAT® & Accessibility Conformance Reports",
"from": "$1900"
},
{
"service": "Document & PDF Accessibility",
"from": "$9"
}
],
"more": "8 more services in structured data"
}Most teams design for the reader in front of a large monitor. The rest arrive through software, hardware, or a weak signal, and they all read the same markup.
Hear your page as a sequence of names, roles, and states. An unlabeled button is a silent one.
Move one focus stop at a time. A trap in a date picker ends the visit.
Read at 200% or 400%. Fixed-height boxes clip text and sticky headers hide the focus.
Wait for every script you ship. Heavy pages are slow to load and slower to answer a tap.
Index what your headings, links, and structured data say, not what your design implies.
Read screenshots, raw HTML, and the accessibility tree to book, buy, and compare on someone’s behalf.
Four numbers we keep on the wall. Each links to its primary source.
of the top one million home pages had detectable WCAG 2 failures in February 2026
WebAIM, The WebAIM Million (2026)detectable accessibility errors per home page on average in February 2026
WebAIM, The WebAIM Million (2026)of U.S. adults (more than 1 in 4) reported a functional disability in 2022
CDC, Disability and Health Data Now (Disability and Health Data System, 2022 BRFSS)digital accessibility lawsuits were filed in U.S. federal and state courts in 2025
UsableNet, 2025 Year-End Digital Accessibility Lawsuit ReportAccessibility, performance, tag governance, and machine readability usually live in four different vendors’ reports. They share root causes, so we work on them together.
Find, fix, and document the barriers that stop people using your site.
Make pages fast to respond and keep third-party code on a short leash.
Know everything you publish, and how machines read it.
Keep it fixed after launch day, and stop new barriers at the source.

A curb cut was built for wheelchairs and ended up serving strollers, suitcases, and delivery carts. Code works the same way. Give a button a real name and a screen reader announces it, voice control can click it, a crawler understands it, and an AI agent can press it. Remove an abandoned script and every visitor’s taps get faster while a privacy gap closes.
That is why we audit accessibility, performance, and third-party code in one pass, and fix the shared component instead of patching every page.

We don’t sell badges, seals, or a percentage score. You get a findings register tied to WCAG success criteria, recorded screen-reader walkthroughs, before-and-after measurements, and retest results your attorney, auditor, or procurement officer can actually read.
If a vendor tells you a script will make your site conformant overnight, ask them for the evidence. The FTC did.

Most regressions arrive on an ordinary Tuesday: a new carousel, a marketing tag, a redesigned checkout button. Baclion Watch scans weekly, tracks field performance, flags new third-party scripts, and puts a person on quarterly assistive-technology checks. Our CI gates catch the machine-detectable problems before they merge.
Federal accessibility dates for public entities and healthcare organizations. Counts verified November 1, 2026. See every date.
April 26, 2027
ADA Title II web and mobile app compliance date for state and local governments with a total population of 50,000 or more.
U.S. Department of Justice, Interim Final Rule, 91 FR 20902 (FR Doc. 2026-07663)
176days away
May 11, 2027
Section 504 web and mobile app compliance date for HHS-funded recipients with 15 or more employees.
U.S. Department of Health and Human Services, Interim Final Rule, 91 FR 25496 (FR Doc. 2026-09266)
191days away
April 26, 2028
ADA Title II web and mobile app compliance date for public entities with a total population under 50,000 and for special district governments.
U.S. Department of Justice, Interim Final Rule, 91 FR 20902 (FR Doc. 2026-07663)
542days away
Field notes on regulation, code, and the readers you can’t see. All articles.

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.

We’re a Kentucky company, an hour north of Nashville, close enough to sit in your conference room in Louisville, Lexington, or Owensboro and comfortable working with teams anywhere in the country. Kentucky has its own privacy law now, and its cities and counties have federal accessibility dates to meet. We know both.
1280 Fairway Street, Suite 200Send 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.