skills.rest
Arnutt-N
Arnutt-NCOMMUNITY
Explore all skills by this author →
GitHub

Accessibility Guidelines

Audit UI accessibility using WCAG 2.1 POUR principles and semantic HTML.

Updated Jan 8, 2026
Search Tags:#accessibility#a11y#wcag#semantic-html#aria#keyboard-navigation
One-click install
npx skills add https://github.com/Arnutt-N/hr-ims --skill accessibility-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility Guidelines
Source: https://github.com/Arnutt-N/hr-ims/tree/main/.agents/skills/accessibility-guidelines
Command: npx skills add https://github.com/Arnutt-N/hr-ims --skill accessibility-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI designed without accessibility guidelines leads to exclusion of users with disabilities, missing WCAG compliance, and reduced usability across assistive technologies.

Core Features & Use Cases

  • Guidance on semantic HTML usage for common elements (button, nav, main, article, aside)
  • ARIA labeling strategies and keyboard navigation patterns to ensure focus visibility and skip navigation
  • Practical accessibility testing and auditing notes with recommended tools (Lighthouse, aXe)

Quick Start

Audit your UI for accessibility by applying WCAG 2.1 POUR principles and implementing semantic HTML, ARIA attributes, and keyboard-friendly interactions.

Frequently Asked Questions about Accessibility Guidelines

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

FAQPage Schema
How do I audit my web UI for WCAG 2.1 accessibility compliance?▼

Implement accessible web forms by applying semantic HTML elements, adding appropriate ARIA labeling, and ensuring keyboard-friendly interactions with visible focus management for assistive technologies.

When do I need ARIA attributes instead of semantic HTML for accessibility?▼

You need ARIA attributes instead of semantic HTML when standard elements cannot convey dynamic UI changes, requiring ARIA labeling strategies to ensure focus visibility and proper screen reader announcements.

How does keyboard navigation and focus management work for accessible interfaces?▼

Keyboard navigation and focus management work by implementing skip links, ensuring visible focus states, and using semantic elements to allow users to navigate web applications without a mouse.

What are the best tools for testing semantic HTML and color contrast in web applications?▼

Yes, you can apply these accessibility guidelines to any web application by implementing semantic element usage, ARIA attributes, skip links, and focus management to meet WCAG 2.1 POUR compliance.

Related Skills

Explore More Design & Creative Skills→
HaslienHaslien

typography

Define scalable UI type systems with CSS variables and mathematical ratios.

Community
Advanced
Khrees2412Khrees2412

accessibility

Audit web content against WCAG 2.1 and Lighthouse accessibility guidelines.

Community
Advanced
ksciuskscius
2

web-accessibility

Enforce WCAG 2.1 AA accessibility requirements for web UI components.

Community
Intermediate
musher-devmusher-dev

auditing-accessibility-compliance

Audit developer documentation websites for WCAG 2.1 AA accessibility compliance.

Official
Advanced