Accessibility Standard
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as published by the World Wide Web Consortium (W3C). W3C+2wcag2.com+2
What We’re Doing to Improve Accessibility
To support accessibility, we have taken/are taking measures such as:
-
Incorporating accessibility into our web design and development process.
-
Using semantic HTML to ensure content is correctly structured for screen readers.
-
Ensuring that images have meaningful alt text where applicable.
-
Testing keyboard navigation so that all functionality is accessible without a mouse (where possible).
-
Using color contrast that supports readability for users with low vision.
-
Regularly reviewing and updating content to improve accessibility.
Known Limitations
While we are committed to accessibility, there might still be parts of our website that are not fully accessible. For example:
-
Some interactive elements (forms, maps, widgets) may not yet be fully optimized for keyboard-only navigation.
-
Certain images or media may not have alternative formats for all assistive technologies.
-
There may be compatibility issues with older browsers or less common assistive tools.
If you encounter a specific accessibility barrier, please let us know by contacting us (see below), and we’ll do our best to provide you with an alternative way to access the information or fix the issue.
Feedback & Contact Information
We welcome feedback on the accessibility of our website. If you experience any difficulties or have suggestions, please contact:
-
Email: [insert your contact email]
-
Phone: [insert phone number, if available]
When you contact us, please provide as much detail as possible about the problem (e.g., the web page, browser, and assistive technology you were using) so we can help you better.
Technical Details
Our website is built using technologies such as HTML, CSS, and JavaScript. We test across modern browsers (Chrome, Firefox, Safari, Edge) and strive for compatibility with common assistive technologies.
Ongoing Work
Accessibility is an ongoing effort. We plan to:
-
Conduct periodic accessibility audits (automated + manual)
-
Train our content creators and developers on accessibility best practices
-
Address reported barriers in priority order
-
Update this statement when there are meaningful changes
Why This Matters / Guidance (for your internal team)
-
According to W3C guidance, an accessibility statement should include: your commitment, the standard you’re aligning to, known limitations, contact info, and any work in progress. W3C
-
Many organizations reference WCAG 2.1 because it's a stable and widely-adopted standard. wcag2.com+1
-
It’s good to be transparent about limitations — it builds trust, and also gives you a roadmap for improvement.
-
Having a feedback channel is key; you might discover real-world barriers that automated testing doesn’t pick up.