Accessibility Statement

Our commitment to making Explore Moor calm, readable, and usable.

This Accessibility Statement is written in plain English. It explains what we are aiming for, what we currently support, where we still need to improve, and how you can tell us if something gets in your way.

Last updated: May 2026

Explore Moor is built around story, writing, video, newsletter links, and real-life updates. Accessibility matters because people should not have to fight the website before they can read, watch, contact us, or follow the journey.

We want Explore Moor to feel calm, readable, navigable, and practical for as many people as possible, including disabled people, neurodivergent people, carers, tired people, anxious people, and anyone using assistive technology.

Explore Moor is a Moor & More Studio project, created by Millie Carter.

In plain English

We aim for calm design

Pages should be readable, spacious, predictable, and not overloaded with visual noise.

We support browser and device settings

You should be able to use browser zoom, larger text, screen readers, keyboard navigation, and device accessibility settings.

We do not claim perfection

Explore Moor is still developing. Some areas, especially embeds, videos, and third-party tools, may not be fully accessible yet.

Video and embeds need care

YouTube, Substack, social embeds, and future third-party tools may have accessibility limits outside our control.

Feedback helps us improve

If something blocks you, confuses you, or makes the site hard to use, we want to know.

What we are aiming for

1. Our approach

Explore Moor should aim to be:

calm to look at
easy to read
easy to navigate
mobile-friendly
keyboard-friendly
respectful of people’s time and energy
not full of unnecessary movement, urgency, or distraction
written in clear language where possible
structured with meaningful headings
usable with assistive technologies where possible

Accessibility is not only technical. It is also about reducing overwhelm, avoiding clutter, and making information easier to understand.

2. Standards we aim towards

We aim to work towards recognised accessibility good practice, including WCAG 2.2 AA where reasonably possible.

Explore Moor is still evolving and has not yet had a full independent accessibility audit, so we are not claiming full compliance at this stage.

What we currently support

3. Reading and navigation

Explore Moor should support:

readable text
generous spacing
clear headings
predictable layouts
visible focus states
sensible colour contrast
keyboard navigation
mobile-friendly layouts
plain-language content where possible
meaningful link text
forms with clear labels
buttons and links that make sense

4. Cognitive load and neurodivergence

Explore Moor should also be easier to use for people who may be neurodivergent, anxious, fatigued, overwhelmed, or dealing with brain fog.

We aim to reduce cognitive load by:

keeping pages calm
avoiding unnecessary clutter
using clear headings
avoiding manipulative urgency
breaking long information into sections
using plain language where possible
making actions predictable
keeping forms as simple as possible
explaining what happens next

This matters because Explore Moor may be read by people who are tired, caring, grieving, researching, disabled, unwell, or trying to make big decisions.

5. Contact forms

Contact forms should aim to:

have clear labels
explain what information is needed
avoid asking for unnecessary information
provide clear success/failure messages
be usable by keyboard
be readable on mobile
avoid making people repeat themselves where possible

6. Newsletter and Substack

Explore Moor Journal is hosted on Substack.

Substack has its own accessibility standards, tools, and limitations. We do not fully control the Substack platform.

if a Substack embed is used, we will try to provide a direct external link too
if the embed is blocked by cookie choices, users should still have a way to open the newsletter directly
newsletter content should aim to be readable and clearly structured

7. Video and YouTube

Explore Moor may use YouTube.

Video accessibility matters. Where possible, videos should be supported by captions, clear titles, useful descriptions, and, where practical, written summaries or transcripts.

We may not be able to provide perfect captions, transcripts, or summaries for every video immediately, but this is something we should improve over time.

YouTube has its own player and accessibility features
embedded videos may be blocked until embedded content consent is given
users should be able to open videos directly on YouTube where possible

8. Social media and third-party platforms

Explore Moor may link to Facebook, Instagram, YouTube, Substack, and future platforms.

Third-party platforms have their own accessibility strengths and limitations. We cannot fully control them, but we can try to offer clear links, avoid relying only on one platform, and keep important information available on our own site where possible.

What users can control themselves

9. Browser and device settings

Many people use their own browser, operating system, or assistive technology settings.

Explore Moor should work as well as possible with:

browser zoom
text size
display scaling
contrast settings
reduced motion settings
screen readers
keyboard navigation
voice control
colour filters or display adjustments

We do not currently provide built-in font size controls or contrast mode controls on the site itself. If those are added later, this statement should be updated.

We do not want to pretend we offer accessibility controls that do not exist yet. For now, the site should support the controls people already use on their own devices and browsers.

Known limitations

10. Images, media, and embeds

Known or possible limitations may include:

some images may not yet have ideal alt text
some embedded content may not be fully accessible
some video captions/transcripts may be incomplete or missing
third-party embeds may behave differently across browsers/devices
cookie-gated embeds may require an extra step

Where possible, we should provide context or alternatives when embedded content is important, especially if consent has not been granted.

11. Forms, errors, and account/support features

Possible limitations:

form error messages may need refinement
success/failure states may need testing
future support/payment/community features may need extra accessibility review
mobile layouts may need checking as new pages are added

12. Third-party content

This includes:

Substack
YouTube
Facebook
Instagram
payment/support platforms if added later
analytics or embedded tools if added later

We cannot fully control third-party platforms, but we can avoid making them the only route to important information where possible.

13. Known audit status

Explore Moor has not yet had a full independent accessibility audit.

We aim to improve these areas over time.

Feedback and improvements

14. What we will do as the site grows

As Explore Moor develops, we should keep checking accessibility when adding or changing:

new pages
newsletter embeds
YouTube/video embeds
contact forms
legal pages
support or membership features
social embeds
image-heavy pages
resource/download pages
mobile navigation

Accessibility is part of the build process, not something to sprinkle on at the end.

Accessibility checklist for future features

Before adding a new feature, ask:

Can this be used with a keyboard?
Is the focus state visible?
Are labels and instructions clear?
Are errors readable and helpful?
Does it work on mobile?
Does it respect browser zoom and text scaling?
Does it avoid unnecessary motion or visual clutter?
Does it rely on colour alone?
Is the language clear enough?
Is the third-party embed consent-gated and accessible?

16. Reporting accessibility issues

If you find something difficult to use, confusing, inaccessible, or frustrating, please tell us.

Helpful details may include:

what page or feature you were using
what happened
what you expected to happen
what device or browser you were using
whether you were using a screen reader, keyboard navigation, zoom, contrast settings, or other assistive tools

You do not need to write a perfect bug report. A simple message is enough.

17. Contact

For accessibility feedback, questions, or support, please contact us.

Get in touch

We are always looking to improve.