Accessibility

Friendsly is built to be usable by everyone, including people who browse with a screen reader, navigate by keyboard, rely on magnification, or prefer reduced motion. We aim to meet WCAG 2.2 Level AA, the standard referenced by the Americans with Disabilities Act (ADA) and Section 508.

• Dialogs and payment flows move focus into the dialog, keep keyboard focus inside it, and return focus to where you left off.
• Queue position and turn changes are announced to screen readers, so a fan who has paid is told when their turn arrives.
• Form errors are announced and tied to the field they belong to.
• Text and interface colours are checked against WCAG AA contrast minimums.
• Every page reflows without horizontal scrolling at 200% and 400% zoom.
• A skip link lets keyboard users jump past navigation.
• Animation is reduced or stopped when your system requests reduced motion.
• Pages are tested in a real browser with automated accessibility tooling (axe-core).

We would rather tell you what does not work yet than claim more than we can support.

• Live calls do not currently have captions. Deaf and hard-of-hearing users cannot follow the audio of a live video call today. This is our highest-priority accessibility gap and we are actively working on it.
• Automated testing does not catch everything. We have not yet completed a full manual review with every screen reader (NVDA, JAWS, VoiceOver), so some rough edges may remain.

Some parts of Friendsly are governed by real time and cannot be paused or extended, because doing so would affect the other person in the call:

• The join window for a scheduled booking opens 5 minutes before the start time.
• A booking is automatically cancelled if neither party joins within 10 minutes.
• Turns in a live queue advance in real time, so that the fans waiting behind you are not held up.

Under WCAG 2.2, these fall within the real-time exception to success criterion 2.2.1 (Timing Adjustable): the time limit is set by a live event involving another person, and no alternative to that timing is possible. Where these countdowns appear, they are announced to assistive technology rather than shown only visually.

Card entry fields are provided by our payment processor, Braintree, and render inside their own secure frames. Their accessibility is controlled by Braintree rather than by Friendsly. If you hit a barrier while paying, please contact us and we will help you complete the booking another way.

If any part of Friendsly is difficult or impossible for you to use, we want to hear about it — that is the fastest way for us to fix it. Please email support@friendsly.app. Tell us the page you were on, what you were trying to do, and the assistive technology you use, if any. We aim to respond within 5 business days.

This statement reflects the state of Friendsly as of the date below. It is based on our own testing and has not been independently audited by a third party. We update it as we fix the gaps listed above.

Last reviewed: 13 July 2026