skills.rest
eyadsibai
eyadsibaiCOMMUNITY
Explore all skills by this author →
Website𝕏@eyadsibaiGitHub

Accessibility

Guide web accessibility implementation with WCAG compliance and ARIA usage.

7|1|Updated Jan 14, 2026
Search Tags:#inclusive design#accessibility#a11y#screen reader#keyboard navigation#wcag
One-click install
npx skills add https://github.com/eyadsibai/ltk --skill accessibility-eyadsibai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility
Source: https://github.com/eyadsibai/ltk/tree/main/plugins/ltk-design/skills/accessibility
Command: npx skills add https://github.com/eyadsibai/ltk --skill accessibility-eyadsibai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating digital products that are usable by everyone, regardless of their abilities, by providing guidance on accessibility best practices.

Core Features & Use Cases

  • WCAG Compliance: Offers guidance on meeting Web Content Accessibility Guidelines (WCAG).
  • Accessible Design Principles: Explains core concepts like POUR (Perceivable, Operable, Understandable, Robust).
  • Practical Implementation: Provides code examples for images, forms, links, and ARIA usage.
  • Testing Strategies: Outlines both automated and manual testing methods, including screen reader usage.
  • Use Case: A developer needs to ensure their new web application is usable by individuals with visual impairments. They can consult this Skill for best practices on color contrast, keyboard navigation, and ARIA attributes.

Quick Start

Provide guidance on how to make images accessible according to WCAG guidelines.

Frequently Asked Questions about Accessibility

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

FAQPage Schema
How do I make my website WCAG compliant?▼

WCAG compliance is achieved by following the POUR principles to ensure content is Perceivable, Operable, Understandable, and Robust. This involves implementing proper ARIA attributes, keyboard navigation, and color contrast guidelines for inclusive digital experiences.

What are the POUR principles in web accessibility?▼

POUR principles in web accessibility are Perceivable, Operable, Understandable, and Robust. They form the foundation of inclusive design, ensuring all users can perceive interface elements, navigate effectively, comprehend content, and rely on robust technology compatibility.

How do I add ARIA attributes to web forms for screen reader compatibility?▼

ARIA attributes for screen reader compatibility are added by applying semantic HTML and ARIA roles to form elements. This ensures proper labels, instructions, and error messages are announced, making forms operable and understandable for keyboard navigation users.

What is the best way to test keyboard navigation and accessibility?▼

Testing keyboard navigation and accessibility is best done through a combination of automated tools and manual testing. This includes verifying tab order, focus management, and using a screen reader to validate the inclusive digital experience for visually impaired users.

When do I need to use ARIA roles in inclusive design?▼

ARIA roles in inclusive design are needed when native HTML elements cannot provide the necessary semantic meaning. Use ARIA to enhance screen reader compatibility for dynamic content, custom widgets, and complex navigation patterns where standard HTML falls short.

Related Skills

Explore More Design & Creative Skills→
teknokomoteknokomo
25

accessibility

Audit web content against WCAG 2.2 and generate remediation plans.

Official
Intermediate
MinhDuyDEVMinhDuyDEV

accessibility-audit

Audit web interfaces for WCAG compliance issues and remediation recommendations.

Community
Intermediate
fellipeutakafellipeutaka
6

react-aria

Build accessible React components with hooks managing ARIA attributes and keyboard interactions.

Community
Advanced
warpdotdevwarpdotdev
820

web-accessibility-audit

Audit web pages against WCAG standards using automated tools and manual review.

Official
Intermediate