Yadhu AU | A11yRemedy

I build A11yRemedy: WCAG 2.2 scans for web agencies, with fix code and white-label reports. Free scan below. Also GhostPrompter.

[Yadhu AU | A11yRemedy @auyadhu]

I'm building A11yRemedy: weekly WCAG 2.2 scans for web agencies, with fix code for your developer and reports under your own logo.

Free scan, no account: https://t.co/jjKFIZWPdX

[Yadhu AU | A11yRemedy @auyadhu]

Website accessibility is like a gym membership. Easy to sign up, harder to keep showing up six months later.

[Yadhu AU | A11yRemedy @auyadhu]

@arixanxim @luigismustach3 Yep, exactly! Screen readers already announce that it's a graphic/image, so specifying 'GIF of...' or just describing the motion at the end (e.g., '[Description] (Animated GIF)') avoids redundancy while keeping the distinction clear

[Yadhu AU | A11yRemedy @auyadhu]

@MarcoAlmeidaPT I'd keep the visitor's choice once they've picked one, and only follow the OS when they haven't. A sudden switch mid-visit can be disorienting, especially for someone using a magnifier or halfway through a form. A visible match-system option keeps it clear.

[Yadhu AU | A11yRemedy @auyadhu]

@jlipinski_ Nice. Curious how it handles fixes that need context, like alt text or link text that says 'click here'. The code change is easy, but the right wording depends on the page. Does it flag those for a human instead of guessing?

[Yadhu AU | A11yRemedy @auyadhu]

@pierrickselas Grey text is the classic one. If it's placeholder or helper text, darkening it to about #595959 on white usually passes 4.5:1 without changing the look much. Worth tabbing through the builder too, since drag-and-drop UIs often trap keyboard focus.

[Yadhu AU | A11yRemedy @auyadhu]

@amasen02 Self-hosted makes sense for small sites. How do you handle pages behind a login or forms that only appear after an action? That's where a lot of issues hide, and it's the hardest part of monitoring to get right.

[Yadhu AU | A11yRemedy @auyadhu]

@faisalahammadwp The pattern I keep seeing: sites pass at launch, then new issues come in through the content editor. Theme markup is where widgets can't help: heading order, button vs link, form labels. Fixed once in the template, it clears dozens of pages.

[Yadhu AU | A11yRemedy @auyadhu]

6/9

Days 76–150: FIX.

Don't fix the same issue page by page.

Start with template-level fixes.

Then address PDFs, forms, and third-party tools.

Ask vendors for accessibility documentation.

Fixing root causes can reduce duplicated work.

[Yadhu AU | A11yRemedy @auyadhu]

1/9

The first ADA Title II web deadline for state and local governments serving 50,000+ people is about 180 days away: April 26, 2027.

If your agency works on government websites, here's a practical 180-day plan to get started.

🧵

[Yadhu AU | A11yRemedy @auyadhu]

5/9

Days 61–75: PRIORITIZE.

Start with what residents need to do:

→ Pay a bill
→ Find a public meeting
→ Submit a form
→ Report a problem
Prioritize barriers that prevent people from accessing essential services.

[Yadhu AU | A11yRemedy @auyadhu]

We built A11yRemedy for agencies and freelancers who look after client sites. It scans each site, groups issues by root cause, shows the code fix, and sends white-label reports under your own name.

Automated scans find only about 30 to 57% of WCAG issues, so a human review still matters. It's a way to catch the rest sooner.

Free scan, just a URL: https://t.co/posNpnMPva

[Yadhu AU | A11yRemedy @auyadhu]

@rubisinghpanwar Good list. One thing worth adding: 10 minutes on a real phone with VoiceOver or TalkBack turned on. Swipe order and unlabelled icon buttons show up fast, and automated checks miss a lot of that on mobile.

[Yadhu AU | A11yRemedy @auyadhu]

@tiffrentamine Nice process. Stark covers contrast and target size well. A keyboard-only run and a few minutes with VoiceOver usually catch the rest, like focus order and unlabelled icons, since automated checks find only about 30 to 57% of WCAG issues.

[Yadhu AU | A11yRemedy @auyadhu]

@RoyGaTaH Agree. The other common miss on restaurant sites is the menu posted as an image or scanned PDF. Screen readers can't read it and it doesn't zoom well on phones. Real text at 4.5:1 contrast fixes both.

[Yadhu AU | A11yRemedy @auyadhu]

@AlexDmzz Nice touch on focus stopping it. Does the Pause button keep an accessible name and switch to a Play label once paused? That's an easy one to miss on marquees, and screen reader users rely on it.

[Yadhu AU | A11yRemedy @auyadhu]

@MythiliRaju5 @stevejonesdev @danielhayesmith Agree on wiring it in early. Worth knowing the limit though: automated checks find about 30 to 57% of WCAG issues. Contrast they handle well. Keyboard order and focus behaviour mostly need a quick manual Tab pass on top.