Accessibility statement
Accessibility is part of the product.
This accessibility statement explains the current accessibility approach for the BaseLayer Digital site, the runtime controls available through the BaseLayer engine, the known limitations of the current implementation, and the route for accessibility feedback.
Statement scope
This statement covers the public BaseLayer Digital site.
The site is designed to adapt in front of the person using it rather than forcing a single fixed presentation. The runtime accessibility layer is intended to support visual comfort, reading support, focus clarity, motion reduction, and related adjustments without requiring the visitor to leave the page they were trying to use.
Accessibility approach.
The current site includes theme switching, palette changes, contrast changes, depth and transparency adjustment, motion reduction, reading-width control, typographic changes, stronger focus handling, talkback support where the browser permits it, and a saved-preferences layer so those choices can persist. The aim is to let visitors adapt the page without being forced into a separate reduced version of the site.
This statement does not present the site as independently certified. Its purpose is to set out the accessibility features currently built into the site, the limitations known at the time of publication, and the route for reporting a barrier so it can be reviewed properly.
Current engine capabilities
- Theme, palette, and contrast control
- Reading layout, text sizing, spacing, and font options
- Motion, transparency, and media-pressure reduction
- Focus, link, and control highlighting
- Talkback and page read-aloud support where the browser allows it
Implementation principles
- Semantic HTML and keyboard-safe interaction patterns
- Token-driven colour and type layers that adapt through the engine
- Preference persistence so the page reopens the way the visitor requested
WCAG position.
The site is designed with WCAG 2.2 AA principles in mind, including semantic structure, keyboard access, focus visibility, adaptable presentation, colour contrast, and reduced-motion support. This statement should not be read as a claim of independent certification or as a guarantee that every future browser, device, or third-party integration will remain free from error.
Known limitations and third-party boundaries.
Accessibility work is ongoing, and not every platform environment offers the same freedom as this custom frontend. Managed builder platforms and third-party integrations can impose layout, component, script, or embedding limits that make parts of the engine unavailable, reduced, or technically impractical unless explicitly scoped and supported for that environment.
If a third-party service, embed, booking widget, search component, or builder layer introduces its own accessibility limitation, that limitation sits with the relevant service provider unless BaseLayer Digital has explicitly agreed to own that layer in the project scope. The live site is delivered through Cloudflare, but Cloudflare is not intended to alter the semantics of page content; where delivery, caching, or network behaviour affects the timing of updates, that should be understood as infrastructure behaviour rather than as a deliberate accessibility feature.
Feedback.
If you find an accessibility issue on this site, need information in another format, or want to report a barrier that stops you using a page or control, please use the project contact route already provided to you if you are an existing client or correspondent. A public business contact route for general accessibility enquiries will be published separately when it is ready for public use.
- Reports should identify the page, the issue, the browser or device used, and any engine settings that were active if known.
- Where the issue sits inside a third-party platform or integration, that boundary should be identified clearly rather than misdescribed as first-party code.
- Where a direct fix belongs in this codebase, it should be treated as product work rather than brushed off as a user-preference issue.
Want to inspect the live control layer?
Go to the engine page and see the runtime model in full.
The engine page explains the purpose of the control layer and the wider direction beyond a standard theme switcher.