Accessibility Statement

Accessibility is built into our development process, not bolted on afterward. Our goals include:

• Keyboard navigation. All interactive elements — sign-in, booking flows, messaging, and settings — are reachable and operable using only a keyboard. We test with Tab, Shift+Tab, Enter, Space, and arrow keys.
• Screen-reader semantics. We use semantic HTML and ARIA landmarks, roles, and labels so screen readers (NVDA, JAWS, VoiceOver, TalkBack) can accurately describe the interface. Forms include visible labels and explicit error messages.
• Color contrast. Text and interactive elements meet or exceed the WCAG 2.1 AA contrast ratio of 4.5:1 for normal text and 3:1 for large text. We test against both light and dark themes.
• Alternative text. All images that convey meaning have descriptive alt text. Decorative images use empty alt attributes (alt="") so screen readers skip them.
• Responsive layout. The interface reflows correctly at 320px width and supports up to 400% browser zoom without horizontal scrolling or loss of functionality.
• Focus indicators. Focus rings are visible at all times and meet the WCAG 2.1 AA non-text contrast requirement of 3:1 against adjacent colors.
• No seizure triggers. We do not use content that flashes more than three times per second.

We are honest about where the platform falls short. The following known issues are on our accessibility backlog:

• Stripe payment iframe. The Stripe embedded payment form is rendered inside a third-party iframe. While Stripe publishes its own accessibility conformance statement, LiveGrid cannot directly remediate issues within that iframe. If you encounter a barrier at checkout, please contact us and we will assist you with an alternative payment path.
• Embedded audio/video player. The artist profile page embeds audio and video previews using an iframe from Spotify/SoundCloud where applicable. Playback controls within those iframes are outside LiveGrid’s direct control. The “Open in [service]” link is always available as a fallback.
• Map component. The venue proximity map (powered by an H3 hexagonal grid) currently lacks a fully accessible text-based alternative for users who cannot use the map. We are building a list-based proximity view as a replacement and expect to ship it in the next release cycle.

We are actively working on all of the above. If you find an issue not listed here, please report it (see Section 4).

LiveGrid’s web application is built with Next.js, React, and Tailwind CSS using the Radix UI primitive library (which ships with built-in ARIA compliance). We test using:

• VoiceOver on macOS and iOS
• NVDA + Firefox on Windows
• TalkBack on Android
• axe-core automated scanning integrated into our CI pipeline
• Manual keyboard-only navigation walkthroughs on each major feature

If you experience an accessibility barrier on LiveGrid, we want to hear about it.

• Email: a11y@livegrid.alldayautomations.ai
• What to include: The URL or feature where you encountered the barrier, the assistive technology you are using (screen reader, switch access, etc.), a description of what you expected to happen and what actually happened, and your operating system and browser.
• Response time: We aim to acknowledge accessibility reports within 2 business days and provide a resolution timeline within 10 business days.

We will not discard or deprioritize accessibility feedback. If we cannot fix an issue immediately, we will tell you our timeline and offer an accessible alternative in the meantime.

If you are not satisfied with our response and you are in the United States, you may contact the U.S. Department of Justice Civil Rights Division or the U.S. Access Board about potential violations of the Americans with Disabilities Act. EU users may contact their national market surveillance authority.

LiveGrid Music Corp, LLC
State of Florida, United States
Accessibility: a11y@livegrid.alldayautomations.ai

See also: Privacy Policy · Help Center