Accessibility

1. Our commitment

Onika L. Dainty and SturdyCloud are committed to providing a respectful digital experience for people with disabilities. We aim to meet WCAG 2.2 Level AA where reasonably possible and to consider Ontario accessibility requirements, including the Accessibility for Ontarians with Disabilities Act.

This statement describes an ongoing goal. It is not a claim that every page, document, or third-party service currently meets every success criterion.

2. Accessibility features

The website includes:

• semantic headings, landmarks, lists, buttons, and links;
• a skip link for moving directly to the main content;
• keyboard-accessible navigation and visible focus indicators;
• descriptive alternative text where images communicate information;
• text and controls designed for readable contrast;
• responsive layouts that support zoom and smaller screens;
• plain-language labels and consistent navigation;
• reduced-motion support for visitors who request it; and
• captions, transcripts, or text alternatives when media is published and those materials are available.

3. Known limitations

Some content may still present accessibility limitations, including:

• some small secondary text and accent colours that need stronger colour contrast;
• the speaking reel, which still needs a verified accessible visual description and any required captions or transcript;
• the downloadable speaker kit, which still needs a complete tagged-PDF and reading-order review;
• older PDF files or externally hosted documents that may not be fully accessible;
• third-party websites, video players, social platforms, and embedded services outside our control; and
• complex personal stories that may benefit from an alternate format or additional reading support.

We will review reported barriers and prioritize fixes based on impact, feasibility, and the needs of the person affected.

4. WCAG 2.2 AA review findings

A source-level review of 150 website pages and an automated WCAG 2.2 AA scan of representative page types were completed on October 7, 2026. The review confirmed that every source-scanned page includes a language declaration, one main content landmark, one H1 heading, a skip link, alternative-text attributes for images, labelled form controls, and a heading structure without skipped levels. No duplicate element identifiers were found.

The automated review found one recurring violation category on the tested page types: insufficient colour contrast in some small teal, coral, muted, and pale secondary text. It also found a homepage reflow issue at 320 CSS pixels. The reflow issue and the mobile menu’s changing accessible name were corrected and retested during this review.

The following work remains before full WCAG 2.2 Level AA conformance can be claimed:

• adjusting the remaining teal, coral, muted, and pale secondary text combinations to meet minimum colour-contrast requirements;
• providing or confirming an accessible alternative for the speaking reel;
• testing and remediating the downloadable speaker kit as a tagged, keyboard-readable PDF;
• completing manual keyboard testing, including focus order, focus visibility, menu operation, and access without a pointer;
• testing with current screen readers, including VoiceOver and NVDA where available;
• completing manual testing of text resizing, browser zoom, reflow, orientation, target size, and content shown on hover or focus; and
• reviewing third-party and future embedded content as it is added.

Automated checks can identify only some accessibility barriers. Manual testing and feedback from people who use assistive technology remain necessary.

5. Improvement approach through May 2027

Accessibility improvements will be made during regular website updates, with a broader accessibility upgrade planned for May 2027.

• October to December 2026: correct high-impact issues during scheduled updates, beginning with colour contrast, accessible menu names, media alternatives, and the speaker-kit review.
• January to April 2027: add repeatable automated checks, test representative page types with a keyboard, screen readers, zoom, reflow, and mobile devices, and maintain a prioritized barrier log.
• May 2027: complete the planned site upgrade, remediate confirmed WCAG 2.2 AA failures, retest the full set of page templates, and publish an updated accessibility status.
• Ongoing: include accessibility checks in content and design updates, periodically sample older Journal entries, and address reported barriers as promptly as reasonably possible.

This approach supports continuous improvement. It does not postpone urgent fixes when a barrier prevents someone from accessing information or using the website.

6. Alternate formats and communication support

If you need information in another format or need help accessing a page, tell us what you need. Examples may include plain text, a larger print-ready document, a transcript, a simplified explanation, or help locating the same information through another channel.

We will work with you to identify a suitable option where reasonably possible.

7. Report an accessibility barrier

For Ontario’s official website accessibility guidance, visit How to make websites accessible.