skills.rest
mathemagie
mathemagieCOMMUNITY
Explore all skills by this author →
Website𝕏@mathemagieGitHub

accessibility

Audit web accessibility against WCAG 2.1 standards and generate remediation plans.

1|Updated Dec 18, 2015
Search Tags:#accessibility#a11y#wcag#screen-reader#aria#keyboard-navigation
One-click install
npx skills add https://github.com/mathemagie/mathemagie.github.io --skill accessibility-mathemagie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/mathemagie/mathemagie.github.io/tree/main/bidouille/3615_terre/.agents/skills/accessibility
Command: npx skills add https://github.com/mathemagie/mathemagie.github.io --skill accessibility-mathemagie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web projects often fail accessibility checks, creating barriers for users with disabilities and risking non-compliance. This Skill provides guidance and actionable steps to audit and improve accessibility across content and UI.

Core Features & Use Cases

  • A11y auditing: Identify WCAG 2.1 failures for perceivable, operable, understandable, and robust content.
  • Remediation guidance: Suggest concrete fixes (alt text, keyboard navigation, aria labeling, focus management).
  • Use Case: When launching a new website or updating an app, run a guided accessibility review to produce an improvement plan and proof-of-compliance checks.

Quick Start

Run an accessibility audit on the target page and generate a prioritized remediation plan.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my website for WCAG 2.1 compliance?▼

To audit for WCAG 2.1 compliance, evaluate perceivable, operable, understandable, and robust content against success criteria. This identifies failures in color contrast, keyboard navigation, and semantic markup, producing a prioritized remediation plan.

What is the best way to fix keyboard navigation and ARIA labeling issues?▼

Fix keyboard navigation and ARIA labeling issues by applying concrete remediation steps like adding alt text, managing focus, and ensuring proper semantic markup. This aligns UI components with screen reader support requirements.

How do I test color contrast for web accessibility using Lighthouse or axe?▼

Test color contrast for web accessibility by running guided audits with testing tools like Lighthouse and axe. These tools evaluate pages and components against WCAG 2.1 POUR principles to identify contrast failures.

When do I need to run a web accessibility review on my app?▼

Run a web accessibility review when launching a new website or updating an app. This generates an improvement plan and performs proof-of-compliance checks across affected pages and UI components.

Does this accessibility audit cover screen reader support and semantic markup?▼

Yes, the accessibility audit covers screen reader support and semantic markup. It evaluates web apps requiring ARIA labeling, keyboard navigation, and proper HTML structure to ensure content meets WCAG 2.1 robust criteria.

Related Skills

Explore More Software Engineering Skills→
ryan-nguyen-01ryan-nguyen-01
4

skill-ui-accessibility

Analyze web UI structure, semantics, and ARIA usage for accessibility gaps.

Community
Advanced
EIS-ITSEIS-ITS

Frontend Accessibility

Identify and fix accessibility issues in frontend interfaces using semantic HTML, ARIA, and keyboard navigation.

Official
Intermediate
as4584as4584
2

wcag-audit-patterns

Audit web applications for WCAG 2.2 compliance and provide remediation patterns.

Community
Advanced
esneiderbravoesneiderbravo
1

accessibility-standards

Audit UI accessibility for WCAG 2.2 AA compliance with automated and manual checks.

Community
Intermediate