fec-accessibility-checkUse 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 re
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-accessibility-checkGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/bovinphang/frontend-craftAudited Jun 4, 2026 · audit v1.0
Generated Oct 6, 2026
A frontend team is about to ship a major design system release with new modal, dropdown, and tab components. They run this skill to check semantic structure, keyboard paths, ARIA states, and WCAG 2.2 AA risks before merging. The generated report helps prioritize fixes and prevents regressions across product teams.
A government agency requires WCAG 2.2 AA conformance for a citizen-facing benefits portal. An external agency uses this skill to document keyboard support, screen reader behavior, and focus management. The output report is used as evidence for procurement and remediation planning.
An online retailer discovers that users with screen readers abandon checkout due to unlabeled form fields and missing error associations. The accessibility check assesses the full checkout flow, including dynamic loading states and touch target sizes. The findings lead to fixes that reduce cart abandonment for assistive technology users.
A mobile-first banking app wants to ensure its complex forms and gestures work for users with motor impairments. The skill checks touch target sizes, focus visibility, zoom to 200%, and keyboard behavior on mobile. It also verifies that drag interactions have alternative paths, aligning with WCAG 2.2 requirements.
A B2B analytics product includes interactive tables, charts, and filter panels that are difficult for screen reader users. The team uses this skill to inspect ARIA roles, live region announcements, and table semantics. The resulting report guides development of accessible alternatives and improves non-visual data access.
Agencies and independent consultants offer paid accessibility audits using this skill as a standardized checklist. They deliver detailed reports with severity levels and remediation recommendations, often as part of a broader compliance engagement.
A software company builds a platform that integrates this skill's checks into CI/CD pipelines, scanning deployed pages and generating reports automatically. Customers subscribe for continuous monitoring, historical trends, and team collaboration features.
An education provider uses this skill as the foundation for workshops and certification courses that teach frontend teams how to perform WCAG 2.2 AA checks. Participants learn to identify issues and write remediation plans through hands-on exercises.
💬 Integration Tip
Integrate this skill into your pull request workflow or design review checklist to catch accessibility issues early. Pair it with automated tools like axe-core for broad coverage, but always perform manual keyboard and screen reader testing on critical paths.
Scored Oct 21, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.