dium.io
Book a demoStart free

Accessibility statement

The standard we aim for, where we fall short today, and how to reach us.

Last updated
Draft for review. Confirm bracketed items and have counsel review before publishing.

In short

  • Target: WCAG 2.2 level AA.
  • Status: partially conformant, self-assessed, no independent audit.
  • Report a barrier to [email protected] with the subject Accessibility.

Our commitment

We want everyone to be able to ask questions, answer them and join live sessions on Dium, including people who use screen readers, keyboards, magnification, voice control or other assistive technology.

Conformance status

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

Dium is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform yet. We have not had an independent audit.

This statement covers this website (dium.io) and the Dium app. [Confirm whether the app has been evaluated at all, or narrow this statement to the website]

What we have done

On this website:

  • A skip link to jump past the menu to the main content.
  • Form labels sit above their fields, and errors are described in text, not only in colour.
  • Tables have proper row and column headers.
  • Icon-only buttons have text labels for screen readers.
  • Animations are turned off when your system asks for reduced motion.
  • Status is never shown by colour alone. For example, "Yes", "No" and "Limited" are written out in tables.

Known gaps

These are the problems we know about. We are listing them so you can plan around them.

  • [Confirm: live updates in the app, such as new replies and DMs, may not be announced to screen readers]
  • [Confirm: images uploaded by members often have no text alternative]
  • [Confirm: some app dialogs may not trap and return keyboard focus correctly]
  • [Confirm: colour contrast in custom Flow brand colours is set by Flow owners and may be too low]
  • [Confirm: PDFs uploaded by members may not be tagged for accessibility]
  • Live sessions open in Google Meet or Zoom. Their accessibility, including captions, depends on those services.
  • When Dium is shown inside a partner's own website, the partner's pages around it are outside our control.

How we checked

We evaluated Dium by self-assessment: [method, e.g. keyboard-only testing, screen reader testing with NVDA and VoiceOver, and an automated checker]. Last evaluated [date].

We do not use an accessibility overlay widget, and we do not claim that any tool makes Dium fully accessible.

Compatibility

Dium relies on HTML, CSS, JavaScript and WAI-ARIA. It is designed to work with current versions of major browsers and the assistive technology built into them. [List the browser and screen reader combinations tested]

Tell us about a barrier

If something on Dium does not work for you, email [email protected] with the subject line "Accessibility". Tell us the page, what you were trying to do, and the browser and assistive technology you use.

We reply within [response time, e.g. 5 business days]. If you need information from a page in another format, ask and we will send it.