skills.rest
jschulte
jschulteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Pantheon Accessibility (Iris)

Review frontend code for WCAG 2.1 AA accessibility compliance.

Updated Aug 23, 2026
Search Tags:#code review#accessibility#a11y#frontend#compliance#wcag
One-click install
npx skills add https://github.com/jschulte/pantheon --skill pantheon-accessibility-iris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Pantheon Accessibility (Iris)
Source: https://github.com/jschulte/pantheon/tree/main/src/skills/pantheon-accessibility
Command: npx skills add https://github.com/jschulte/pantheon --skill pantheon-accessibility-iris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the review of frontend code for accessibility compliance, identifying violations of WCAG 2.1 AA standards to ensure your web applications are usable by everyone.

Core Features & Use Cases

  • Automated Accessibility Audits: Scans frontend files (tsx, jsx, css, html) for common accessibility issues.
  • Violation Classification: Categorizes findings into MUST_FIX, SHOULD_FIX, and STYLE for prioritized remediation.
  • Use Case: After a new feature is developed, run this Skill to automatically check for keyboard navigation issues, missing alt text, and insufficient color contrast before deployment.

Quick Start

Use the Pantheon Accessibility (Iris) skill to review the files changed in story 1-3.

Frequently Asked Questions about Pantheon Accessibility (Iris)

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

FAQPage Schema
How do I check my frontend code for WCAG 2.1 AA accessibility compliance?▼

To check WCAG 2.1 AA accessibility compliance, scan your modified tsx, jsx, css, or html files for semantic HTML, keyboard accessibility, screen reader compatibility, and visual design issues. Violations are categorized into MUST_FIX, SHOULD_FIX, and STYLE for prioritized remediation.

What is WCAG 2.1 AA compliance and how does automated code review handle it?▼

WCAG 2.1 AA compliance ensures web applications are usable by everyone by meeting specific accessibility standards. Automated code review handles this by scanning frontend files to identify missing alt text, keyboard navigation issues, and insufficient color contrast before deployment.

Can I use an automated accessibility audit on tsx and jsx files?▼

Yes, you can use an automated accessibility audit on tsx and jsx files. The review process applies to stories involving tsx, jsx, css, or html file modifications and utilizes file analysis tools to perform compliance checking.

How do I prioritize fixing screen reader compatibility and keyboard navigation issues?▼

To prioritize fixing screen reader compatibility and keyboard navigation issues, review the violation classifications provided by the accessibility audit. Findings are sorted into MUST_FIX, SHOULD_FIX, and STYLE categories to guide your remediation sequence.

What file types are supported for automated accessibility audits?▼

Supported file types for automated accessibility audits include tsx, jsx, css, and html. The review process specifically targets these frontend file modifications to identify violations of WCAG 2.1 AA standards.

Related Skills

Explore More Software Engineering Skills→
softsparksoftspark
161

a11y-validate

Detect accessibility violations in web and mobile project files.

Community
Advanced
PP-NamiasPP-Namias
2

accessibility-audit

Validate web accessibility compliance with WCAG 2.1 AA standards.

Community
Intermediate
eugenereugener
3

refactoring-ui

Audit frontend UI code against Refactoring UI design principles.

Community
Advanced
PrasadTelasulaPrasadTelasula

accessibility-compliance

Implement WCAG 2.1 AA accessibility across QA Team Portal interfaces with ARIA roles, keyboard navigation, and color contrast fixes.

Community
Advanced