Skip to main content

Accessibility Statement

Last updated: July 2026

Our Commitment

We are committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to the best of our ability.

Standards Target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards. These guidelines define how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

Accessibility Features Implemented

  • βœ“Semantic HTML β€” Proper landmark structure using <header>, <main>, <nav>, <footer>, and <search> elements
  • βœ“Skip Navigation β€” A skip-to-content link is available at the top of every page
  • βœ“Keyboard Navigation β€” All interactive elements are accessible via keyboard
  • βœ“ARIA Attributes β€” Appropriate ARIA labels, expanded states, current page markers, and autocomplete roles
  • βœ“Visible Focus Indicators β€” Custom focus-visible ring styles on all interactive elements
  • βœ“Color Contrast β€” All text meets WCAG AA minimum contrast ratios
  • βœ“Reduced Motion Support β€” Respects prefers-reduced-motion settings
  • βœ“Responsive Design β€” Fully functional across screen sizes from mobile to desktop
  • βœ“Accessible Autocomplete β€” Search autocomplete uses combobox pattern with proper ARIA roles
  • βœ“Screen Reader Support β€” Descriptive labels, alt text on icons, and proper heading hierarchy
  • βœ“Accessible Accordions β€” Collapsible sections use proper ARIA expanded states
  • βœ“Accessible Tables β€” Data tables have proper <thead> and <th> scope attributes
  • βœ“Form Labels β€” All form inputs have associated labels or aria-label attributes

Known Limitations

While we strive for full accessibility compliance, some areas may have limitations:

  • β€’Some third-party content from external APIs may not be fully accessible
  • β€’Historical label documents may contain complex table structures
  • β€’Loading states and dynamic content updates may not be fully announced by all screen readers

Ongoing Efforts

Accessibility is an ongoing process. We regularly:

  • Review and test our platform with accessibility tools
  • Address accessibility issues reported by users
  • Incorporate accessibility best practices in new features
  • Stay current with WCAG guideline updates

Feedback

We welcome your feedback on the accessibility of this platform. If you encounter accessibility barriers or have suggestions for improvement, please:

  • Visit our contact page
  • Describe the specific accessibility issue you encountered
  • Include the URL of the page where you experienced the issue

Compatibility

This website is designed to be compatible with:

  • Latest versions of Chrome, Firefox, Safari, and Edge
  • Screen readers including NVDA, JAWS, and VoiceOver
  • Keyboard-only navigation
  • Browser zoom up to 200% without loss of functionality

Assessment Approach

We assess the accessibility of our platform through:

  • Automated accessibility testing tools
  • Manual testing with screen readers
  • Keyboard-only navigation testing
  • Regular code reviews for accessibility best practices

Note: This accessibility statement is reviewed and updated regularly as we continue to improve the accessibility of our platform.