Ologywood is committed to making our artist booking platform accessible to everyone, including people with disabilities. We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards across all areas of our Platform, including artist and venue profiles, the booking flow, rider contract builder, messaging, and payment checkout.
We target WCAG 2.1 Level AA conformance. Our current conformance status is partially conformant, meaning that some portions of the content may not yet fully conform to the standard. We are actively working to identify and resolve remaining gaps.
The Platform is built with React and uses semantic HTML elements (<header>, <main>, <nav>, <section>, <footer>) throughout. Page headings follow a logical hierarchy. All pages include a consistent navigation structure with a mobile-responsive hamburger menu and bottom navigation bar.
All interactive elements (buttons, links, form fields, modals, dropdown menus) are reachable and operable via keyboard. Focus indicators are visible on interactive elements. The tab order follows the visual reading order of the page. Modal dialogs trap focus and return focus to the triggering element when closed.
The Platform supports both light and dark modes. Text and interactive elements maintain a minimum contrast ratio of 4.5:1 against their backgrounds in both modes. Color is not used as the sole means of conveying information — status indicators (booking confirmed, pending, cancelled) use both color and text labels. Focus indicators use visible outlines that meet contrast requirements.
All form fields have associated labels. Required fields are indicated with both visual markers and aria-required attributes. Error messages are associated with their fields using aria-describedby and are announced to screen readers. The booking form, rider builder, and profile editor all follow these patterns.
Profile photos, venue images, and event images include descriptive alt text. Decorative images use empty alt attributes. The Platform does not auto-play audio or video content.
The Platform is fully responsive and functions on screen sizes from 320px to desktop widths. Content reflows without horizontal scrolling at 200% browser zoom. Touch targets on mobile are at least 44x44 CSS pixels. The progressive web app (PWA) version provides the same accessibility features as the desktop site.
The Platform respects the prefers-reduced-motion media query. When reduced motion is enabled, transitions and animations are minimized or disabled. No content relies on motion to convey meaning.
We are aware of the following areas where accessibility may be limited:
| Area | Limitation | Status |
|---|---|---|
| Google Maps | Embedded maps for venue and event locations rely on Google's accessibility implementation, which may not fully meet WCAG 2.1 AA. Venue addresses are also provided as text. | Third-party dependency |
| Stripe Checkout | Payment forms redirect to Stripe's hosted checkout page, which follows Stripe's own accessibility standards. | Third-party dependency |
| E-Signature Drawing | The draw-to-sign feature in rider contracts requires mouse or touch input. A type-to-sign alternative is available for users who cannot use the drawing canvas. | Alternative provided |
| PDF Contracts | Generated PDF contracts may not be fully screen-reader accessible. The HTML preview of contracts is accessible and contains the same information. | Alternative provided |
The Platform is designed to be compatible with:
We test accessibility using a combination of automated tools and manual review. Automated scans are run during development to catch common issues. Manual testing includes keyboard-only navigation, screen reader testing with VoiceOver, and visual review of color contrast and focus indicators. We welcome reports from users who encounter barriers we may have missed.
If you encounter an accessibility barrier on Ologywood, please let us know. We take all reports seriously and will work to resolve issues promptly.
When reporting an issue, please include the page URL, a description of the problem, the assistive technology you are using (if applicable), and your browser and operating system. We aim to respond to accessibility feedback within 5 business days.