- Home
- Skills
- Frontend & Web Apps
- Web Accessibility Auditor Fixer
Works with the AI Agents you already use
Web Accessibility Auditor Fixer
An accessibility audit against WCAG 2.2 AA: every barrier with its success criterion and who it blocks, a remediation plan, and fixes applied only after you approve them
$5
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
Web Accessibility Auditor Fixer
Example session with this skill installed
Audit this signup form for accessibility, target WCAG 2.2 AA. React + TS.
src/components/SignupForm.tsx
export function SignupForm({ onSubmit, error }: Props) {
return (
<div className="form">
<img src="/hero.png" />
<input placeholder="Email" />
<input type="password" placeholder="Password" />
<div className="btn" onClick={onSubmit}
style={{ color: '#9ca3af', background: '#e5e7eb' }}>Sign up</div>
<span style={{ color: 'red' }}>{error}</span>
</div>
);
}
Global CSS has *:focus { outline: none; }
- Read your context and instructions
- Compiled the web accessibility auditor
- Generated the image
Accessibility audit: SignupForm.tsx, target WCAG 2.2 AA
1. Scope
- In scope:
src/components/SignupForm.tsxas you pasted it, plus the global rule*:focus { outline: none; }. - Target: WCAG 2.2 Level AA.
Not visible to me: the Props type, the .form / .btn CSS, the page background behind the form, what hero.png shows, and what error contains. Any finding that depends on one of these is marked as an assumption, or listed under "Can't verify from the code".
2. What the component contains
| Element | Role exposed to assistive tech | Accessible name | Keyboard reachable |
|---|---|---|---|
<div className="form"> | none (generic) | none | n/a |
<img src="/hero.png"> | img | none (screen readers fall back to the file name) | n/a |
<input placeholder="Email"> | textbox | placeholder only (fallback naming, inconsistent across browsers) | yes |
<input type="password" placeholder="Password"> | textbox (password) | placeholder only | yes |
<div className="btn" onClick> | none (generic) | none (the text is there but it has no role) | no |
<span style="color: red"> | none, not a live region | n/a | n/a |
There are no landmarks, no heading, and no <form> element. That means pressing Enter in a field submits nothing.
3. Violation inventory
| ID | Issue | WCAG SC | Severity | Assistive-tech impact |
|---|---|---|---|---|
| A1 | *:focus { outline: none; } removes every focus indicator, app-wide, with nothing in its place | 2.4.7 Focus Visible (AA) | Blocker | Keyboard users can't see where focus is, on this form or anywhere else in the app |
| A2 | "Sign up" is a div with onClick: no role, no tabindex, no Enter/Space handling, no <form> | 2.1.1 Keyboard (A), 4.1.2 Name, Role, Value (A) | Blocker | Keyboard and switch users can't submit the form. Screen readers announce plain text, not a button. Voice control can't target it ("click Sign up" fails) |
| A3 | Inputs have no <label>. The placeholder is the only name and disappears as soon as the user types | 1.3.1 Info and Relationships (A), 3.3.2 Labels or Instructions (A), 4.1.2 Name, Role, Value (A) | Blocker | Screen readers may announce "edit text" with no name. Users with memory or cognitive impairments lose the field's purpose mid-entry |
| A4 | Button text #9ca3af on #e5e7eb has a contrast ratio of 2.05:1. Normal text needs 4.5:1 | 1.4.3 Contrast (Minimum) (AA) | Major | Low-vision users can't read the only action. It also looks disabled, but the inactive-component exemption doesn't apply because it isn't disabled |
| A5 | The error span isn't a live region and isn't linked to the inputs. The fields carry no aria-invalid | 4.1.3 Status Messages (AA), 3.3.1 Error Identification (A) | Major | When submit fails, nothing is announced. A screen reader user hears silence and doesn't know which field is wrong |
| A6 | Error text color: 'red' (#ff0000) is 4.0:1 on white (assumed background) | 1.4.3 Contrast (Minimum) (AA) | Major | Low-vision users may miss or misread the error |
| A7 | <img src="/hero.png" /> has no alt | 1.1.1 Non-text Content (A) | Major | Screen readers read out "hero.png" or the image path, which is noise if the image is decorative and a gap if it carries information |
| A8 | No autoComplete tokens, and the email field isn't type="email" | 1.3.5 Identify Input Purpose (AA) | Major | Autofill, password managers and symbol-based assistive tools can't recognise the fields. This hits users with motor and cognitive impairments hardest |
Advisory, not a failure: the form has no visible heading or accessible name. Nothing visual is missing its markup, so 1.3.1 isn't failed, but a named form (aria-labelledby pointing at a heading) makes screen-reader navigation much easier. I'll only add it if you want it (see F9).
Can't verify from the code
- 2.5.8 Target Size (Minimum): the
.btnpadding and size aren't shown, so I can't check the 24x24 CSS px minimum. - 1.4.11 Non-text Contrast: input borders come from
.formCSS I can't see.
3.3.2 for the password: if there are password rules (length, character classes), they have to be stated before submit. I don't know if there are any.
- 1.4.10 Reflow / 1.4.4 Resize Text: these depend on the layout CSS.
- A6 depends on the page background: I assumed white.
4. Fix plan
F1 (A1). Global stylesheet: restore focus visibility
- Delete
*:focus { outline: none; }. - Add
:focus-visible { outline: 2px solid #1d4ed8; outline-offset: 2px; }. :focus-visiblekeeps rings off mouse clicks, which is usually whyoutline: nonewas added.#1d4ed8measures 6.7:1 against white and 5.4:1 against the button's#e5e7eb.
F2 (A2). SignupForm.tsx: real form, real button
- Change the outer
<div className="form">to<form className="form" onSubmit={handleSubmit}>. - Replace the
div.btnwith<button type="submit" className="btn">Sign up</button>. handleSubmitcallse.preventDefault()and thenonSubmit.- Result: a native button gets focus, Enter/Space and the button role for free, and Enter now submits from either field.
F3 (A3, A8). SignupForm.tsx: labels and input purpose
const emailId = useId();
const passwordId = useId();
<label htmlFor={emailId}>Email</label>
<input id={emailId} name="email" type="email" autoComplete="email" />
<label htmlFor={passwordId}>Password</label>
<input id={passwordId} name="password" type="password" autoComplete="new-password" />
- Drop the placeholders, since the labels replace them.
new-passwordtells password managers to offer a generated password, not to fill in a stored one.
F4 (A4). SignupForm.tsx: button contrast
- Change the text colour from
#9ca3afto#4b5563and keep the#e5e7ebbackground. That gives 6.1:1. - Better still, move both colours into
.btnso the inline style goes away.
F5 (A5). SignupForm.tsx: announce the error and link it to the fields
const errorId = useId();
<span id={errorId} role="alert" className="form-error">{error}</span>
- The
spanstays rendered even whenerroris empty, so the live region already exists when text arrives. That makes the announcement reliable. - On both inputs, add
aria-invalid={error ? true : undefined}andaria-describedby={error ? errorId : undefined}.
F6 (A6). SignupForm.tsx: error colour
- Change
'red'to#b91c1c. That's 6.5:1 on white.
F7 (A7). SignupForm.tsx: image alternative
- If the hero image is decorative, use
alt="". - If it carries information (text in the image, a product shot that matters), use a short
altdescribing it.
I need your answer before I apply this one.
F9 (advisory, optional). SignupForm.tsx: heading and form name
- Add a visible heading, e.g.
<h2 id={titleId}>Create your account</h2>, andaria-labelledby={titleId}on the<form>. - The heading level depends on the page outline, which I can't see.
5. Risk flags
F1 is global. Focus rings will show on every focusable element in the app, not just this form. That's the point of the fix, but expect visual-review comments and possible clashes with components that draw their own focus style.
F2 changes the handler contract. Right now onSubmit gets a MouseEvent<HTMLDivElement> from onClick. After F2 it's called from a form submit handler. If Props['onSubmit'] is typed against the mouse event, or relies on it, the type has to change and so do the call sites. Note also that the inputs are uncontrolled and nothing passes their values to onSubmit today. I won't change that unless you ask, but you'll want to know before wiring this up.
F2 restyles the button. A <button> comes with browser default border, padding and font, which a div didn't have. .btn may need font: inherit; border: 0; to look the same.
F3 changes the layout. Visible labels add height to the form. If the design requires placeholder-only fields, the accessible alternative is a floating-label pattern, not aria-label (which fixes 4.1.2 but still fails 3.3.2).
F3 required fields. If the fields are required, adding required turns on native browser validation popups, which is a behaviour change. I've left it out unless you want it.
F5 marks both fields invalid. error is a single string, so F5 sets aria-invalid on both fields whenever any error is present. If your errors are field-specific ("email already in use"), the error should be split per field so only the guilty input is marked. That would change Props.
6. Approval needed
I haven't changed anything yet. Tell me which fixes to apply ("apply all", or a list like "F1-F6"), and answer these so the fixes are correct:
- Is
hero.pngdecorative, or does it carry information? (F7) - What is the
Propstype, in particular the signature ofonSubmit? (F2) - Which file holds the global
*:focusrule, and was it added on purpose (e.g. to hide rings on mouse click)? (F1) - Is the page background behind the error white? (F6)
- Is
errorever specific to one field? (F5) - Do you want the optional heading, F9?
Once you approve, I'll send back the edited SignupForm.tsx and the CSS change, a per-file summary mapping each edit to its WCAG criterion, and a re-audit marking each item A1-A8 as resolved, remaining or not verifiable.
SignupForm.tsx
PNG · 1536×1024
Example file from a real run - the skill writes it into your workspace.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Audits web components and pages for accessibility barriers against WCAG 2.2 (AA by default) and fixes them once you approve. It looks at what assistive technology actually gets: roles, accessible names, labels, keyboard reachability, focus visibility, contrast, error announcements, alt text and semantic structure.
What it does
You get the scope, a table of every element with the role and name it exposes and whether a keyboard can reach it, then a violation inventory where each item names the WCAG success criterion, the severity and who it blocks. A remediation plan gives the fix for each, and a short list of questions covers what the code can't settle (is this image decorative? what's behind the form?). It stops for your approval, applies only the approved fixes, and re-audits each item as resolved, remaining or not verifiable.
Try it first
Paste a form or point it at a component and say "audit this for accessibility, WCAG 2.2 AA". Check that every finding cites a success criterion and that nothing is edited before you approve.
What it needs
Read access to the components and styles, and write access for the fixes you approve. React, Vue, Svelte, Angular and plain HTML. No network access and no API keys.
It audits code, not a rendered page, so contrast against a background it can't see, and anything set at runtime, are marked as assumptions or as not verifiable. It doesn't replace testing with a screen reader or with disabled users; it tells you which checks to do by hand. Its scope is what you point it at, so a global style problem is fixed where it sits only if that file is in scope. Edits wait for your approval.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 28 days ago
Permissions
Browser is declared because the skill reads Lighthouse, axe-core and Pa11y results; it does not drive a browser itself, and audits the code you point it at.