Skip to content
TeamPickerWheel
Reviewed 16 September 2026

Accessibility Statement

What works with a keyboard and a screen reader, what the measured contrast is, and the parts of the site that are still a problem.

Team Picker Wheel aims to meet WCAG 2.2 Level AA. This statement describes what has actually been built and measured rather than claiming a certification. The site has not been audited by an independent accessibility body.

What Works Today

Keyboard

The whole site can be operated without a mouse. Every control is a real button or input rather than a clickable div, so it is reachable by tab and activated by Enter or Space.

  • A Skip to content link is the first thing the tab key reaches on every page.
  • The space bar spins the wheel from anywhere on a tool page.
  • Focused controls get a visible outline, drawn with :focus-visible so it appears for keyboard users without following a mouse click.
  • The result card is a modal with a close button in the tab order.

Screen readers

  • The result of every spin is announced through a polite live region, so the name is read out without moving focus.
  • The wheel canvas carries a text label describing what it is and how many entries are on it.
  • Each entry in the list below the wheel is a toggle button with a pressed state, so its on or off status is read out rather than shown only by color.
  • The result card is marked as a modal dialog.

Motion

If your operating system is set to reduce motion, the site honors it. Page transitions are flattened, and on a tool page the wheel does not animate at all — a spin lands on the result immediately and the confetti burst is suppressed. The odds are identical either way, because the winner is chosen before anything is drawn.

Color and text

Color is never the only way information is conveyed: entries that are switched off are labeled as well as dimmed, and the result is written out in text rather than only shown on the wheel. Measured contrast ratios against their real backgrounds:

Measured text contrast, WCAG AA requires 4.5:1 for normal text
ElementRatioResult
Body text in guides10.3:1Passes AA and AAA
Section headings17.1:1Passes AA and AAA
Navigation links18.3:1Passes AA and AAA
Primary button label17.9:1Passes AA and AAA
Hint text under the wheel5.5:1Passes AA
Footer small print4.7:1Passes AA, the lowest on the site

Text reflows down to a 320 pixel viewport and can be zoomed to 200 percent without content being cut off or overlapping. There are no time limits anywhere on the site and nothing flashes.

Known Limitations

These are real problems that have not been solved yet. They are listed because a statement that only lists successes is not useful to anybody deciding whether they can use the site.

Known accessibility gaps and what to do instead
LimitationWho it affectsWorkaround
The wheel is drawn on a canvas, so individual segments cannot be reached or read one by oneScreen reader usersThe same entries appear below the wheel as a list of real buttons, and the result is announced in text
Sound effects are on by defaultAnyone who needs silence or finds the ticking distractingA Sound effects switch on every tool page turns them off and the choice is remembered
The wheel needs a reasonably sized screen to show long entry namesSmall screens and high zoomLong names are shortened on the wheel itself, but the full text appears in the result and in the entry list
No independent audit has been carried outEveryoneReport anything you hit and it will be treated as a bug

Reporting an Accessibility Problem

Accessibility problems are treated as bugs, not as feature requests. Email infodigirankrise@gmail.com with Accessibility in the subject line.

Telling us what you were trying to do, which page you were on, and what assistive technology and browser you use makes a fix far more likely to be the right one. If something on this site blocks you completely, say so in the first line so it can be prioritized.

How This Statement Is Maintained

This statement was last reviewed on 16 September 2026. It is rewritten whenever the wheel engine changes in a way that affects any of the claims above, because every tool page on the site is rendered by that one engine — a change to it changes all of them at once.

The contrast figures are measured against the live site rather than taken from a design file. The keyboard and screen reader behavior described above is what the current code does, not what it is intended to do.