Accessibility statement

01 Our commitment

We want everyone to be able to find out about and play Choke Point: Tower Defense, including people with disabilities. We treat accessibility as part of how the website and the game are built, not as an add-on, and we fix problems people tell us about.

02 The standard we aim for

We design and test chokepointtd.com against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. The site hasn’t had an independent audit yet, so this statement reflects our own testing. Where we know we fall short, we say so under Known limitations.

03 What we’ve done on this site

• Structure. Each page has one main heading and a logical heading order, marked-up regions (header, navigation, main content, footer), a “Skip to content” link, and its language set to English.
• Keyboard. Everything works from a keyboard, including the menu and the route builder demo. Focus is always visible as a bright cyan outline with a contrast of 13.9:1 against the background.
• Contrast. Text is checked against the background it actually sits on, not just the color palette, and meets WCAG’s 4.5:1 minimum.
• Reduced motion. If your device is set to reduce motion, animations stop and nothing autoplays, and anything an animation shows, like a lamp lighting up, is shown in its final state instead.
• Gameplay video. The gameplay loops are silent and have a visible pause button. They play only while on screen, and never start by themselves when reduced motion or a data-saving mode is on.
• Route builder. The interactive board can be played by keyboard: focus it, move with the arrow keys, build with Enter or Space, and press R to reset. Changes are announced to screen readers, and a button pauses the Machines.
• Without JavaScript. All content and navigation work, including the menu on small screens. Where a feature needs JavaScript, like the route builder, you get a real still from the game with the same explanation.
• Text alternatives. Images that carry information have text descriptions; decorative art is hidden from screen readers.
• Zoom and text size. Type is sized in relative units, so browser zoom and text-size settings scale it, and pages reflow to fit screens as narrow as 320 pixels.
• Capitals. Headings and labels are shown in capitals in the game’s style, but written in normal case, so screen readers read them as words.

We check pages with automated tools (Lighthouse and the axe accessibility engine it uses) and by hand with a keyboard before they go live.

04 Known limitations

• The route builder is visual. You can play it by keyboard and hear what changes, but the board isn’t described tile by tile. The text beside it explains the same rule, and the version without JavaScript shows a still from the game.
• Gameplay loops have no captions or audio description. They have no sound, and what they show is also in the text around them. Any video we publish with speech or meaningful sound will have captions.
• Screenshots contain game text as pictures. Their text descriptions cover what matters, but not every label on screen.
• We haven’t tested every page with every screen reader. If something doesn’t work with yours, please tell us.
• Other sites. Pages we link to, such as scarletaurora.com, Instagram, X and the App Store, are outside this statement.

05 Accessibility in the game

Choke Point has its own accessibility settings, under Settings → Accessibility. In the current build they include:

• Text size. Follow your device’s text size, or choose Large or Extra Large.
• Readability. Higher text contrast and state symbols, which follow your device’s Increase Contrast and Differentiate Without Color settings unless you choose otherwise; a large readout; tower level markers shown as numbers or a base glow; and text labels for combat cues.
• Motion and haptics. Reduce Motion (it follows your device setting by default), Reduce Flashes, Reduced Effects for fewer flashes, pulses and glow, a screen-shake switch, and haptics on, off or gentle.
• Battle captions. Short on-screen captions for battle events, shown for 5 or 10 seconds, plus a list of the run’s last 20 alerts.
• Game pace. Start waves at half speed and start each wave yourself. On every difficulty you can pause and keep building; on Relaxed, Machines can’t damage your towers.
• Sound. Separate volume controls, Voice Focus to lower music during speech, a detailed sound mix, and a spatial audio switch.
• VoiceOver. Menus and the battlefield have VoiceOver labels and actions, and battle events are announced.
• Keyboard and game controllers. On the battlefield, use the arrow keys or W A S D to move, Return to confirm, Esc to cancel, Space to start the wave, P to pause, 1–9 and 0 to pick one of the ten towers, and [ ] to cycle them. With a controller, move with the D-pad or left stick; A confirms, B cancels, X starts the wave, the shoulder buttons change tower, and Menu pauses.

The game hasn’t been released yet, so these settings may change before release. If a setting you need is missing, we’d like to hear about it.

06 Feedback and help

If anything on this site or in the game is hard to use, or you need information from the site in another format, email support@scarletaurora.com. Tell us the page or screen, what you were trying to do, and the device and assistive technology you use, if you’re comfortable sharing it. We aim to reply within five business days.

07 About this statement

This statement was last reviewed on September 23, 2026. We update it when the site or the game changes in a way that affects accessibility.