skills.rest
RodrigoTomeES
RodrigoTomeESCOMMUNITY
Explore all skills by this author →
Website𝕏@RodrigoTomeESGitHub

accessibility

Audit web interfaces for WCAG 2.1 compliance and accessibility issues.

12|3|Updated Feb 17, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#wcag#contrast#aria
One-click install
npx skills add https://github.com/RodrigoTomeES/getmcp --skill accessibility-rodrigotomees
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/RodrigoTomeES/getmcp/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/RodrigoTomeES/getmcp --skill accessibility-rodrigotomees

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you find and fix accessibility barriers that make websites and interfaces hard to use for people relying on keyboards, screen readers, zoom, high contrast, or reduced motion.

Core Features & Use Cases

  • WCAG-Oriented Audits: Check common accessibility failures such as missing alt text, poor contrast, missing labels, invalid structure, and weak focus states.
  • Interaction Accessibility: Improve keyboard navigation, modal behavior, skip links, live regions, and other operability patterns for real user workflows.
  • Practical Remediation Guidance: Apply concrete fixes for forms, media, navigation, and dynamic UI so products work more reliably across assistive technologies.
  • Use Case: A product team can use this Skill to review a new checkout flow, identify accessibility issues before launch, and produce actionable fixes for developers.

Quick Start

Use the accessibility skill to audit this interface for WCAG 2.1 issues and give me clear, prioritized fixes for keyboard use, screen reader support, contrast, and form labeling.

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 interface for WCAG 2.1 compliance issues?▼

WCAG 2.1 audits validate semantic HTML structure, check color contrast ratios, verify keyboard navigation, and ensure screen reader support through proper ARIA implementation and accessible names to identify and fix accessibility barriers.

What's the best way to fix keyboard navigation and focus management in dynamic UIs?▼

Fix keyboard navigation by implementing robust focus management, skip links, and correct modal behavior. Ensure operability patterns work reliably across assistive technologies by using semantic HTML before applying ARIA.

When do I need to use ARIA attributes for screen reader support?▼

Use ARIA attributes for screen reader support only when semantic HTML is insufficient to convey meaning. Apply ARIA to provide accessible names, manage live regions, and handle dynamic interaction patterns that native HTML cannot cover.

How do I check color contrast and form labeling for accessibility barriers?▼

Check color contrast by validating ratios against WCAG success criteria, and verify form labeling by ensuring all inputs have programmatically associated labels and accessible names to prevent screen reader failures.

Can I use this approach to review a checkout flow for assistive technology compatibility?▼

Yes, you can review checkout flows and dynamic interactions for assistive technology compatibility by validating operability patterns, media alternatives, and form accessibility against WCAG success criteria to produce prioritized developer fixes.

Why does my screen reader skip dynamic content updates on the page?▼

Screen readers skip dynamic content updates when live regions are missing or incorrectly configured. Fix this by applying appropriate ARIA live region roles to announce dynamic interaction pattern changes to assistive technologies.

Related Skills

Explore More Software Engineering Skills→
dragoscirjandragoscirjan

lang-html

Enforce semantic HTML, WCAG 2.1 AA accessibility, and keyboard navigability.

Community
Basic
ricablericable

accessibility

Audit and remediate web interfaces for WCAG 2.1 accessibility barriers.

Community
Intermediate
bipinksbipinks
3

accessibility-patterns

Apply WCAG 2.1 AA/AAA patterns to improve UI accessibility.

Community
Advanced
mikecubedmikecubed

a11y-check

Detect accessibility issues in TSX/JSX code and provide remediation guidance.

Community
Advanced