skills.rest
luanrodrigues
luanrodriguesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bee:dev-frontend-accessibility

Validate frontend components against WCAG 2.1 AA with axe-core and keyboard tests.

2|1|Updated Mar 3, 2026
Search Tags:#testing#accessibility#a11y#frontend#compliance#wcag
One-click install
npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-dev-frontend-accessibility
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bee:dev-frontend-accessibility
Source: https://github.com/luanrodrigues/ia-frmwrk/tree/main/dev-team/skills/dev-frontend-accessibility
Command: npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-dev-frontend-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the validation of frontend components against WCAG 2.1 AA accessibility standards, preventing usability issues for users with disabilities.

Core Features & Use Cases

  • Automated Accessibility Scans: Utilizes axe-core to identify WCAG 2.1 AA violations.
  • Keyboard Navigation Testing: Verifies that all interactive elements are navigable via keyboard.
  • Focus Management Validation: Ensures proper focus handling for modals and dialogs.
  • Use Case: After implementing a new modal component, this Skill will automatically scan it for accessibility issues, test keyboard navigation, and confirm focus is correctly managed, ensuring it's usable by everyone.

Quick Start

Use the bee:dev-frontend-accessibility skill to test the accessibility of the new user profile form.

Frequently Asked Questions about bee:dev-frontend-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test frontend components for WCAG 2.1 AA compliance?▼

Test WCAG 2.1 AA compliance by running automated axe-core scans and keyboard navigation tests on your frontend components. This process validates interactive elements and focus management to ensure usability for users with disabilities.

What is automated accessibility testing for keyboard navigation?▼

Automated accessibility testing for keyboard navigation verifies that all interactive elements are fully navigable via keyboard. It checks focus management for modals and dialogs to ensure frontend components meet WCAG 2.1 AA standards.

Does axe-core scanning work with TypeScript implementation files?▼

Yes, axe-core scanning works with TypeScript implementation files. You must provide TypeScript implementation files and adhere to specific testing commands to validate your frontend components against accessibility guidelines.

How do I validate focus management for modals and dialogs?▼

Validate focus management for modals and dialogs by running automated accessibility scans. This verifies that keyboard navigation and focus handling correctly trap and restore focus, ensuring compliance with WCAG 2.1 AA standards.

When do I need to run automated accessibility scans on frontend components?▼

Run automated accessibility scans on frontend components whenever you implement new interactive elements like user profile forms or modals. This ensures ongoing WCAG 2.1 AA compliance and prevents usability issues for users with disabilities.

Related Skills

Explore More Software Engineering Skills→
V4-CompanyV4-Company
2

marsai:dev-frontend-accessibility

Run axe-core accessibility scans on React/TypeScript UI components.

Official
Intermediate
omarrohit20omarrohit20

Axe-core Accessibility

Automate axe-core accessibility scans with Playwright for WCAG 2.1 AA compliance.

Community
Advanced
luanrodriguesluanrodrigues
2

bee:dev-frontend-accessibility-vuejs

Validate Vue.js components for WCAG 2.1 AA compliance with axe-core scans.

Community
Advanced
ariesanhthuariesanhthu

accessibility-expert

Audits WCAG 2.1/2.2 compliance and fixes accessibility violations in web projects.

Community
Advanced