skills.rest
exceptionless
exceptionlessOFFICIAL
Explore all skills by this author →
Website𝕏@ExceptionlessGitHub

accessibility

Enforce WCAG 2.2 AA compliance for frontend components with semantic HTML and ARIA.

2.5k|507|Updated Feb 7, 2014
Search Tags:#inclusive design#accessibility#a11y#web development#frontend#wcag
One-click install
npx skills add https://github.com/exceptionless/Exceptionless --skill accessibility-exceptionless
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/exceptionless/Exceptionless/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/exceptionless/Exceptionless --skill accessibility-exceptionless

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that web interfaces are usable by everyone, regardless of their abilities, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • WCAG 2.2 AA Compliance: Guides development and review for semantic HTML, ARIA patterns, keyboard navigation, and focus management.
  • Inclusive Design: Promotes the use of accessible forms, images, and interactive elements.
  • Use Case: When developing a new modal dialog, use this skill to ensure it's keyboard-operable, properly announced by screen readers, and returns focus to the triggering element upon closing.

Quick Start

Use the accessibility skill to ensure the new user profile form is WCAG 2.2 AA compliant.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I make my frontend components meet WCAG 2.2 AA accessibility standards?▼

To meet WCAG 2.2 AA accessibility standards, frontend components must implement semantic HTML, correct ARIA patterns, keyboard navigation, focus management, and screen reader support for interactive elements.

How do I handle focus management for a modal dialog so it is keyboard operable?▼

For accessible focus management, a modal dialog must be keyboard-operable, properly announced by screen readers, and return focus to the triggering element upon closing.

What is inclusive design in web development and when do I need it?▼

Inclusive design in web development ensures interfaces are usable by everyone regardless of ability. You need it when developing new UI components, fixing bugs, or implementing accessible markup for forms and images.

How do I ensure form accessibility for screen readers using ARIA patterns?▼

Ensuring form accessibility requires applying ARIA patterns and semantic HTML so form inputs are properly announced by screen readers and fully operable via keyboard navigation.

Does keyboard navigation work for interactive elements without semantic HTML?▼

Keyboard navigation for interactive elements relies heavily on semantic HTML. Without proper semantic markup, screen readers and keyboard users cannot effectively access or operate the web interface components.

Related Skills

Explore More Software Engineering Skills→
sigmadigitalzasigmadigitalza
1

frontend-accessibility-review

Audit web frontends for WCAG 2.2 AA conformance with static and live checks.

Official
Advanced
ariesanhthuariesanhthu

accessibility-expert

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

Community
Advanced
theofernandezztheofernandezz

Accessibility (a11y)

Apply WCAG-compatible patterns and ARIA semantics to web interfaces.

Community
Advanced
AGMO-IncAGMO-Inc
4

accessibility

Detect WCAG accessibility issues in React/HTML/CSS via static review.

Official
Intermediate