iiinova — where your digital self keeps evolving

AAArdvark @aaardvarka11y.bsky.social · 02/10/2026

Got a component nobody wants to look at too closely? Send it to Natalie for Roast My Component: tested live with a keyboard and screen reader. Anonymous, just a link, don't tidy it up. Closes Mon Oct 19th. natalie@a20y.com Livestream on the 21st.

000

AAArdvark @aaardvarka11y.bsky.social · 01/10/2026

Start an hour-long scan, then notice pages are missing. Until now you waited it out and scanned again. You can now cancel a running scan from the AAArdvark dashboard. Pages it already checked keep their results, and it won't mark anything fixed on pages it never reached.

000

AAArdvark @aaardvarka11y.bsky.social · 25/09/2026

24 hours of free accessibility talks, and every one is on YouTube now. Thank you @inclusivedesign24.bsky.social and every speaker. We were glad to support #id24 this year. Start with the ethics framework panel and Neha Pandit on AI agents: bit.ly/4Avfdyv

000

AAArdvark @aaardvarka11y.bsky.social · 23/09/2026

A page can score 100 on an accessibility audit and still be unusable with a keyboard. Today, 1pm PT: how scores get made, what they can't see, and what an honest one has to do differently. Live, including on our own tool. youtu.be/ucS9QQAY82o

001

AAArdvark @aaardvarka11y.bsky.social · 18/09/2026

Roast My Component is open through October 5th. The test Natalie runs: Tab to it, work it with the keyboard only, land on it with a screen reader, then leave it and see where focus went. Want to watch her run it on yours? Send a link, stay anonymous. natalie@a20y.com

000

AAArdvark @aaardvarka11y.bsky.social · 16/09/2026

A WordPress agency owner told us the homepage accessibility report is what gets his prospects to sign. Not the pitch, the report. "Your site has issues" gets a nod. A list of issues on their own homepage gets a decision. Show them first. bit.ly/46QW1gD

000

AAArdvark @aaardvarka11y.bsky.social · 11/09/2026

Roast My Component: send a component you're not sure about, and Natalie tests it live with a keyboard and a screen reader on stream. Anonymous unless you want the credit. All it costs is a link. natalie@a20y.com, submissions close Sept 21.

000

AAArdvark @aaardvarka11y.bsky.social · 09/09/2026

Having captions and having usable captions are two different claims, and only one of them helps anybody. Today 1pm Pacific we turn the automatic captions on over our own past streams and score them live against a real quality standard. youtu.be/TqXv0BErl8c

000

AAArdvark @aaardvarka11y.bsky.social · 04/09/2026

Every site in AAArdvark now has an Accessibility Score, and a clean automated scan tops out at a B. That ceiling is deliberate. Scans catch part of what matters, so reviewing and manual testing lift it. Progress, never compliance. bit.ly/4A1YGC6

000

AAArdvark @aaardvarka11y.bsky.social · 28/08/2026

A plain HTML site serves its homepage at / and /index.html. An IIS one at / and /default.aspx. Add a trailing slash or a utm parameter and one page is five URLs. AAArdvark now treats them as one page, so you stop scanning, reviewing, and paying for the same page twice.

000

AAArdvark @aaardvarka11y.bsky.social · 26/08/2026

Most modal dialog code is doing work the browser already does for free. The advice to hand-write a focus trap was right when it was written. It's out of date now. Today 1pm Pacific we build one from scratch, and the best moment is a deletion. youtu.be/SFqczuXXkpQ

000

AAArdvark @aaardvarka11y.bsky.social · 19/08/2026

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.

000

AAArdvark @aaardvarka11y.bsky.social · 12/08/2026

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. youtu.be/cd82ZiwmY9o

000

AAArdvark @aaardvarka11y.bsky.social · 05/08/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 31/07/2026

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. bit.ly/4aAAoVn

000

AAArdvark @aaardvarka11y.bsky.social · 29/07/2026

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. bit.ly/4fnC2f3

000

AAArdvark @aaardvarka11y.bsky.social · 25/07/2026

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: bit.ly/4fxglZ0

010

AAArdvark @aaardvarka11y.bsky.social · 22/07/2026

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. bit.ly/4aAAoVn

010

AAArdvark @aaardvarka11y.bsky.social · 15/07/2026

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. youtu.be/dj2mbNkEACY

000

AAArdvark @aaardvarka11y.bsky.social · 13/07/2026

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. bit.ly/4aAAoVn

000

AAArdvark @aaardvarka11y.bsky.social · 08/07/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 08/07/2026

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

010

AAArdvark @aaardvarka11y.bsky.social · 02/07/2026

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. bit.ly/4aAAoVn

000

AAArdvark @aaardvarka11y.bsky.social · 01/07/2026

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: bit.ly/4g5Ty8q #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 01/07/2026

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

011

AAArdvark @aaardvarka11y.bsky.social · 25/06/2026

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

010

AAArdvark @aaardvarka11y.bsky.social · 23/06/2026

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.

000

AAArdvark @aaardvarka11y.bsky.social · 18/06/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 17/06/2026

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: bit.ly/3QH8AqL #a11y

bit.ly

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...

000

AAArdvark @aaardvarka11y.bsky.social · 16/06/2026

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

020

AAArdvark @aaardvarka11y.bsky.social · 11/06/2026

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

010

AAArdvark @aaardvarka11y.bsky.social · 09/06/2026

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

020

AAArdvark @aaardvarka11y.bsky.social · 04/06/2026

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

010

AAArdvark @aaardvarka11y.bsky.social · 03/06/2026

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. bit.ly/3PC9VPk

000

AAArdvark @aaardvarka11y.bsky.social · 02/06/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 27/05/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 26/05/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 21/05/2026

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

001

AAArdvark @aaardvarka11y.bsky.social · 20/05/2026

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. bit.ly/4tF0f4e

000

AAArdvark @aaardvarka11y.bsky.social · 19/05/2026

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

000

AAArdvark @aaardvarka11y.bsky.social · 18/05/2026

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: bit.ly/4tF0f4e #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 16/05/2026

Semantic HTML isn't the whole answer. But it's still the first answer. It works for the 70% of UI that maps cleanly to existing elements. Comboboxes, tree views, custom video players? You'll need ARIA. Both arguments are right. The mistake is treating either as the universal answer. #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 13/05/2026

Nobody's complained about your accessibility? That's not a good sign. That's the warning sign. Blind shoppers abandon 23% of e-commerce transactions. They don't file tickets. They go to a competitor. That's $6.9B in lost revenue every year. Silence isn't satisfaction. It's churn you can't see.

010

AAArdvark @aaardvarka11y.bsky.social · 12/05/2026

A11y Tip of the Week: Use a button to do something. Use a link to go somewhere. Form submit, menu toggle, modal trigger? Button. New page, anchor jump, external URL? Link. A div styled to look like a button isn't a button. Keyboard users can't reach it. Screen readers don't announce it. #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 06/05/2026

Live today: ARIA Deep Dive Part 3 - states and properties in action. aria-expanded, aria-pressed, aria-current, the stale-state bug, and how to fix all of it. Demos in NVDA and VoiceOver. bit.ly/3P35AEr #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 05/05/2026

A11y Tip of the Week: aria-expanded goes on the button, not the panel. The button is the control. The panel is what gets shown or hidden. Screen readers announce the state on the trigger - that's where the attribute belongs. Tab to your menu button. Does it announce "collapsed"? #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 05/05/2026

Menu button says "collapsed" - while the menu is wide open. A super common ARIA bug in the wild. Wed 1pm PT: Natalie wraps the ARIA Deep Dive with Part 3 - states and properties, live demos in NVDA and VoiceOver. bit.ly/3P35AEr #a11y

000

AAArdvark @aaardvarka11y.bsky.social · 29/04/2026

The same six accessibility issues have topped WebAIM's annual list for six straight years. 94.8% of top sites still fail. Low contrast, missing alt text, missing form labels, empty links, empty buttons, missing document language. None are hard to fix. Most teams never check. #a11y

010

AAArdvark @aaardvarka11y.bsky.social · 28/04/2026

A11y Tip of the Week: Respect motion preferences. Two underused tools: the @media (prefers-reduced-motion) CSS query, and window.matchMedia() in JavaScript - which catches autoplay, parallax, and anything CSS can't reach. Test by turning reduced motion on in your OS settings. #a11y

000