Accessibility

What we aim for

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practice that means we work to keep:

• Every interactive control reachable and operable by keyboard alone.
• A visible focus indicator, so keyboard users can always see where they are.
• Text contrast that stays readable, including in bright outdoor light on a phone at the course.
• Labels and descriptions on form fields, buttons and icons that assistive technology can announce.
• Meaningful alternative text on images that carry information.
• Layouts that reflow when text is enlarged or the window is narrow.
• Status messages — a saved score, a failed payment — announced rather than only shown.

Where we fall short

We would rather name the gaps than imply there are none. Known areas we are still improving:

• No independent audit yet. Our accessibility work is self-assessed. We have not commissioned a third-party WCAG evaluation, so we cannot claim conformance — only that we are working toward it.
• Dense tables. Leaderboards and the tournament catalog carry a lot of columns. They are navigable, but they are harder work with a screen reader than the rest of the app.
• Some drag interactions. A few scoring and pairing surfaces offer drag as the quick path. Where they do, there is a keyboard- and tap-accessible alternative — if you find one without, that is a bug and we want to hear about it.
• Third-party pages. Registration links in the tournament catalog lead to organizers' own websites, and payment steps are handled by Stripe. We do not control the accessibility of those pages.
• Scanned scorecards. Reading a photographed paper scorecard is inherently visual. Every scanned round can also be entered and edited hole by hole as text, which is the accessible path.

Telling us about a barrier

If any part of GolfSync is difficult or impossible for you to use, please tell us — it is the fastest way for it to get fixed, and we treat these reports as bugs rather than suggestions.

Email support@golfsync.io or use the support form. If you can, include the page you were on, what you were trying to do, and the assistive technology and browser you were using — that usually lets us reproduce it the same day.

We aim to respond within five business days. If a fix will take longer, we will tell you what we are doing and offer another way to get the same thing done in the meantime.

Assistive technology

We test primarily with VoiceOver on iOS and macOS, and with keyboard-only navigation in current versions of Chrome, Safari and Firefox. We do not claim coverage of every screen reader and browser combination. If you use something we have not tested and it does not work, that is useful information rather than an unsupported configuration — please report it.

Formal complaints

If you have raised an issue with us and are not satisfied with the response, reply to your existing thread with support@golfsync.io and ask for it to be escalated. We will review it directly and write back with what we intend to do and by when.