AI coding and accessibility

By @fifbuilds · Instagram

Source: https://www.instagram.com/reel/Dbd5KA0pXoe/?igsh=c2Nld3BpeHFvNjhx

AI generated summary of the linked source. Posted anonymously. Transcripts are published only for public links, never for uploads, documents or pasted text.

Your library

The AI link is plain markdown. Paste it into any assistant and it can read the whole public entry.

Summary

AI-generated "vibe coded" sites look right but often fail basic accessibility standards, breaking screen readers, contrast, and form labels. A fix exists: drop an ally.md file into your repo with WCAG rules baked in, then point your AI tool at it before it builds anything.

Core ideas

One context card plus 7 ideas

Optimized for looks, not access: AI coding tools prioritize visual output over semantic correctness, so accessibility gets stripped out by default.
Screen readers break silently: CTAs generated by AI often don't work with assistive tech, and nobody notices until a real user hits the wall.
Contrast fails WCAG: Color choices from AI tools frequently don't meet WCAG contrast requirements, even though they look fine visually.
Labels disconnect from inputs: Forms get built where the label isn't actually tied to its input field, which breaks accessibility tools that rely on that link.
Ally.md as a fix: A file similar to design.md, pre-loaded with WCAG rules, that you drop into your repo so your AI has accessibility context before it generates anything.
Vibe coding's blind spot: Anyone can build anything now, but the ease of building means nobody's checking for the pieces that don't show up in a quick visual review.
Double check the agent: The core discipline is still human oversight. AI output needs a review pass specifically for accessibility, not just function.

Quotes

“One of the most overlooked things AI is doing to technology is that it's making what we use less and less accessible.”
@fifbuilds

“These AI tools they're using to make them are optimized to make things look right, not read right.”
@fifbuilds

“So it's stripping broken accessibility by default.”
@fifbuilds

“Everyone can build everyone's chip and it's great, but be very careful.”
@fifbuilds

Resources

Links to the tools, products, repos or reading this entry mentions. Found by a web search of what the entry names, so you can go and use them.

A11Y.md
github.com
Open-source repo you drop in root, name reads as 'ally', enforces WCAG 2.2 rules on AI coding agents before they build UI.
WCAG (Web Content Accessibility Guidelines)
w3.org
The W3C standard for contrast, labels, and screen reader compatibility that AI-generated sites keep failing.
axe-core
github.com
Open source engine to automatically catch contrast and ARIA violations in generated code, the check-pass the piece argues for.
Vibe coding
arxiv.org
The AI-first coding style at the center of the piece, where speed of building outpaces checking for accessibility gaps.

Remix this knowledge

Turn this entry into something you can post. Pick a format and get a fresh, original rewrite.

Remixes are AI generated, original wording, and free to reuse.

Talk it through

Open a round table on this entry and argue with other people about what it means.

Start a round table

Drop your own

Paste any video, podcast or audio link and get the transcript, the core ideas and the quotes back in one pass.

Try Drop