skills.rest
teknokomo
teknokomoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

accessibility

Audit web content against WCAG 2.2 and generate remediation plans.

25|3|Updated Mar 3, 2025
Search Tags:#accessibility#a11y#wcag#lighthouse#screen-reader#aria
One-click install
npx skills add https://github.com/teknokomo/universo-platformo-react --skill accessibility-teknokomo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/teknokomo/universo-platformo-react/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/teknokomo/universo-platformo-react --skill accessibility-teknokomo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensures digital content is usable by people with disabilities by auditing for accessibility gaps and guiding improvements.

Core Features & Use Cases

  • WCAG 2.2 guidance baked into practical checks and Lighthouse-style audits.
  • Remediation guidance for pages, components, and interactive widgets to improve perceivability, operability, and understandability.
  • Use Case: A development team audits a new web app and produces a prioritized list of fixes for keyboard navigation and screen reader support.

Quick Start

Analyze a target page for accessibility issues and generate an actionable 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 web app for WCAG 2.2 compliance?▼

Audit web accessibility by applying WCAG 2.2 guidelines and Lighthouse-style audits to evaluate digital products against POUR principles, producing actionable remediation plans for HTML, CSS, and ARIA implementations.

What is the best way to fix keyboard navigation and screen reader support?▼

Fix keyboard navigation and screen reader support by auditing interactive widgets and pages, then applying targeted remediation guidance to improve perceivability, operability, and understandability based on WCAG 2.2 standards.

How do I generate an accessibility remediation plan for interactive widgets?▼

Generate an accessibility remediation plan by analyzing target pages and interactive widgets for gaps, evaluating them for POUR principles, and producing a prioritized list of fixes for ARIA implementations and keyboard navigation.

Can I use Lighthouse audits to evaluate web accessibility for people with disabilities?▼

Yes, you can evaluate web accessibility using Lighthouse-style audits combined with WCAG 2.2 guidelines to ensure digital content is usable by people with disabilities, identifying gaps across pages and components.

What do I need to provide to get actionable ARIA and HTML accessibility fixes?▼

You need to provide code patterns and ensure reference materials are available in the references directory to drive actionable fixes in HTML, CSS, and ARIA implementations during the accessibility audit and remediation process.

When should I not rely solely on automated accessibility audits?▼

Automated accessibility audits should be supplemented with manual evaluation when assessing complex interactive widgets, as WCAG 2.2 compliance requires thorough evaluation of POUR principles across real-world content and user interactions.

Related Skills

Explore More Software Engineering Skills→
RB-chrismandichRB-chrismandich
1

a11y-audit

Audit web projects for WCAG 2.2 AA accessibility issues with ARIA and semantic HTML checks.

Community
Advanced
leonardoteodorooleonardoteodoroo

accessibility-compliance

Guides teams to implement WCAG 2.2 compliant accessibility across web interfaces.

Community
Intermediate
inbharataiinbharatai
22

accessibility-checker

Audit digital content for WCAG 2.2 compliance and accessibility issues.

Community
Intermediate
kennyolofsson23-netizenkennyolofsson23-netizen

wcag-accessibility-audit

Audit web interfaces against WCAG 2.1 and 2.2 success criteria.

Community
Advanced