accessibility

Audits webpages for WCAG 2.1 and Lighthouse accessibility standards.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/terna-cc/support-sdk --skill accessibility-terna-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/terna-cc/support-sdk/tree/main/.claude/skills/accessibility
Command: npx skills add https://github.com/terna-cc/support-sdk --skill accessibility-terna-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web content usable by everyone, including individuals with disabilities, by auditing and improving adherence to accessibility standards.

Core Features & Use Cases

  • WCAG 2.1 Compliance: Provides guidelines and checks based on the Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Automated & Manual Testing: Offers guidance on using tools like Lighthouse and axe-core, alongside a manual testing checklist.
  • Use Case: When developing a new feature, use this Skill to ensure it meets WCAG AA standards, making it accessible to users with visual, auditory, motor, or cognitive impairments.

Quick Start

Use the accessibility skill to audit the provided webpage for WCAG 2.1 compliance.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I check my web content for WCAG 2.1 compliance?

Check WCAG 2.1 compliance by auditing your web content against the Perceivable, Operable, Understandable, and Robust principles. This process evaluates text alternatives, color contrast, keyboard navigation, ARIA usage, and form accessibility to meet Lighthouse standards.

What is the best way to test keyboard navigation for screen reader compatibility?

The best way to test keyboard navigation is combining automated tools like axe-core with a manual testing checklist. This ensures your web content is operable for screen reader users and identifies focus order or ARIA usage issues that automated checks might miss.

Does Lighthouse accessibility auditing cover all WCAG AA standards?

Lighthouse accessibility auditing does not cover all WCAG AA standards automatically. It provides a baseline check for common issues like color contrast and ARIA usage, but you must also perform manual testing to fully verify content is perceivable and understandable for users with disabilities.

How do I improve color contrast and ARIA usage for web accessibility?

Improve color contrast and ARIA usage by evaluating your web elements against WCAG 2.1 guidelines. Ensure text meets minimum contrast ratios and use ARIA roles correctly to make dynamic content robust and perceivable for screen readers.

When do I need to perform a manual web accessibility audit?

You need a manual web accessibility audit when automated tools like Lighthouse cannot fully verify WCAG compliance. Manual testing is essential to confirm keyboard navigation flows, screen reader behavior, and that content is genuinely understandable for users with cognitive or motor impairments.