skills.rest
open-gsd
open-gsdOFFICIAL
Explore all skills by this author →
Website𝕏@opengsdGitHub

accessibility

Audit web content for WCAG 2.1 compliance and generate remediation steps.

1.0k|92|Updated May 22, 2026
Search Tags:#accessibility#a11y#wcag#lighthouse#aria#keyboard-access
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill accessibility-open-gsd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/open-gsd/gsd-pi/tree/main/src/resources/skills/accessibility
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill accessibility-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility barriers prevent a significant portion of users from effectively interacting with web content. This skill provides guidelines and checks based on WCAG 2.1 to identify and address those barriers.

Core Features & Use Cases

  • WCAG 2.1 and Lighthouse-based audits to evaluate conformance and surface actionable recommendations.
  • Semantics and ARIA guidance to improve screen reader compatibility, keyboard navigation, and accessible naming.
  • Practical remediation examples for images, contrast, forms, focus management, and skip navigation, applicable to websites and web apps.

Quick Start

Audit a webpage for WCAG 2.1 compliance and generate actionable accessibility improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a webpage for WCAG 2.1 compliance?▼

To audit a webpage for WCAG 2.1 compliance, you validate semantic HTML, ARIA usage, and keyboard focus management, using Lighthouse automated checks to generate actionable remediation steps for images, forms, and navigation.

How do I fix keyboard navigation and focus management issues?▼

Fix keyboard navigation and focus management issues by validating semantic HTML structures, correcting ARIA usage, and applying practical remediation examples for keyboard interaction and skip navigation across web components.

What is the best way to improve screen reader compatibility using ARIA?▼

Improving screen reader compatibility involves applying ARIA guidance to correct accessible naming and semantic structures, ensuring web content meets WCAG 2.1 guidelines and interacts properly with assistive technologies.

Can I use Lighthouse automated checks to evaluate web accessibility on web applications?▼

Yes, you can use Lighthouse automated checks to evaluate web accessibility on web applications and components across devices, generating actionable recommendations to meet WCAG 2.1 conformance.

Does this accessibility audit cover color contrast and form remediation?▼

Yes, the accessibility audit covers color contrast and form remediation, providing practical examples to address barriers for images, forms, and navigation to ensure effective interaction with web content.

When do I need to validate semantic HTML for web accessibility?▼

You need to validate semantic HTML for web accessibility when identifying barriers preventing users from interacting with web content, ensuring proper screen reader compatibility and keyboard access across devices.

Related Skills

Explore More Design & Creative Skills→
dvegaa20dvegaa20

accessibility

Audit web pages for WCAG 2.2 accessibility issues and provide prioritized remediation guidance.

Community
Intermediate
rampstackcorampstackco
523

accessibility-audit

Identify WCAG 2.1 AA conformance issues and generate remediation plans.

Official
Advanced
MinhAnh-CorpMinhAnh-Corp

accessibility-compliance

Implement WCAG 2.2 compliant interfaces and ARIA patterns for UI components.

Official
Intermediate
basmawebinfo-hubbasmawebinfo-hub

Accessibility Auditor

Audit digital interfaces for WCAG 2.2 compliance and accessibility barriers.

Community
Advanced