Accessibility statement

VertexSpot LLC aims for the website at dinkpartner.com, the DinkPartner app for iPhone and Android, and the tools our staff use to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is the standard the Americans with Disabilities Act is measured against in practice, and the one app stores and public bodies point to.

We treat an accessibility barrier as a bug: it is fixed in the normal course of work, not saved for a redesign.

• Structure — every page has one main heading, headings in order, a skip-to-content link, labelled navigation, and a title of its own.
• Keyboard — everything can be reached and used with a keyboard alone, in a sensible order, with a clearly visible focus ring; wide tables scroll with the arrow keys.
• Colour and contrast — text meets at least 4.5:1 against its background (3:1 for large text and for controls). Our ball-yellow is only ever used behind dark ink text. Links in sentences are underlined, and a rating, a win or a status is never told by colour alone.
• Pictures — the app screen drawn on the home page is described in words; purely decorative graphics are hidden from screen readers.
• Zoom and reflow — pages reflow to a 320-pixel-wide screen and to 400% zoom without scrolling sideways, and respect your text-size and reduced-motion settings.
• Touch — buttons and links on the site and in the app are at least 44 pixels tall.
• Automated checks — every page of this site is tested with the axe-core accessibility engine on every build, and a build with a failure does not ship.

• The App Store and Google Play badges are our own drawings until the public listings open. They are labelled, but are not yet links.
• Community, tournament and court pages (the links that start /c/, /t/ and /r/) are filled in from our servers after the page loads. They announce that they are loading, but a court board refreshing itself every 20 seconds is not announced, on purpose, so a screen reader is not interrupted. A “Pause live updates” button on the board, and on every live board in the app, stops the refreshing until you resume it.
• In the app, buttons are at least 44 points: Apple’s measure, and above the 24 that WCAG 2.2 asks for, but below the 48 that Android’s own guidance recommends. Whether to raise them to 48 on Android is a design decision we have not made yet.
• In the app, a tournament’s bracket and schedule grid are drawn at a fixed size so their lines meet. At the very largest text sizes a caption on them can be cut short. Each match is still read in full by a screen reader, and the same matches are listed as text on Match day.
• The app has been checked screen by screen in automated tests (labels, contrast, touch targets, text at 200%), but not yet end to end on a phone with VoiceOver or TalkBack, with Switch Control or Voice Control, or at the largest iOS text sizes. We will do that before the app leaves beta.
• The app has no dark mode yet, and does not yet respond to the Increase Contrast and Bold Text settings.
• Text that organizers and players write — a community description, a tournament’s refund terms — is shown as they wrote it, and we cannot guarantee its plain language.
• Automated tools catch only part of what matters, and we have not yet had an independent audit with disabled testers. We intend to before the app leaves beta.

If something here stops you doing what you came to do, tell us and we will help you do it another way while we fix it.

Email [email protected] with “Accessibility” in the subject. It helps to say:

• the page or app screen, and what you were trying to do;
• what got in the way;
• the device, browser or app version, and any assistive technology you use (for example VoiceOver, TalkBack, NVDA, JAWS, Switch Control or zoom).

You do not need an account to write to us, and you will hear back from a person. If email does not work for you, say so in any message and we will use a way that does. Our postal address is 920 US Hwy 64 W, Apex, NC 27523.

A person replies within two business days to say we have it and what we will do. A barrier that stops you using a core part of DinkPartner — signing in, logging or confirming a score, joining a game, entering or paying for a tournament, changing your settings — is critical: we fix it, or give you a working alternative, within five business days, and tell you when it is done. Other serious barriers are fixed within 30 days, and smaller ones within 90.

For anything else about the service, see Support.

The site is plain HTML and CSS with a little JavaScript, and works in current versions of Safari, Chrome, Firefox and Edge, with the assistive technology built into them and into iOS, Android, macOS and Windows. It was last reviewed against WCAG 2.2 AA on 2026-11-01, by the people who build it: a page-by-page review of the code against each success criterion, and the axe-core engine run over every page.