accessibility-testing SKILL.md skillA
accessibility-testing from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/accessibility-testing@git:20260529.7c05904Pins git:20260529.7c05904 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/accessibility-testing/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260529.7c05904, committed May 29, 2026
- Size
- 1,736 bytes
- Repository stars
- 74,516
- License
- MIT
Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Include accessibility testing Automated accessibility testing catches 30-50% of WCAG violations before code reaches users—reducing legal risk and improving usability for everyone. ## Quick Reference - Use jest-axe for component-level accessibility testing - Integrate @axe-core/playwright or cypress-axe for E2E a11y tests - Run accessibility tests in CI/CD to catch regressions early - Test specific WCAG rules like color-contrast individually ## Check Review this test suite for accessibility testing coverage using axe-core, jest-axe, or similar tools. ## Fix Add automated accessibility testing to detect WCAG violations in components and pages. ## Explain Explain how to implement automated accessibility testing and what issues it can detect. ## Code Review Inspect component tests, E2E suites, and CI workflows for automated accessibility coverage. Flag critical pages or shared components that ship without axe-based checks, and note issues that still require manual keyboard or screen reader validation. --- For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`. …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/accessibility-testing@sha256:3942f26524ef4d9eThe line at the top of this page pins the label git:20260529.7c05904, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mohhy432ews6mths)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1736 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mohhy432ews6mths GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/accessibility-testing GET https://markdownregistry.com/api/v1/blob/3942f26524ef4d9ead70efdd7c78b51813ed1c796baf341f0ad399a4328f8d14
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from thedaviddias/front-end-checklist
Every file in thedaviddias/front-end-checklist