Accessibility Statement
Effective Date: February 1, 2026 | Last Updated: September 1, 2026
Full Circle Access exists to make live events accessible, so our own site and app have to be. This page says where we are.
Our standard
We build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and we test with assistive technology throughout development, not only before release.
What we do today
Every screen is tested with a screen reader and with keyboard-only use. Every interactive element has a name, a visible focus state, and a touch target of at least 44 by 44 points. Text meets a 4.5:1 contrast ratio, and nothing is communicated by color alone. Images have alt text. The site works from 320px screens up, with text resizing to 200%. We do not use accessibility overlays or widgets. We use inclusive language across the product, and features are named for what they are, never for who they are for.
How we work
Paid focus groups with disabled guests shape what FCA asks for and what it never collects. Disability inclusion trainers are on our team. Our meetings run with live captions and shared agendas, and we ask external participants what would make a meeting work for them.
Where we are not yet
We are in beta. Some third-party pieces, like payment screens and embedded forms, are built by other companies, and we are working with them on their accessibility. We plan an independent WCAG audit before public launch and will publish the results.
Report a barrier
If something does not work for you, tell us at accessibility@fullcircleaccess.co, or use the contact form, which lets you choose email, text, phone, or video. It helps to include the screenshots, or page links, the assistive technology you were using, and what happened. We reply within 5 business days and fix reported barriers by impact.
Full Circle Access exists to make live events accessible, so our own site and app have to be. This page says where we are.
Our standard
We build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, and we test with assistive technology throughout development, not only before release.
What we do today
Every screen is tested with a screen reader and with keyboard-only use. Every interactive element has a name, a visible focus state, and a touch target of at least 44 by 44 points. Text meets a 4.5:1 contrast ratio, and nothing is communicated by color alone. Images have alt text. The site works from 320px screens up, with text resizing to 200%. We do not use accessibility overlays or widgets. We use inclusive language across the product, and features are named for what they are, never for who they are for.
How we work
Paid focus groups with disabled guests shape what FCA asks for and what it never collects. Disability inclusion trainers are on our team. Our meetings run with live captions and shared agendas, and we ask external participants what would make a meeting work for them.
Where we are not yet
We are in beta. Some third-party pieces, like payment screens and embedded forms, are built by other companies, and we are working with them on their accessibility. We plan an independent WCAG audit before public launch and will publish the results.
Report a barrier
If something does not work for you, tell us at accessibility@fullcircleaccess.co, or use the contact form, which lets you choose email, text, phone, or video. It helps to include the screenshots, or page links, the assistive technology you were using, and what happened. We reply within 5 business days and fix reported barriers by impact.
Our Commitment
Full Circle Access is committed to providing a website and platform that works for all users. Accessibility is built into our product from the start — it is a core feature of our culture and how we design, build, and test everything we create.
We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. We test with assistive technology users throughout development and apply universal design principles so the platform serves the full range of guests.
What We Built
Our website (fullcircleaccess.co) is built to the following standards. Our mobile app and venue dashboard will meet these same standards at launch.
Screen reader compatible: Tested with VoiceOver (macOS/iOS), NVDA (Windows), and JAWS (Windows). All interactive elements are properly labeled and navigable.
Keyboard navigable: Every feature on our platform is accessible without a mouse. Tab order follows a logical reading sequence. All interactive elements are reachable and operable via keyboard.
Color and contrast: All text meets a minimum 4.5:1 contrast ratio against its background. Large text (18px+ or 14px+ bold) meets a minimum 3:1 ratio. We do not rely on color alone to convey information.
Images and media: All images include descriptive alt text. All video content includes captions and audio descriptions. Decorative images are marked appropriately and hidden from assistive technology.
Responsive design: Our platform is fully functional from 320px mobile screens through desktop displays, with no loss of content or functionality at any viewport size.
No overlays: We do not use accessibility overlay tools or widgets.
Language and Communication
We follow inclusive language guidelines throughout our platform, communications, and documentation. We use person-first and identity-first language as preferred by the communities we serve. We do not use ableist metaphors or terminology in our product, marketing, or internal communications.
Ongoing Testing
We conduct regular accessibility testing with assistive technology users, including screen reader users, keyboard-only users, and users with cognitive and motor disabilities. Testing happens throughout development — not only before launch. We incorporate accessibility feedback into every sprint cycle.
Team Practices
Our team uses Google Meet with live captions, transcripts, and visual descriptions for all meetings. We share agendas in advance. We provide materials in accessible formats. When scheduling meetings with external participants, we ask what accommodations would make the meeting work best for them.
Known Limitations
We are a pre-launch platform and accessibility improvements are ongoing. If you encounter a barrier, please email us at accessibility@fullcircleaccess.co. We track all reported issues and prioritize fixes based on impact.
Third-Party Evaluation
We are committed to independent accessibility evaluation and will publish audit results as they become available. Our goal is to complete a third-party WCAG 2.1 AAA audit before our public launch.
Report a Barrier
If you encounter an accessibility barrier on our platform, please contact us: accessibility@fullcircleaccess.co
Our contact form lets you choose your preferred communication method — email, text, phone call, or video call — so we can respond in the way that works best for you.
We respond to accessibility feedback within 3 business days and work to resolve reported barriers as quickly as possible.
When you report an issue, please include the page, screenshot, or feature where you encountered the barrier, the assistive technology you were using (if applicable), and a description of what happened.
Contact
Accessibility questions and feedback: accessibility@fullcircleaccess.co