skills.rest
Gabrielloopes33
Gabrielloopes33COMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web accessibility against WCAG 2.1 guidelines for keyboard navigation and screen readers.

Updated Feb 27, 2026
Search Tags:#accessibility#a11y#wcag#lighthouse#screen-reader#keyboard-navigation
One-click install
npx skills add https://github.com/Gabrielloopes33/nexIA --skill accessibility-gabrielloopes33
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Gabrielloopes33/nexIA/tree/main/.copilot/skills/accessibility
Command: npx skills add https://github.com/Gabrielloopes33/nexIA --skill accessibility-gabrielloopes33

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.1 guidelines. This guide helps teams ensure digital content is usable by people with disabilities by applying the POUR principles and recognized testing practices.

Core Features & Use Cases

  • WCAG 2.1 conformance guidance (A/AA/AAA) and practical audit checklists
  • POUR framework (Perceivable, Operable, Understandable, Robust) with actionable examples
  • Real-world use cases for audits of websites and web apps focusing on keyboard navigation, screen reader compatibility, color contrast, and accessible forms.

Quick Start

Audit a website for accessibility issues using WCAG 2.1 guidelines and apply fixes to improve conformance.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a website for WCAG 2.1 conformance and fix accessibility issues?▼

Audit a website for accessibility issues by applying WCAG 2.1 guidelines to check keyboard navigation, screen reader support, color contrast, and semantic structure, then apply fixes to improve conformance levels A, AA, or AAA.

What is the POUR framework and how does it apply to web accessibility testing?▼

The POUR framework defines web accessibility through Perceivable, Operable, Understandable, and Robust principles. Apply it to digital content audits to evaluate keyboard navigation, screen reader compatibility, and semantic structure for WCAG 2.1 conformance.

How do I check if my web application supports screen readers and keyboard navigation?▼

Check screen reader and keyboard navigation support by applying WCAG 2.1 guidelines and ARIA best practices. Use practical audit checklists to verify focus management, semantic HTML structure, and interactive element operability.

Does this accessibility audit approach work for both websites and web apps?▼

Yes, apply WCAG 2.1 conformance checks to both websites and web applications. The audit addresses color contrast, accessible forms, keyboard navigation, and screen reader compatibility across digital content platforms.

What are the limitations of using WCAG 2.1 checklists for accessibility audits?▼

WCAG 2.1 checklists focus on guideline conformance but require manual testing for keyboard navigation and screen reader compatibility. Automated checks cannot fully replace human evaluation of semantic structure and POUR principle adherence.

When do I need to use ARIA best practices during an accessibility audit?▼

Apply ARIA best practices during accessibility audits when evaluating dynamic web content and interactive UI components. Use ARIA roles and properties to ensure screen reader support when semantic HTML alone does not provide sufficient context.

Related Skills

Explore More Software Engineering Skills→
1veso1veso

tweak

Inject a live tweak panel into HTML files and bake adjustments into source CSS.

Community
Intermediate
clawpod-appclawpod-app
46

accessibility-review

Audit designs or pages for WCAG 2.1 AA compliance with remediation guidance.

Community
Intermediate
mauriciodelriomauriciodelrio
3

a11y-rules

Audit React and Next.js components for WCAG 2.2 AA accessibility violations.

Community
Intermediate
thiagoooo34252thiagoooo34252
1

engineer-accessibility

Scan web applications for WCAG 2.2 violations using axe-core.

Community
Advanced