Accessibility
A clear experience should be an accessible one.
EMBOK is working toward an experience that people can understand and operate across devices, assistive technologies, input methods, and motion preferences.
Last reviewed:
Our target
The design and engineering target for embok.ca is the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Accessibility is treated as an ongoing product responsibility rather than a one-time certification.
What the experience is designed to support
- Keyboard navigation with a logical order and visible focus.
- Semantic headings, landmarks, controls, labels, status messages, and error guidance.
- Screen-reader-friendly navigation, disclosure controls, assessment questions, progress, and results.
- Text resizing and browser zoom without hidden content or horizontal scrolling.
- Colour contrast and status communication that does not rely on colour alone.
- Reduced-motion alternatives for transitions and smooth scrolling.
- Responsive touch targets and layouts at mobile, tablet, desktop, and high zoom.
Testing approach
Accessibility reviews should combine automated checks with manual keyboard testing, screen-reader checks, zoom and reflow testing, reduced-motion testing, colour-contrast review, and representative mobile and desktop browsers. Automated testing alone cannot confirm conformance.
Ongoing improvement areas
Areas that require continued testing as the product evolves include:
- Focus and live announcements throughout the dynamic assessment and results experience.
- Responsive product dashboards, charts, framework explorers, and data summaries.
- Third-party email, scheduling, analytics, and embedded services when they are enabled.
- Any future downloadable documents, which must have an accessible source or equivalent format.
- Compatibility at 200% and 400% zoom and with Windows high-contrast or forced-colour modes.
Feedback and accommodation
If content or a function is difficult to use, EMBOK intends to provide the information or service in a reasonable alternative format and use the feedback to improve the experience. Include the page, task, browser or assistive technology, and the format that would help, but do not send sensitive personal information.
Requires operational review: Add a dedicated accessibility email address, phone number, or accessible feedback form that accepts messages from people without a company email. Define acknowledgement and resolution targets before publishing a promised response time.
Third-party content
EMBOK may link to or rely on third-party services that it does not fully control. Accessibility issues in those services should still be documented, raised with the provider, and addressed through an alternative path where reasonably possible.