Fec accessibility check

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

frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.

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

19 stars19 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.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.9 KB, 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

Check the semantic structure: landmark, title level, form label, button/link accessible name, table semantics and image alt.
Check the keyboard path: Tab order, Enter/Space/Esc behavior, focus visible, focus restored after closing.
Check the ARIA status of complex components: dialog boxes, menus, tabs, trees, drawers, tables, and custom controls.
Check dynamic status: loading, empty, error, toast and asynchronous updates need to be perceived by screen readers.
Check visual and touch readability: text/background contrast, focus ring, zoom to 200%, reduced animation preference, touch target size, and mobile virtual keyboard behavior.
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.
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.
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.