Last reviewed: March 2026

Our Commitment

Designing for Accessibility is dedicated to making our website accessible to all people, regardless of disability or technology. We believe that accessibility is not a feature. It's a fundamental requirement for an inclusive and equitable digital experience.

This accessibility statement outlines our commitment, the standards we target, our technical approach, and how to report accessibility issues.

Standards We Target

We aim for WCAG 2.1 Level AA compliance across all pages and content. WCAG (Web Content Accessibility Guidelines) is the internationally recognized standard for web accessibility, developed by the World Wide Web Consortium (W3C) Web Accessibility Initiative.

Level AA represents a good balance between accessibility and practical implementation, and is the standard required by U.S. Section 508, the ADA, and most government and enterprise accessibility requirements.

Technical Approach

Semantic HTML

We build our site with semantic HTML5 elements that clearly communicate document structure. Proper heading hierarchy, landmark regions (nav, main, footer), and semantic elements (button, article, section) help assistive technologies understand the page structure.

Keyboard Navigation

All interactive elements on this site are fully keyboard accessible. You can navigate the entire site using the Tab key, and interact with buttons, links, and form elements using Enter or Space. Focus indicators are visible on all interactive elements.

Screen Reader Testing

We regularly test our site with screen readers, including NVDA (Windows) and VoiceOver (macOS). All content is announced clearly, and interactive elements have proper accessible names and roles.

Colour Contrast

Text and interactive elements meet WCAG AA colour contrast ratios (4.5:1 for normal text, 3:1 for large text). We avoid relying on colour alone to communicate information.

Responsive Design

Our site is designed to be fully responsive and accessible across all device sizes, from large desktop monitors to mobile phones. Touch targets are appropriately sized for mobile users.

ARIA Implementation

Where needed, we use ARIA (Accessible Rich Internet Applications) to add semantic information and improve screen reader experience. ARIA is used judiciously and only where native HTML cannot express the needed semantics.

What We Do Well

  • Clear, descriptive page titles that indicate page content
  • Proper heading hierarchy (H1, H2, H3, etc.) throughout articles
  • Alternative text for meaningful images
  • Descriptive link text that makes sense out of context
  • Form labels and error messages for all interactive elements
  • Sufficient colour contrast throughout the site
  • Skip navigation link to jump to main content
  • Table of contents with linked headings on article pages

Known Limitations

While we strive for full accessibility, there are some known limitations:

  • Data tables in VPAT documentation. Complex comparison tables may be challenging for screen reader users. We are working to simplify these or provide alternative formats.
  • Code examples. Code blocks are presented as plain text, which may be less accessible for some users. We are exploring better ways to present code examples.
  • External content. Links to external resources (like W3C documentation) may have their own accessibility limitations that are beyond our control.

Feedback & Accessibility Issues

We welcome feedback on the accessibility of this site. If you encounter any barriers to accessing content, please let us know:

Please include:

  • The page or section where you encountered the barrier
  • What assistive technology or browser you're using
  • A description of what you expected vs. what you experienced

We'll investigate your report and work to resolve accessibility issues as quickly as possible.

Third-Party Content

This site contains links to external resources and social media. We are not responsible for the accessibility of external websites, but we encourage all linked resources to follow WCAG guidelines.

Continuous Improvement

Accessibility is an ongoing commitment, not a destination. We regularly review and test our site for accessibility issues, implement fixes, and stay current with WCAG guidelines and best practices. We update this statement annually, and more frequently if significant changes are made to the site.