Skip to content
Belonging Works
Join free

Accessibility

A site that works for everyone.

The A in DEIA is for accessibility. Inclusion work that is not accessible is not inclusion. This site is built to that standard, and we want to hear from you when we miss the mark.

Our commitment

WCAG 2.2 AA, with the work to back it up

Belonging Works targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at the AA level across our public website and member experience.

That commitment includes keyboard navigation for every interactive element, sufficient colour contrast in all text and key UI states, descriptive alternative text on meaningful images, captions on every webinar and recorded session, semantic structure for screen readers, and clear focus indicators.

We don't consider WCAG conformance a finish line. We test with real assistive technology, work with practitioners with disabilities on our content, and treat every barrier report as a priority issue, not a backlog item.

What this means in practice

How we build, test, and learn

Built in, not bolted on

Every page is designed to be operable by keyboard, screen reader, and switch from the first commit, not patched at the end.

Captions on everything

Every webinar, community call, and recorded session has accurate captions. We use human review on top of automatic transcripts.

Plain language by default

We write at a clear reading level, define jargon, and avoid metaphor-heavy openings. Plain language is an access feature.

Real testing

We test with screen readers (NVDA, VoiceOver, JAWS), keyboard-only navigation, and zoom up to 400%. We also pay testers with disabilities, where we can.

Found a barrier? Tell us.

If anything on Belonging Works does not work for you, we want to hear about it. We treat accessibility issues as priority, not a nice-to-have.

Email us at accessibility@belongingworks.com with:

  • The page or section where you ran into the problem
  • What you were trying to do
  • What happened instead
  • The assistive technology, browser, or device you were using, if you can share it

We aim to acknowledge every report within one business day and fix the issue or share a clear timeline within five business days.