Help, trust, and releases · player, parent, coach, organization, partner, help · both
Accessibility in 6Tool
Use device accessibility features and report a barrier with useful details.
- Last reviewed:
- 2026-08-30
- Applies to:
- 2.2
Video guide
Placeholder video: this will be replaced with a tutorial for this guide.
The preview image comes from YouTube's image server. Loading the player connects to YouTube. Watch on YouTube
Accessibility in 6Tool
6Tool can be used with standard browser and device accessibility features. Available behavior varies by surface, device, browser, and content. This guide does not claim that every workflow or item meets every accessibility standard.
Adjust the experience
- Use the operating system's text-size, contrast, motion, or display settings before opening 6Tool.
- On the web, use browser zoom rather than modifying the page's source or URL.
- Navigate interactive web controls with Tab and Shift+Tab, and activate the focused control with Enter or Space when supported.
- Turn on the device screen reader before opening the affected screen so its reading order can initialize normally.
- For media, use captions or transcripts when the content provides them and verify device media volume separately.
Expected result: the page remains usable at the selected device settings, focus reaches the needed control, and labeled content is announced by the assistive technology.
If a task is blocked
- Record the page or screen name and the task you were trying to complete.
- Note the assistive technology, version, device, operating system, browser, zoom or text-size setting, and input method.
- Try the same action once in the latest available app or a current supported browser.
- If safe and practical, try the equivalent 6Tool web or mobile surface. Do not change accounts or repeat a scored submission merely to test.
- Ask the assigning coach, organization, or event contact for a reasonable alternative while support investigates.
Report an accessibility barrier
Contact support and describe:
- the control, image, media, or text that was inaccessible;
- what you expected and what happened;
- the exact error or screen-reader announcement;
- whether keyboard focus was visible and where it moved;
- whether the issue prevented completion or only made it difficult.
Include a screenshot or short recording only after removing names, email addresses, private results, and child information. Never include passwords, one-time codes, or provider tokens. Support can help route the report but cannot promise a release date until the issue has been reviewed.