Get the FREE Ultimate OpenClaw Setup Guide →

accessibility

Scanned
npx machina-cli add skill Fujigo-Software/f5-framework-claude/accessibility --openclaw
Files (1)
SKILL.md
4.3 KB

Accessibility Skills

Overview

Web accessibility (a11y) ensures websites are usable by everyone, including people with disabilities. Accessible design benefits all users and is often required by law.

WCAG Principles (POUR)

PrincipleDescriptionExamples
PerceivableInfo must be presentable to usersAlt text, captions, contrast
OperableUI must be operable by everyoneKeyboard access, timing
UnderstandableInfo and UI must be understandableClear labels, error handling
RobustContent must work with assistive techValid HTML, ARIA

WCAG Conformance Levels

LevelDescriptionTarget Audience
AMinimum accessibilityBasic requirements
AARecommended standardMost organizations (legal requirement)
AAAEnhanced accessibilitySpecialized applications

Key Statistics

  • 15% of world population has a disability
  • 1 in 4 adults in the US has a disability
  • 8% of men have color blindness
  • By 2030, 1.4 billion people will be over 60

Categories

Fundamentals

Core accessibility concepts:

  • WCAG Overview - Understanding the guidelines
  • Accessibility Principles - POUR principles in detail
  • Disability Types - Understanding user needs

HTML

Semantic structure:

  • Semantic HTML - Using proper elements
  • Landmarks - Page regions for navigation
  • Headings - Document structure
  • Forms - Accessible form design

ARIA

Accessible Rich Internet Applications:

  • ARIA Basics - When and how to use ARIA
  • ARIA Roles - Element roles
  • ARIA States - Dynamic state attributes
  • Live Regions - Announcing dynamic content

Keyboard

Keyboard accessibility:

  • Keyboard Navigation - Tab order and shortcuts
  • Focus Management - Focus indicators and trapping
  • Skip Links - Bypassing repeated content

Visual

Visual accessibility:

  • Color Contrast - Contrast ratios and tools
  • Text Sizing - Responsive typography
  • Motion Reduction - Respecting user preferences

Media

Multimedia accessibility:

  • Images & Alt Text - Descriptive alternatives
  • Video Captions - Synchronized text
  • Audio Transcripts - Text alternatives

Testing

Accessibility testing:

  • Manual Testing - Keyboard and visual testing
  • Automated Testing - axe, Lighthouse, Pa11y
  • Screen Reader Testing - NVDA, VoiceOver, JAWS

Components

Accessible patterns:

  • Accessible Buttons - Button best practices
  • Accessible Forms - Form patterns
  • Accessible Modals - Dialog accessibility
  • Accessible Tables - Data table patterns

Quick Reference

Minimum Requirements (WCAG 2.1 AA)

RequirementGuidelineCheck
Color contrast (normal text)4.5:1Tools
Color contrast (large text)3:1Tools
Focus visible2.4.7Manual
Keyboard accessible2.1.1Manual
Alt text for images1.1.1Automated
Form labels1.3.1Automated
Error identification3.3.1Manual
Page titled2.4.2Automated

Testing Checklist

- [ ] Can navigate with keyboard only
- [ ] Focus indicator is visible
- [ ] Color contrast meets requirements
- [ ] Images have alt text
- [ ] Forms have labels
- [ ] Headings are hierarchical
- [ ] Links are descriptive
- [ ] Errors are announced
- [ ] Works with screen reader

Legal Requirements

RegionLawStandard
USAADA, Section 508WCAG 2.1 AA
EUEuropean Accessibility ActWCAG 2.1 AA
UKEquality ActWCAG 2.1 AA
CanadaAODAWCAG 2.0 AA

Tools

ToolPurposeType
axe DevToolsBrowser testingExtension
WAVEVisual inspectionExtension
LighthouseAuditBrowser
Pa11yCI integrationCLI
NVDAScreen readerApplication
VoiceOverScreen readermacOS/iOS

Related Skills

Source

git clone https://github.com/Fujigo-Software/f5-framework-claude/blob/main/plugins/f5-core/skills/accessibility/SKILL.mdView on GitHub

Overview

Web accessibility (a11y) ensures websites are usable by everyone, including people with disabilities. Accessible design benefits all users and is often required by law.

How This Skill Works

The skill centers on WCAG principles (POUR) and conformance levels (A, AA, AAA), then maps practical techniques across Fundamentals, HTML, ARIA, Keyboard, Visual, Media, Testing, and Components. It emphasizes semantic HTML, proper ARIA usage, keyboard navigation, focus management, and thorough testing with manual checks and automated tools to verify accessibility.

When to Use It

  • Auditing a new or existing site to meet WCAG 2.1 AA
  • Building forms, navigation, modals, and interactive components to be accessible
  • Ensuring content is operable with keyboard, screen readers, and other assistive tech
  • Regulatory compliance and risk management for accessibility laws and standards
  • Designing and testing media with captions, transcripts, alt text, and accessible controls

Quick Start

  1. Step 1: Audit for POUR alignment and WCAG 2.1 AA basics
  2. Step 2: Implement semantic HTML, landmarks, alt text, labels, and appropriate ARIA
  3. Step 3: Test with keyboard, screen readers (NVDA, VoiceOver, JAWS), and automated tools; fix issues and iterate

Best Practices

  • Start with semantic HTML and landmarks to establish a solid structure
  • Maintain proper color contrast and scalable text for readability
  • Ensure keyboard accessibility with visible focus indicators and logical focus order
  • Provide accurate alt text, clear labels, and use ARIA only when necessary
  • Combine manual testing with automated tools (axe, Lighthouse, Pa11y) and screen reader testing

Example Use Cases

  • Using landmarks and skip links to simplify navigation for assistive tech
  • Providing descriptive alt text for images and captions for video content
  • Accessible forms with labeled controls and clear error messaging
  • Accessible modals with proper focus management and ARIA attributes
  • Live regions and ARIA updates for dynamic content changes

Frequently Asked Questions

Add this skill to your agents

Related Skills

Sponsor this space

Reach thousands of developers