Accessibility

Solidiom is built on the principle that accessible software is not optional. Every primitive, component, and template is designed and tested against WCAG 2.2 Level AA and WAI-ARIA Authoring Practices Guide (APG) patterns.

#Our Commitment

• Every interactive primitive implements the corresponding APG keyboard and ARIA pattern
• Every primitive ships with committed accessibility evidence (evidence.json)
• Every theme preset passes AA contrast minimums in both light and dark modes
• Automated axe-core scans run on every build for all 52 primitives
• Keyboard navigation is documented and tested for every interactive element

#Evidence

Our accessibility evidence is machine-verified and committed to the repository:

#Automated Testing

#Per-Primitive Evidence

Each of the 52 primitives has a committed packages/<name>/docs/accessibility/evidence.json containing:

• axe-core scan results (violations, passes, incomplete)
• Keyboard navigation contract
• ARIA attributes and roles used
• Screen reader behavior expectations

#Screen Reader Testing

#WCAG 2.2 AA Compliance

All primitives and components comply with WCAG 2.2 Level AA. Our full audit is documented at docs/qa/wcag-2.2-aa-audit.md and covers:

• Perceivable — semantic HTML, ARIA roles, 4.5:1+ text contrast, rem typography
• Operable — full keyboard navigation, no traps, visible focus, 24px+ targets
• Understandable — lang attributes, no unexpected changes, labeled inputs
• Robust — valid ARIA, live regions for dynamic content

#APG Pattern Compliance

Interactive primitives implement WAI-ARIA Authoring Practices patterns:

#Reporting Issues

If you encounter an accessibility barrier in Solidiom:

1. Open a GitHub issue with the accessibility label
2. Include the primitive/component affected
3. Describe the barrier and the assistive technology used
4. We prioritize accessibility issues as critical bugs

#Resources

• WCAG 2.2 Quick Reference
• WAI-ARIA Authoring Practices Guide
• Our full WCAG audit