How do I install the Accessible Authentication skill?

Run npx skillmds@latest add thedaviddias/accessible-authentication in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Accessible Authentication safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Accessible Authentication?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Accessible Authentication free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Accessible Authentication?

thedaviddias (@thedaviddias) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Accessible Authentication by thedaviddias

Name: Accessible Authentication
Author: thedaviddias

Accessible Authentication

Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.

thedaviddias e13169b 2 files · 6.4 KB Updated Sep 17, 2026

File contents

Provide accessible authentication methods

Authentication often becomes the first hard blocker for users with cognitive, motor, low-vision, or speech-input needs. If sign-in, MFA, or recovery relies on memorization or transcription with no assisted path, the user may be locked out before they can access the product at all.

Quick Reference

Do not block paste or password managers in login and recovery flows
Prefer passkeys, magic links, device approval, or password-manager-friendly flows
Support OTP autofill and paste with appropriate semantics such as autocomplete="one-time-code"
Avoid CAPTCHA or secondary checks that require memorizing or transcribing information without an alternative

Check

Review login, MFA, password reset, and account recovery for accessible authentication problems. Flag blocked paste, password-manager hostility, manual transcription requirements, inaccessible OTP handling, and CAPTCHA or knowledge checks without a compliant alternative.

Fix

Add password-manager-friendly fields, support paste and OTP autofill, and provide at least one authentication path that does not depend on a cognitive function test.

Explain

Explain WCAG Accessible Authentication, why memorization and transcription are barriers, and how passkeys, password managers, OTP autofill, and device approval improve both accessibility and security.

Code Review

Review authentication pages, MFA steps, recovery flows, and security controls related to Provide accessible authentication methods. Flag exact steps that require memorization, transcription, blocked assistive tooling, or inaccessible fallback paths.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/accessibility/accessible-authentication

---name: accessible-authenticationdescription: Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.---# Provide accessible authentication methodsAuthentication often becomes the first hard blocker for users with cognitive, motor, low-vision, or speech-input needs. If sign-in, MFA, or recovery relies on memorization or transcription with no assisted path, the user may be locked out before they can access the product at all.## Quick Reference- Do not block paste or password managers in login and recovery flows- Prefer passkeys, magic links, device approval, or password-manager-friendly flows- Support OTP autofill and paste with appropriate semantics such as `autocomplete="one-time-code"`- Avoid CAPTCHA or secondary checks that require memorizing or transcribing information without an alternative## CheckReview login, MFA, password reset, and account recovery for accessible authentication problems. Flag blocked paste, password-manager hostility, manual transcription requirements, inaccessible OTP handling, and CAPTCHA or knowledge checks without a compliant alternative.## FixAdd password-manager-friendly fields, support paste and OTP autofill, and provide at least one authentication path that does not depend on a cognitive function test.## ExplainExplain WCAG Accessible Authentication, why memorization and transcription are barriers, and how passkeys, password managers, OTP autofill, and device approval improve both accessibility and security.## Code ReviewReview authentication pages, MFA steps, recovery flows, and security controls related to Provide accessible authentication methods. Flag exact steps that require memorization, transcription, blocked assistive tooling, or inaccessible fallback paths.---For full implementation details, code examples, and framework-specific guidance,see `references/rule.md`.Rule page: https://frontendchecklist.io/en/rules/accessibility/accessible-authentication

Frequently asked questions