Accessibility.

Accessibility Statement.

What we have done, where we fall short, and how to tell us about anything we have missed. Targeting WCAG 2.2 Level AA across the site.

Bright Loop Media is committed to making brightloopmedia.co.uk accessible to everyone, including people with disabilities. We design and build with accessibility as a baseline requirement, not an afterthought.

This statement explains what we do, where we know we fall short, and how to tell us about anything we have missed.

Conformance Standard

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 is the international standard maintained by the W3C and is the standard required for UK public-sector websites.

You can read the full WCAG 2.2 specification here: https://www.w3.org/TR/WCAG22/

What We Have Done

The current website includes the following accessibility features:

  • Semantic HTML. Pages use proper heading hierarchy and landmark regions so screen readers can navigate them.
  • Keyboard navigation. All interactive elements (links, buttons, forms, the navigation menu) can be operated with a keyboard alone.
  • Visible focus indicators. Every interactive element shows a visible outline when focused.
  • Colour contrast. Body text and interactive elements meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text).
  • Reduced motion. Animations respect the operating system's "reduce motion" preference. If you have this setting enabled, motion-heavy effects are softened or removed.
  • Image alt text. Every meaningful image has a descriptive alt attribute. Decorative images are marked as decorative so screen readers skip them.
  • Form labels. Every input has a programmatically associated label.
  • Responsive design. Pages reflow correctly on screens from 320px wide upwards without horizontal scrolling.
  • Plain English. We aim for clear, jargon-light writing throughout the site.

Known Issues

We are honest about the things we have not yet fixed. As of the last review date, we are aware of the following:

  • Custom video and animated backgrounds. Some hero sections use motion that may be distracting for users with vestibular conditions, even with reduced-motion preferences. We are auditing every animation and tightening the reduced-motion rule sitewide.
  • Third-party embeds. Where we embed external content (for example a Calendly booking widget on the contact page in future), we cannot guarantee the same level of accessibility as the rest of the site. We choose providers with accessible defaults and monitor their compliance.
  • PDF documents. Some downloadable PDFs are not yet fully accessible (e.g. tagged for screen readers). We are working through them.

If you find an issue not listed here, please tell us (see "Feedback" below).

How We Test

We test accessibility through:

  • Automated checks using axe-core, integrated into our build pipeline so issues are caught before deployment.
  • Manual keyboard-only navigation on every new page or component.
  • Manual screen reader spot-checks using VoiceOver (macOS) and NVDA (Windows).
  • Colour contrast checks during design.
  • Real-device testing on iOS Safari and Android Chrome.

We do not currently use a formal third-party accessibility audit. We are exploring this for 2026.

Feedback

If you have difficulty using this website, or you spot an accessibility issue we have missed, we want to know.

We will acknowledge your message within 2 working days and aim to respond substantively within 10 working days.

If your enquiry is urgent, please mention this in your email and we will prioritise it.

Enforcement

If you are not satisfied with how we respond to your accessibility feedback, you can contact the Equality and Human Rights Commission (EHRC), the body responsible for enforcing accessibility regulations in the UK.

Technical Details

This website is built with React, TypeScript, and TailwindCSS, prerendered to static HTML and served from Netlify. The technical specification has no inherent barriers to accessibility. Any issues are implementation-level and tracked openly in our project repository.

Review Cycle

We review this statement at least every 12 months, and after any major site change. The "Last reviewed" date at the top of this statement reflects the most recent review.