accessible-authentication
Skill0 starsChanged 29 days agoMITView on GitHub
Use when building or reviewing a login, sign-up, password reset, or two-factor step, when paste is blocked, when a password manager will not fill the form, or when a CAPTCHA or code entry stands between a user and their account.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- smukh/a11y-agent-skillstheir own version, first seen Sep 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- smukh/a11y-agent-skills★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessible-formsSkill
- accessible-nameSkill
- accordion-disclosureSkill
- audit-componentSkill
- carouselSkill
- charts-and-datavizSkill
- combobox-autocompleteSkill
- data-tableSkill
- email-html-accessibilitySkill
- fix-color-contrastSkill
- forced-colors-and-dark-modeSkill
- headings-and-landmarksSkill
- keyboard-focusSkill
- live-regionsSkill
- media-captionsSkill
- menu-buttonSkill
- modal-dialogSkill
- motion-and-animationSkill
- page-title-and-languageSkill
- pagination-and-searchSkill
- pointer-and-gesturesSkill
- predictable-contextSkill
- progress-and-loadingSkill
- screen-reader-test-planSkill
- semantic-htmlSkill
- skip-linksSkill
- svg-and-iconsSkill
- tabsSkill
- tooltip-popoverSkill
- triage-automated-resultsSkill
- wcag22-new-criteriaSkill
- zoom-reflow-text-spacingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 125
If you must time out — a bank, a shared terminal — preserve what the user typed and offer it back after re-authentication, which is the …
- Distinctive: line 177
Prefer passkeys, which are both stronger and free of a cognitive test.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accessible authentication
Criteria: SC 3.3.8 Accessible Authentication (Minimum), SC 3.3.9 Accessible Authentication (Enhanced), SC 1.3.5 Identify Input Purpose, SC 3.3.1 Error Identification, SC 2.2.6 Timeouts
Authentication is a cognitive function test in disguise: it asks a user to remember a password, transcribe a code, or solve a puzzle. WCAG 2.2 accepts that you may ask, but requires that a user who cannot do it still has a way in. The mistake that costs the most is blocking paste "for security" — it removes the one mechanism most people with cognitive disabilities rely on.
When to use
- "I can't paste into the password field." / "My password manager won't fill it."
- Building or reviewing sign-in, registration, password reset, or a two-factor step.
- A CAPTCHA, puzzle, arithmetic challenge, or "enter characters 3, 7 and 11" gates access.
- Reviewing a request to add
onpaste="return false"orautocomplete="off". - A one-time code arrives by email or SMS and the field will not accept the whole value.
Procedure
- Name the cognitive function test. Memory (a password or PIN), transcription (typing a code you read elsewhere), and puzzle-solving are tests. Under SC 3.3.8 (Level AA, new in 2.2) a test is permitted only if at least one of these is true — an alternative method without a cognitive test, a mechanism that assists completing it, or the test is object recognition or personal content the user supplied. SC 3.3.9 (Level AAA) removes the object-recognition and personal-content exceptions, so at AAA even "pick the photo you uploaded" needs an alternative. Allowing a password manager to fill the field is a mechanism: the user no longer has to recall anything.
Never block paste, copy, or the password manager. A paste handler that cancels the event,
draggable="false", oruser-select: noneon the field makes the task impossible for someone using a manager.<!-- Fails SC 3.3.8 — paste is cancelled and the code is split into six boxes, so neither a paste nor autofill can fill it --> <form> <input type="password" name="pw" autocomplete="off" onpaste="return false" oncopy="return false"> <div class="otp" onpaste="return false"> <input maxlength="1" inputmode="numeric" aria-label="Digit 1"> <input maxlength="1" inputmode="numeric" aria-label="Digit 2"> <input maxlength="1" inputmode="numeric" aria-label="Digit 3"> </div> </form>Keep a code in one field. Splitting a code across per-character boxes breaks
autocomplete="one-time-code", breaks paste, and turns one edit field into six for a screen reader. Use one input, allow paste, and constrain it in the right way —type="text"withinputmode="numeric", nottype="number".<!-- Passes SC 3.3.8 — the manager can fill, paste is allowed, one field --> <form method="post" action="/login"> <label for="user">Email</label> <input id="user" name="email" type="email" autocomplete="username" required> <label for="pw">Password</label> <input id="pw" name="password" type="password" autocomplete="current-password" required aria-describedby="pw-help"> <p id="pw-help">Your password manager can fill this field.</p> <button type="submit">Sign in</button> </form> <label for="code">6-digit code</label> <input id="code" name="code" type="text" inputmode="numeric" autocomplete="one-time-code" pattern="[0-9]{6}" maxlength="6">Identify the purpose of every credential field (SC 1.3.5). The
autocompletetoken is what tells browsers and assistive tech what the field is, and it is what makes autofill work:Field autocompleteusername or email usernameexisting password current-passwordnew password new-passwordone-time code one-time-codeone-time PIN one-time-codeautocomplete="on"is not a value that helps anyone, andautocomplete="off"on a login field is both ineffective and hostile.- Offer an alternative path. Passkeys or WebAuthn, a magic link, or an emailed code let a user who cannot complete the test still authenticate. Biometric or device-PIN unlock is not a cognitive function test. Do not make the password the only route.
Make failures identifiable (SC 3.3.1). A rejected credential must produce a text message tied to the field, mark the field
aria-invalid="true", and move focus so the message is reached. "Invalid input" identifies nothing; keep the username so the user is not asked to re-enter it.<label for="pw">Password</label> <input id="pw" type="password" autocomplete="current-password" aria-invalid="true" aria-describedby="pw-err"> <p id="pw-err" role="alert"> That password did not match. Try again, or <a href="/reset">reset your password</a>. </p>Warn before a session times out, and let it be extended (SC 2.2.6, AAA). A timeout the user is not warned about loses work, and for someone typing slowly with a switch or speech input it loses work every time. The criterion asks for warning, and for the ability to continue the activity for at least 20 hours without re-authenticating. Prefer to extend the session over warning at all.
// Warn with time to act, and make the extension a real button - not only a // modal that steals focus, and never a silent redirect to the login page. sessionWarning({ secondsLeft: 120, onExtend: () => refreshSession() });If you must time out — a bank, a shared terminal — preserve what the user typed and offer it back after re-authentication, which is the same as SC 3.3.7 Redundant Entry seen from the other side.
Verify
Automated tools do not test paste or autofill. Do these by hand.
| Do this | Passing looks like | Criterion |
| Paste into password with Ctrl/Cmd+V and with the context menu | the value appears | 3.3.8 |
| Open the browser or OS password manager and autofill | both fields fill and submit succeeds | 1.3.5, 3.3.8 |
| Paste a full one-time code from an email | all characters land in one field | 3.3.8 |
| Submit a wrong credential | a text error tied to the field, aria-invalid, focus moved, username retained | 3.3.1 |
| Create a new account and re-open the form | the manager offers new-password, not current-password | 1.3.5 |
// Confirm the autocomplete tokens, and that no paste handler cancels the event.
for (const [sel, token] of [['#pw', 'current-password'], ['#code', 'one-time-code']]) {
const el = document.querySelector(sel);
if (el.autocomplete !== token) {
console.error(`${sel} should autocomplete="${token}", got "${el.autocomplete}"`);
}
const ev = new ClipboardEvent('paste', { bubbles: true, cancelable: true });
el.dispatchEvent(ev);
if (ev.defaultPrevented) console.error(`${sel} blocks paste`);
}Failure modes
- Blocking paste "to stop clipboard attacks". The common
onpaste="return false"removes the mechanism that makes SC 3.3.8 pass. It does not stop clipboard managers from reading the clipboard anyway. - Splitting a code into one box per character. It looks tidy and ships
everywhere. It breaks
autocomplete="one-time-code", blocks paste, and leaves a screen reader user with six separate edit fields that need manual focus moves. autocomplete="off"on a login form. Browsers often ignore it for passwords, so it looks harmless, but clients that do honour it break the password manager — the mechanism SC 3.3.8 depends on.type="number"for a code. It strips a leading zero, exposes spinner buttons, and breaks autofill in some browsers. Usetype="text"withinputmode="numeric".- A CAPTCHA with no alternative. A single visual puzzle with no audio version and no object-recognition fallback is a cognitive test with no mechanism, which fails SC 3.3.8.
- Asking for selected characters of a password ("enter the 3rd, 5th and 9th character"). This is a pure memory test with almost no mechanism; allow the user to paste the whole password instead.
- Overcorrection — disabling the password manager to "prevent credential theft". It makes the flow non-conforming and does not stop credential theft. Prefer passkeys, which are both stronger and free of a cognitive test.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

