Accessibility

We strive to meet WCAG 2.2 AA. Our site includes semantic landmarks, keyboard navigation, focus styles, color contrast, and skip links. We test regularly with automated tools and assistive technologies. Please contact us if you encounter any issues and we will remediate promptly.

Standards and features

WCAG 2.2 AA targets for contrast, focus, and navigation: We meet WCAG 2.2 AA contrast ratios for text and interactive elements. Focus indicators are visible and clear. Navigation is consistent and predictable. These practices ensure content is perceivable and operable.

Accessible forms with labels, descriptions and error handling: Forms include labels, descriptions, and error messages that are clear and associated with inputs. Required fields are indicated. Error messages are descriptive and help users correct mistakes. These practices ensure forms are usable by everyone.

Role and heading hierarchy for assistive tech: We use semantic HTML and ARIA roles appropriately. Headings follow a logical hierarchy. Landmarks help users navigate. These practices ensure assistive technologies can understand and navigate content.

Regular automated and manual testing with axe and screen readers: We test with automated tools like axe-core and manual testing with screen readers like NVDA, JAWS, and VoiceOver. We fix issues promptly and retest to ensure fixes work. These practices ensure accessibility remains strong over time.

Accessible design

Accessible design means content is usable by everyone, including people with disabilities. We design with accessibility in mind from the start, not added later. Color is not the only way to convey information. Text is readable and resizable. Interactive elements are large enough and have clear targets. These practices ensure content is usable by everyone.

Keyboard navigation ensures all functionality is available via keyboard. Focus order is logical. Skip links help users bypass repetitive content. Focus indicators are visible. These practices ensure keyboard users can navigate and use all features.

Semantic HTML provides meaning to assistive technologies. Headings structure content. Lists group related items. Links and buttons are labeled clearly. These practices ensure assistive technologies can understand and communicate content accurately.

Testing and remediation

We test accessibility regularly with automated and manual methods. Automated testing catches common issues quickly. Manual testing with assistive technologies validates real-world usage. We fix issues promptly and retest to ensure fixes work. These practices ensure accessibility remains strong over time.

When issues are reported, we investigate promptly and fix them. We communicate fixes clearly and test to ensure they work. We learn from issues to prevent similar problems. These practices ensure accessibility improves continuously.

Report accessibility issues

If you encounter accessibility issues, please use our contact form. We investigate promptly and fix issues. We appreciate your feedback and use it to improve accessibility.