Legal
Accessibility Statement
Published June 2026 · Olive Wood IT Limited, trading as Bield
Our commitment
Bield is built for people who race ultras and the teams that support them — including people with disabilities. We are actively working to ensure that app.bield.run conforms to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.
What this statement covers
This statement applies to all pages served from app.bield.run, including:
- Race browsing and search (/races)
- Individual race detail pages (/race/…)
- Pace calculator (/pace-calc)
- User account and settings (/me)
- Notification preferences (/me/notifications)
- Privacy and data rights (/me/privacy)
- Pacer, crewer, and coach finder pages
- Club and organisation pages
The marketing website at bield.run is maintained separately and has its own accessibility review cycle.
Technical specification
Bield relies on the following technologies for conformance:
- HTML
- CSS
- JavaScript (React / Next.js)
- WAI-ARIA 1.2
Measures taken
- Keyboard focus indicators (outline 3px solid, box-shadow) on all interactive elements, including in Windows High Contrast Mode (WCAG SC 2.4.7, 2.4.11).
- Skip to main content link at the top of every page (WCAG SC 2.4.1).
- Desktop navigation dropdowns support Escape to dismiss, Arrow keys to navigate items, and Tab-away-to-close (WCAG SC 2.1.1).
- Active navigation item marked with aria-current="page" (WCAG SC 4.1.2).
- Semantic HTML landmarks: <header>, <nav>, <main>, <footer>, <aside>.
- All navigation menus carry aria-label, aria-expanded, aria-haspopup, and role="menu" / role="menuitem" attributes.
- All form controls have associated labels (wrapping label, htmlFor/id, or aria-label) (WCAG SC 1.3.1, 4.1.2).
- ARIA live regions on status messages, error alerts, and save confirmations.
- Decorative images and icons marked aria-hidden="true".
- Colour contrast meets WCAG 2.2 AA (4.5:1 for normal text, 3:1 for large text) — reviewed June 2026.
- Page titles are unique and descriptive.
- Heading hierarchy is sequential (h1 → h2 → h3) on every page.
Known limitations
We are honest about areas where we have not yet achieved full conformance:
Interactive race maps
The Leaflet-based race maps on the Browse Races and Race Detail pages have limited keyboard accessibility. Map pan and zoom are accessible, but clicking race pins requires a pointing device. We are investigating a keyboard-accessible alternative to pin interaction.
Third-party sign-in
Sign-in via Apple or Strava redirects to those providers' own authentication flows. The accessibility of those flows is outside our control; we recommend using email and password sign-in as an alternative.
Community-uploaded race photos
Alt text for race photos is generated automatically and may not fully describe image content. Organisers and tagged runners can request manual alt text correction by contacting support@bield.run.
3D route preview
The 3D route viewer in the Pace Calculator uses WebGL and does not have a keyboard-accessible equivalent. The elevation profile chart and text-based splits table convey the same information in an accessible form.
Input placeholder text contrast
Placeholder text in search and filter inputs uses a muted grey token (#7c87a3, 3.34:1 on cloud background). WCAG 2.2 does not require placeholder text to meet the 4.5:1 threshold, but we plan to introduce a dedicated placeholder colour token with higher contrast in a future design pass.
Feedback and contact
If you encounter any accessibility barrier on Bield, or if you need content in an alternative format, please contact us:
- Email: support@bield.run
- We aim to respond to accessibility enquiries within 5 business days.
If you are not satisfied with our response, you can contact the Equality Advisory and Support Service (EASS).
This statement was prepared in June 2026. It will be reviewed and updated at least annually, and whenever significant new features are released.
Olive Wood IT Limited — company number 14193135, registered in England and Wales.