Skip to content
UXClaim
Accessibility

Taiwan Accessibility Audit

Automated WCAG 2.2 AA + Taiwan standard accessibility audits with static analysis and browser-based verification

View source More in Accessibility

What it does

Taiwan Accessibility Audit is a Claude Code skill that automatically scans websites against 60 accessibility criteria: 55 from WCAG 2.2 AA and 5 from Taiwan’s digital development standards. It combines static analysis with Playwright runtime verification to catch issues automated tools can detect.

How it works

The skill follows a 6-step audit process:

  1. Scope confirmation — Define which pages/components to audit
  2. Resource loading — Fetch HTML, CSS, and component code
  3. Static analysis — Parse ARIA attributes, contrast ratios (including CSS variables and oklch color spaces), and semantic structure
  4. Runtime verification — Use Playwright to test focus visibility, tab order, reflow at 320px, and dynamic state changes
  5. Structured reporting — Generate statistics with failures, warnings, and passes broken down by criterion
  6. Guided remediation — Classify fixes as auto-fixable (🔧), confirmation-needed (🎨), or manual (📝) with Taiwan-specific guidance

Use cases

  • Pre-development accessibility screening before professional audits
  • CI/CD integration for regression prevention
  • Component library compliance validation
  • Preparation for Taiwan’s Freego official certification tool

Important limitations

Automated tools cover ~30% of WCAG criteria. This skill cannot replace screen reader testing (NVDA, VoiceOver), real user testing, or professional audits. Passing automated checks does not guarantee accessibility compliance.

Who benefits

Product designers and developers building for Taiwan audiences who need systematic accessibility validation without manual testing overhead.

Frequently asked questions

How do I install the Taiwan Accessibility Audit skill?
Copy the `a11y-tw/` directory to `.claude/skills/` in your project. Requires Claude Code (Pro/Max/Team/Enterprise) and Node.js 18+. Then invoke with `/a11y-tw` in Claude Code.
What's the difference between static and runtime checks?
Static analysis examines HTML, ARIA attributes, and CSS without executing code—catching missing alt text or poor contrast. Runtime verification uses Playwright to interact with the page, testing focus order, reflow behavior, and dynamic state changes that only appear during user interaction.
Does passing this audit mean my site is accessible?
No. This tool detects ~30% of WCAG issues. You still need screen reader testing (NVDA/VoiceOver), user testing with disabled people, and ideally professional audits. Use it as a pre-screening tool before Freego certification.
What accessibility standards does it check?
55 criteria from WCAG 2.2 AA level and 5 Taiwan-specific standards (CNS 5521-1) for a total of 60 checks. Taiwan-specific items include Access Keys, landmark definitions, and skip links.
Can it fix accessibility issues automatically?
Partially. Issues are classified as: 🔧 auto-fixable (missing alt text), 🎨 confirmation-needed (color changes), 📝 manual (ARIA logic). The skill provides repair code and re-validates after fixes to prevent regressions.
How do I run audits on specific pages or criteria?
Use commands like `/a11y-tw check all pages`, `/a11y-tw src/components/Modal.tsx`, or `/a11y-tw --criteria 1.4.3,2.4.7` to target specific WCAG criteria by their identifiers.
What's the relationship between this skill and Freego?
Freego is Taiwan's official certification tool (Windows-only). This skill runs earlier in development as a pre-screening tool to catch issues before submitting to Freego, reducing certification friction.
Does it work with React and Next.js components?
Yes. The skill includes 17 accessibility patterns for React/Next.js components (Modal, Tab, Accordion, Form) and guidance for SSR/CSR scenarios. It can audit component source code and rendered output.

Glossary

WCAG 2.2 AA
Web Content Accessibility Guidelines level AA—the international standard for web accessibility covering perceivability, operability, understandability, and robustness. Taiwan adopts this standard as the baseline requirement.
Automated coverage
The percentage of accessibility issues that can be detected without human judgment. Tools typically cover ~30% (color contrast, missing alt text); 70% requires screen reader testing, keyboard navigation, or user testing.
Runtime verification
Testing web pages as they execute in a browser (using Playwright) rather than analyzing static code. Reveals dynamic state changes, focus behavior, and reflow issues that static analysis alone cannot detect.
Remediation classification
Organizing accessibility fixes into three categories: auto-fixable (tool can repair safely), confirmation-needed (requires designer approval for visual changes), and manual (requires developer judgment or ARIA expertise).

More in Accessibility

All →
Accessibility

A&T Claude Skills

Reusable Claude Code skills for accessibility audits, WCAG compliance checking, and web development workflows

automateandtweak
Accessibility

a11y-skills

Claude Skills for accessibility auditing, code review, and WCAG 2.2 compliance across web, mobile, and documents.

joedevon
Accessibility

Prism Inspector

Complete UX/UI design critique and WCAG 2.2 AA accessibility audit in one tool. Review screenshots, Figma URLs, live sites, or HTML files.