agentsclimarketplace
Sign in

Fec accessibility check

Skill bovinphang/frontend-craft/skills/fec-accessibility-check

Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include accessibility, accessibility, a11y, WCAG, screen reader.From its SKILL.md

Install
npx -y skills add bovinphang/frontend-craft --skill fec-accessibility-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, 521 tokens by cl100k_base, as published. Nobody here has run it

Accessibility Implementation Specification (WCAG 2.2 AA)

Purpose

Ensure the front-end UI is accessible to users with disabilities, meets the core requirements of WCAG 2.2 AA, and is stable for keyboard, screen reader, touch, and zoom users.

Procedure

  1. Check the semantic structure: landmark, title level, form label, button/link accessible name, table semantics and image alt.
  2. Check the keyboard path: Tab order, Enter/Space/Esc behavior, focus visible, focus restored after closing.
  3. Check the ARIA status of complex components: dialog boxes, menus, tabs, trees, drawers, tables, and custom controls.
  4. Check dynamic status: loading, empty, error, toast and asynchronous updates need to be perceived by screen readers.
  5. Check visual and touch readability: text/background contrast, focus ring, zoom to 200%, reduced animation preference, touch target size, and mobile virtual keyboard behavior.
  6. Use the real keyboard path to review the key process, and if necessary, add a screen reader or browser accessibility tree observation; see references/screen-reader-testing.md for the screen reader process.
  7. Review the new high-frequency risks in WCAG 2.2: the visible focus is not blocked, the drag operation has alternative paths, the target size is too small, and the help entrance and authentication process do not rely on memory burden.
  8. Output the classification report; see references/report-template.md for the report format.

Detailed reference

When writing an accessibility review report, load references/report-template.md. Load references/screen-reader-testing.md when you need to verify screen reader announcements, focus pronunciations, and dynamic areas.

Constraints

  • Prefer semantic HTML over ARIA.
  • role should not override native semantics.
  • Interactive elements must be keyboard accessible.
  • Form errors must be associated with fields.
  • Color contrast risks need to be pointed out for specific text/background combinations.
  • Don't use ARIA to make up for problems that can be solved with native HTML.
  • Do not treat automatic browser accessibility trees as final; critical paths need to be verified with the keyboard and at least one assistive technology or equivalent check.

Expected Output

Interactive elements are keyboard accessible, semantics and ARIA are used correctly, and focus management is stable; accessibility check reports are saved as reports/accessibility-review-YYYY-MM-DD-HHmmss.md.

What ships with it: 2 files

2.3 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most quality gates skills give in 521 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Verify semantic structure and landmark usage
  • Test keyboard tab order and focus management
  • Validate ARIA status for complex components
  • Check dynamic status updates for screen readers
  • Verify visual contrast and touch target sizes
  • Review WCAG 2.2 high-frequency risks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.