skills.rest
loveconnor
loveconnorCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Verify digital interfaces against WCAG 2.2 AA standards with manual and automated protocols.

Updated Jul 20, 2026
Search Tags:#accessibility#audit#compliance#wcag#screen-reader#keyboard-navigation
One-click install
npx skills add https://github.com/loveconnor/clove-skills --skill accessibility-loveconnor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/loveconnor/clove-skills/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/loveconnor/clove-skills --skill accessibility-loveconnor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of building digital interfaces that are truly usable by people with disabilities, moving beyond simple automated checks to ensure functional, real-world accessibility.

Core Features & Use Cases

  • Accessibility Contract Definition: Establish clear requirements for semantics, keyboard behavior, and assistive technology support before writing code.
  • Layered Verification: Combine automated structural checks with manual protocols for keyboard navigation, screen-reader compatibility, and responsive adaptation.
  • Use Case: When building a complex custom component like a date picker, use this Skill to define the focus management, ARIA roles, and keyboard shortcuts required to ensure it is fully operable by screen-reader and keyboard-only users.

Quick Start

Use the accessibility skill to audit the current interface against WCAG 2.2 AA standards and generate a list of required manual verification steps.

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.2 AA compliance?▼

Auditing for WCAG 2.2 AA compliance involves running automated structural checks and manual protocols for keyboard navigation, screen-reader compatibility, and responsive adaptation to verify perceivable, operable, understandable, and robust content.

How do I make custom components like a date picker operable for screen-reader users?▼

Making custom components operable for screen-reader users requires defining accessibility contracts for focus management, ARIA roles, and keyboard shortcuts to ensure functional, real-world usability before and after writing code.

Does automated testing alone ensure accessible digital interfaces?▼

Automated testing alone does not ensure accessible digital interfaces; true accessibility requires layered verification combining automated structural checks with manual protocols for keyboard navigation and assistive technology support.

What's the best way to verify keyboard navigation and semantic HTML support?▼

The best way to verify keyboard navigation and semantic HTML support is applying structured manual and automated testing protocols that validate focus management and assistive-use conditions against WCAG 2.2 AA standards.

When do I need to establish an accessibility contract for web development?▼

You need to establish an accessibility contract for web development before writing code to define clear requirements for semantics, keyboard behavior, and assistive technology support for complex custom components.

Why does my responsive design fail screen-reader compatibility checks?▼

Responsive design fails screen-reader compatibility checks when structured manual verification protocols are skipped; ensuring robust content requires validating responsive adaptation alongside keyboard navigation and ARIA implementations.

Related Skills

Explore More Software Engineering Skills→
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced
SensLiaoSensLiao

qa-a11y-compliance

Scan web applications for WCAG 2.2 AA accessibility compliance.

Community
Advanced
MonumentalSystemsMonumentalSystems
17

accessibility

Implement WCAG 2.1 accessibility guidance for web and UI content.

Official
Basic
thiagoooo34252thiagoooo34252
1

engineer-accessibility

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

Community
Advanced