Skip to content

$ man accessibility — Legal · Accessibility

accessibility.md
readonly

Accessibility Statement

Last updated: May 1, 2026

ClaudeSkill is committed to making the Service usable for as many people as possible, including users with disabilities. This statement describes our standards, the current conformance status, and how to report a barrier.

1. Our standard

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the W3C. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities. Where applicable, our work also references the European Accessibility Act, EN 301 549, and Section 508 of the US Rehabilitation Act.

2. Current conformance status

The Service is partially conformant with WCAG 2.2 Level AA. “Partially conformant” means that some parts of the content do not yet fully conform to the standard. We are actively working to identify and address gaps.

3. What works well today

  • Semantic HTML with logical heading order, landmark regions, and ARIA labels on interactive widgets.
  • Full keyboard navigation through nav, search, command palette (⌘K), forms, and skill detail pages.
  • Visible focus indicators on all interactive elements; focus is managed when modals and popovers open and close.
  • Sufficient colour contrast in the dark theme, verified against WCAG 1.4.3 (4.5:1 for body text, 3:1 for large text and UI components).
  • Reduced-motion support — animations and parallax respect the user agent's prefers-reduced-motion setting.
  • Right-to-left layout support for Arabic, with the html dir attribute switching automatically based on the selected locale.
  • Skip-to-content links and aria-live regions for asynchronous notifications.

4. Known limitations

Despite our efforts, the following areas may not yet meet the WCAG 2.2 AA bar:

  • Some user-submitted README markdown contains images without alternative text. We cannot retroactively author alt-text for third-party content; the rendered page exposes the missing text so screen-reader users are not silenced.
  • A small number of legacy code-snippets use horizontal scrolling rather than wrapping; we are migrating to wrap-by-default.
  • The terminal-styled illustrations on marketing pages may convey information using colour alone in places. We are auditing each.

5. Assistive technology compatibility

The Service is designed to work with current versions of the following assistive technologies on current major browsers:

  • VoiceOver on macOS Safari and iOS Safari.
  • NVDA and JAWS on Windows Chrome and Edge.
  • TalkBack on Android Chrome.
  • System-level zoom up to 200% without horizontal scrolling at common viewport widths.

6. Reporting accessibility barriers

If you encounter a barrier — a feature you can't use, a contrast that fails, content that your assistive technology can't reach — please tell us so we can fix it. Include:

  • The URL where the issue occurs.
  • A description of the problem and what you were trying to do.
  • The browser and assistive technology you were using.

Email info@claudeskil.com. We aim to acknowledge within 3 business days and to provide a substantive response within 10.

7. Formal complaints

If you are not satisfied with our response and you reside in the European Economic Area or the United Kingdom, you have the right to contact your national enforcement body for the European Accessibility Act. In the United States, you may contact the U.S. Department of Justice or your state attorney general's office regarding ADA Title III access concerns.

8. Continuous improvement

Accessibility is a continuous effort. We track open accessibility issues alongside other engineering work, prioritise them by severity, and include accessibility checks in our review process. We welcome contributions and feedback from users and the broader community.

9. Contact

Accessibility: info@claudeskil.com