An agency told us our sitemap import was broken across their client sites. The fix was in production 1 hour 47 minutes later. Every a11y platform has bugs. What you're really buying is what happens in the two hours after you find one.

Is it time to get ready for WCAG (Web Content Accessibility Guidelines) 3? The explainers are more confident than the spec is. In the draft, the conformance section is labeled Exploratory and the Bronze threshold says "to be determined." Today 1pm Pacific we read it. https://youtu.be/cd82ZiwmY9o

The most important document on your site might not be a web page. I might be a PDF, and it usually sits outside a website accessibility check. We're building PDF scanning into AAArdvark: checked against PDF/UA, tracked like any other issue. Coming soon. #a11y

Last day. Circle enrollment closes tonight, July 31. From member Graham: "Natalie brings a gentle, generous presence to the Circle... a safe space to learn, ask questions, and grow with confidence." Kicks off Aug 7. https://bit.ly/4aAAoVn

Everyone's adding alt text for the AI tools now. It was always for people first, and doing it well is more art than checkbox. Live today at 1pm Pacific: same image, five different alt texts, and how to pick the right one. https://bit.ly/4fnC2f3

Ask an AI coding assistant to fix an accessibility issue and you'll often get confident, wrong advice. We built a way for AAArdvark to feed your AI assistant real WCAG fix guidance, so it stops guessing. Private beta, requesting testers: https://bit.ly/4fxglZ0

The hardest accessibility questions are the specific ones - why is THIS table flagging, is THIS widget okay to ship. The AAArdvark Circle works through them with Natalie every month. New cohort starts Aug 7, enroll by July 31. https://bit.ly/4aAAoVn

A scanner flags accessibility issues in seconds. Fixing them is where teams get stuck. Today at 1pm Pacific: we hand an AI agent a broken site plus real accessibility context and watch it fix issues live, then rescan to prove it. https://youtu.be/dj2mbNkEACY

The AAArdvark Circle is a small membership community for people serious about getting accessibility right. Every month: a mastermind with Natalie + an open Q&A on whatever you're stuck on. New cohort starts Aug 7, doors close July 31. https://bit.ly/4aAAoVn

This Friday: our Circle mastermind on using AI in accessibility work without breaking it. AI is a brilliant assistant and a terrible author. It drafts; you finish. We'll show you exactly where that handoff happens. Join by Friday to be there live. a20y.com/circle

A11y Tip of the Week: The best skip link is one everybody can see - a small, always-visible link in the top-left. When it has to hide until focus, use clip-path in 2026, not the old off-screen hacks. And give the target tabindex -1 so focus actually moves there. #a11y

AI is already in your accessibility workflow. The skill is knowing where it stops and you take over. That's our July 10 Circle mastermind: Using AI in Accessibility Work (Without Breaking It). New cohort's open, kicks off Aug 7, but join by July 10 to be in the room live. https://bit.ly/4aAAoVn

Accessibility overlays promise instant compliance from one line of code. Do they actually work? Today we install a real overlay on a test site and test it by keyboard and screen reader. What it fixes, what it misses, and what the 2026 lawsuit data says. Watch live: https://bit.ly/4g5Ty8q #a11y

A11y Tip of the Week: "Click here" tells a screen reader user nothing. Many navigate by pulling up a list of every link on the page, with no surrounding text. A dozen links that all read "Read more" are useless there. Make each link describe where it goes on its own. #a11y

Finding accessibility issues was solved years ago. Fixing them wasn't. A scanner hands you a list and walks off. We just added plain-language fix guidance for more failure types in AAArdvark: what it means, who it affects, how to fix it, right next to the issue. a20y.com

A11y Tip of the Week: reach for aria-label last. A control's name should be the text people can see. Visible text first, an associated visible label next, aria-label only as a fallback. It's hidden from sighted users and drifts out of date the moment the visible label changes.

A scan that fails with no reason is just frustrating. Now when a first scan fails in AAArdvark, the card tells you exactly why, in plain language - page not found, server blocked the scanner. So you know whether to fix the URL or whitelist us, instead of guessing. Try it free: a20y.com #a11y

Tabs look simple, so why do so many trap keyboard users and lose screen readers? Today we build accessible tabs from scratch and test them live with a screen reader, using the ARIA tabs pattern. Watch live: https://bit.ly/3QH8AqL #a11y

Building Accessible Tabs From Scratch

Tabs look simple. A row of labels, a panel of content, click to switch. So why do so many tab components trap keyboard users, confuse screen readers, or do n...

bit.ly

A11y Tip of the Week: make tap targets big enough to actually tap. The Web Content Accessibility Guidelines set the floor at 24x24 CSS pixels; 44x44 is comfier. Pad small icons, space links apart. Test it one-handed, thumb only - keep mis-tapping? So do your users. #a11y

121 companies were sued for accessibility last month. All of them had an accessibility widget installed. (UsableNet, May 2026) A widget can't fix your code. Testing with a keyboard and a screen reader can. #a11y

A11y Tip of the Week: Don't disable zoom. user-scalable=no and maximum-scale=1 in your viewport meta tag block pinch-to-zoom - the thing low-vision users rely on to read your text. Delete them. Fails WCAG 1.4.4 Resize Text. #a11y

Ever had an accessibility issue flagged but couldn't find the element on the page? It's often hiding in an iframe or shadow DOM. AAArdvark now flags when an issue lives inside one, so you know exactly where to look. You can't fix what you can't find. #a11y

A clean scan doesn't mean an accessible site. Scanners catch about a third of the issues real users hit. Today 1pm PT: we pass the scanners live, then break the illusion with keyboard and screen reader testing, and share the workflow that catches what tools miss. https://bit.ly/3PC9VPk

A11y Tip of the Week: End your alt text with a period. Most screen readers don't pause between the description and the next thing on the page, so without it the alt text runs straight into the following heading. A period gives the listener a clean stop. #a11y

Scanners flag "aria_required_parent" and walk away. That gap is where a11y work falls apart. We just shipped 40+ new plain-language guidance entries inside AAArdvark - covering the long tail of IBM, Axe, and HTMLCS rules nobody explains. Scan results, finally usable. a20y.com

A11y Tip of the Week: click the label. Did the input focus? If nothing happens, the label isn't actually connected to the input. Screen readers can't link them. The hit area shrinks to the checkbox itself. One-line HTML fix. Test every form. #a11y

It's GAAD (Global Accessibility Awareness Day). Three things you can ship today: 1. Visible focus styles on every interactive element 2. Real alt text on your top three pages 3. A free scan to see what else is hiding GAAD is one day. What you ship today helps users every day after. a20y.com #a11y

Tomorrow is GAAD (Global Accessibility Awareness Day). Today at 1pm PT we're going live: why accessibility helps every user. The Persona Spectrum, the curb cut effect, and three things you can do this week. Live demos of captions, voice control, and keyboard nav. https://bit.ly/4tF0f4e

A11y Tip of the Week: a 5-min keyboard-only test on your own site. Hands off the mouse. Tab through. Try your most common user task. Watch where focus disappears, where you get trapped, where you can't reach. It's GAAD (Global Accessibility Awareness Day) week. Small, doable, today. #a11y

GAAD (Global Accessibility Awareness Day) is Thursday, May 21. We're marking it with a free livestream Wed 5/20 at 1pm PT - the case that accessibility benefits every user, every day. Curb cut effect, persona spectrum, live demos. Save a spot: https://bit.ly/4tF0f4e #a11y