OurAccessibilityStatement

Last reviewed: 17 October 2026 · Version 2.0

Enby Meaning™ Media is for everyone, and that includes disabled and neurodivergent readers. We want enbymeaning.com to work for people who use screen readers, keyboards, voice control, magnification and other assistive tools, and on any device.

What we aim for #

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We treat accessibility as ongoing work. We will not claim it is finished.

Back to contents

What we do #

  • We write real headings, lists and tables, so screen readers can move around a page.
  • We add alternative text to images, and we are fixing older posts that lack it.
  • You can use the site with a keyboard alone, with a visible focus outline.
  • We design for phones and for zoom up to 200%, with no sideways scrolling for reading text.
  • We keep text and links at a readable contrast.
  • We respect your device settings for reduced motion, high contrast and larger text.
  • Our policy pages have a linked contents list, and their tables work as stacked cards on small screens.

Back to contents

What we have tested #

Back to contents

Where we fall short #

  • Embedded content. Videos and posts from sites such as YouTube, Instagram and TikTok are made by other companies. We cannot fix their players, but we try to choose ones with captions.
  • Ads. Display ads are served by Google AdSense, and we do not control how accessible they are.
  • Older posts. Some older posts may still have missing alt text or unclear link text.
  • Video and audio. Not every video has captions or an audio description yet.

Back to contents

Our conformance status #

We believe enbymeaning.com partially conforms with WCAG 2.2 Level AA. "Partially conforms" means most of the site meets the standard, and some parts do not yet, for the reasons above.

Back to contents

Tell us about a barrier #

If you cannot use something on the site, or find it hard to, please tell us. Email care@enbymeaning.com with the subject "Accessibility Feedback" and include:

  1. the page address;
  2. what you were trying to do;
  3. what went wrong;
  4. the browser, device and assistive technology you use, if you are happy to share it.

We reply within five working days and aim to fix problems quickly. If you need content in another form, such as plain text, large print or audio, ask and we will try to provide it.

Back to contents

If you are not happy with our response #

You can contact the body that handles disability rights where you live, for example the Human Rights Commission in New Zealand, the Equality and Human Rights Commission in Great Britain, or the data or equality body in your EU country.

Back to contents

What we are working on #

What we are working on
Status What
In progress ARIA labels for interactive parts of the site
In progress Audio descriptions and captions for videos
In progress Accessible forms, with clear labels and focus states
Planned A full review against WCAG 2.2
Planned Regular testing with disabled readers from our community
Planned Translating key accessibility information into other languages

Back to contents

Version history #

Version history of this statement
Version Date What changed
1.0 September 2024 First statement
1.1 May 2025 Added the roadmap and version history
2.0 17 October 2026 Moved to WCAG 2.2, added what we tested, where we fall short, and how to reach us

Back to contents