Accessibility Statement

Community Access is committed to ensuring digital accessibility for people of all abilities. This page describes our conformance status and how to report barriers.

Conformance Status

This website aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities.

We believe this site fully conforms to WCAG 2.2 Level AA. If you experience any accessibility barriers, please let us know.

Technical Specifications

Accessibility of this website relies on the following technologies:

  • HTML
  • CSS
  • JavaScript
  • WAI-ARIA

These technologies are relied upon for conformance with the accessibility standards used.

What We Do

  • Semantic HTML - We use proper heading hierarchy, landmarks, lists, and native elements before ARIA. Buttons are <button>, not <div role="button">.
  • Keyboard navigation - Every interactive element is reachable and operable by keyboard. Tab order follows visual order. Focus indicators are always visible.
  • Color contrast - All text meets WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components).
  • Responsive design - The site works at all viewport sizes and zoom levels up to 400%.
  • Reduced motion - We honor prefers-reduced-motion by eliminating animations and transitions when this preference is set.
  • Dark mode - We support prefers-color-scheme: dark with maintained contrast ratios.
  • Focus management - Skip links, visible focus rings using a high-contrast amber indicator, and proper focus management on dynamic content.
  • Alternative text - Decorative images use empty alt attributes. Meaningful images have descriptive alt text.
  • Link purpose - All links have descriptive text that makes sense out of context. Links that open in new tabs are indicated.

Testing

This site has been tested with:

  • NVDA screen reader with Firefox
  • VoiceOver with Safari on macOS
  • Keyboard-only navigation (Tab, Shift+Tab, Enter, Escape, Arrow keys)
  • axe-core automated accessibility scanner
  • Browser developer tools accessibility inspector
  • High contrast mode on Windows
  • 200% and 400% zoom levels

Known Limitations

  • Dynamic GitHub API content - Some content (contributor lists, repository data, news feed) is loaded from the GitHub API. While we use loading states and descriptive structures, screen reader users may need to refresh the region after content loads.
  • External links - Links to GitHub, the workshop site, and other external resources follow those sites' accessibility practices, which we do not control.

Feedback

We welcome your feedback on the accessibility of this website. If you encounter accessibility barriers, please let us know:

We try to respond to accessibility feedback within 3 business days.

Compatibility

This website is designed to be compatible with:

  • Recent versions of Chrome, Firefox, Safari, and Edge
  • NVDA, JAWS, VoiceOver, Narrator, and Orca screen readers
  • Speech recognition software
  • Screen magnification tools
  • Operating system accessibility features (high contrast, reduced motion, dark mode)

Assessment Approach

Community Access assesses the accessibility of this website through the following approaches:

  • Self-evaluation by developers who use assistive technology daily
  • Use of our own accessibility agent tools during development
  • Automated testing with axe-core
  • Manual keyboard and screen reader testing

This statement was last updated on .