What can I claim about Coassemble's accessibility?

The Statement of Conformance, exactly what it covers, and how to word an accessibility claim in a procurement response.

Coassemble has been awarded a Statement of Conformance for WCAG 2.2 Level AA, independently verified by digital accessibility specialists Modality Co. The Coassemble learner experience met all 56 success criteria across 13 guidelines at both Level A and Level AA.

If your platform embeds the Coassemble learner experience, this conformance extends to the course-taking experience within your platform.

The assessment covers the Classic learner experience. Courses built in the new builder use a rebuilt learner view, which is covered separately below.

What this means for your platform

Learners using your platform, including people with disability, can expect a high standard of accessibility when completing training through the embedded Coassemble learner experience.

Key outcomes include:

• Screen reader support: learners using assistive technologies such as JAWS or NVDA can navigate and complete courses effectively.
• Keyboard-only navigation: full support for learners who rely on a keyboard rather than a mouse.
• Text and display adaptability: content remains usable for learners who resize text in their browser or use Windows High Contrast Mode.

You may reference the Statement of Conformance in customer-facing accessibility documentation, procurement responses, and internal compliance reporting.

Access the Statement of Conformance

The Statement of Conformance is available via the Coassemble Trust Centre:

• https://trust.coassemble.com/

How conformance was assessed

Modality Co conducted the assessment in accordance with the Web Content Evaluation Methodology (WCAG-EM 1.0), the standard methodology used to support a valid WCAG conformance claim.

Testing was completed across multiple rounds and included:

• Chromium-based web browsers
• JAWS and NVDA screen readers
• Browser text resizing
• Windows High Contrast Mode

The evaluation was signed off by:

• Matthew Putland, Digital Accessibility Specialist (Modality Co)
• Rosie Putland, Principal Accessibility Specialist (Modality Co)

Scope: what this conformance does and does not cover

When communicating accessibility claims to customers, it's important to be precise about what's included.

Covered

• The Classic learner experience that delivers courses, as assessed by Modality Co.

Not covered

• The content inside courses.
• The new builder learner experience.
• The Screen Player embeddable, which renders a single screen inside your own application. It uses the new builder's learner view, so it sits outside the assessed scope for the same reason. It's worth being explicit about this one, because a partner embedding single screens is embedding something the Statement of Conformance doesn't name.

A further consideration with Screen Player: because your application can hide the built-in navigation and supply its own controls, the accessibility of that surrounding navigation is yours rather than Coassemble's. If you replace the navigation, keyboard operability and screen reader labelling of your controls are part of what a customer's accessibility review will look at.

Course content is the creator's responsibility

Course content accessibility remains the responsibility of the course creator. Your customers should ensure the courses they build follow accessible content practices, including:

• adding alt text for meaningful images,
• using a clear heading structure,
• maintaining sufficient colour contrast,
• setting the reading order where the visual arrangement doesn't match the order things should be read, and
• checking what they've hidden from mobile. The new builder lets an author hide a block on small screens, which is useful for a wide table but removes that content entirely for a learner on a phone. If the hidden block carries information a learner needs, it has to exist somewhere else in the course.

Where the new builder stands

The new builder's rebuilt learner view is built to the same WCAG 2.2 Level AA standard, applying everything learned from the Modality Co audit. Coassemble's own accessibility testing shows it meets WCAG 2.2 Level AA. It has not been independently verified at this stage.

The distinction matters in a procurement context, so use these two claims precisely:

• For the Classic learner experience, cite the Statement of Conformance. It's an independently verified claim you can point a customer to on the Trust Centre.
• For courses built in the new builder, and for Screen Player, describe Coassemble's own accessibility testing. Don't cite the Statement of Conformance for these, because the assessment didn't cover them.

If a customer's accessibility requirement specifically depends on independent third-party verification, the Statement of Conformance applies to the Classic learner experience only. Email vip@coassemble.com if you need help wording a response.

One thing worth knowing about the Hotspot block: it places interactive labels over an image, which assistive technology does not always interpret clearly. If critical information sits in a hotspot, provide it in text elsewhere on the screen. The block supports reading order, so you can set the order pins are read out.

Ongoing accessibility commitment

WCAG 2.2 Level AA conformance is a significant milestone, but accessibility is an ongoing effort. Coassemble continues testing and improving the learner experience to maintain conformance over time.

Support

If you have questions about accessibility, or if your customers encounter barriers, contact vip@coassemble.com.