accessibility

Audit web accessibility against WCAG 2.1 guidelines with code examples.

Updated Mar 11, 2018

Search Tags:#accessibility #a11y #screen reader #web development #keyboard navigation #WCAG

Ready to run

npx skills add https://github.com/jorgegvalencia/dotfiles --skill accessibility-jorgegvalencia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/jorgegvalencia/dotfiles/tree/main/gemini/skills/accessibility
Command: npx skills add https://github.com/jorgegvalencia/dotfiles --skill accessibility-jorgegvalencia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web content accessible to all users, including those with disabilities, by adhering to WCAG 2.1 guidelines.

Core Features & Use Cases

WCAG Compliance Audits: Provides detailed checks against Perceivable, Operable, Understandable, and Robust (POUR) principles.
Code Examples: Offers practical HTML, CSS, and JavaScript snippets for implementing accessibility best practices.
Use Case: When developing a new website feature, use this Skill to audit its accessibility, ensuring it meets AA compliance standards for keyboard navigation, color contrast, and screen reader support.

Quick Start

Audit the current webpage for accessibility issues based on WCAG 2.1 guidelines.

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?▼

You can audit web accessibility by checking your content against WCAG 2.1 guidelines, evaluating POUR principles and conformance levels to identify areas requiring improvement for AA compliance.

What are the WCAG 2.1 POUR principles for web accessibility?▼

The POUR principles in web accessibility stand for Perceivable, Operable, Understandable, and Robust, providing the foundational framework to ensure web content is usable by everyone.

How do I implement keyboard navigation and screen reader support in web development?▼

You can implement keyboard navigation and screen reader support by applying provided HTML, CSS, and JavaScript code examples that utilize ARIA attributes and ensure operable interfaces for WCAG compliance.

What is the best way to fix color contrast and text alternative issues for accessibility?▼

The best way to fix color contrast and text alternative issues is by applying practical code examples that ensure perceivable content, meeting WCAG 2.1 conformance levels for visual accessibility.

Can I use automated and manual testing checklists to validate a11y compliance?▼

Yes, you can validate a11y compliance using provided testing checklists that guide both automated and manual validation processes to systematically verify keyboard navigation, form labels, and ARIA usage.

Does this accessibility audit work for AA conformance levels in web development?▼

Yes, the accessibility audit checks web features against AA conformance levels, validating keyboard navigation, color contrast, and screen reader support to ensure web content meets WCAG 2.1 standards.