Accessibility

Retire Slider, published by Yellow Sun Systems LLC. Last updated 24 August 2026.

Retire Slider aims to conform to WCAG 2.2 Level AA. This page says where it stands, honestly, including where it does not yet get there. It is written for people who need to know before they rely on the tool, not as a compliance badge.

What is in place

• Keyboard. Every control can be reached and operated from the keyboard, with a visible focus indicator and a skip link to the main content. There are no keyboard traps.
• Screen readers. The app recomputes its answer whenever anything changes, with no button to press — so the figures at the foot of the screen are announced when a refined run settles, rather than changing silently. The announcement waits for the full run and repeats nothing, so dragging a slider does not produce a stream of chatter.
• The projection chart carries a text alternative and a data table conveying the same percentile figures, so nothing is available only as a picture.
• Target sizes. Interactive controls meet the 24 × 24 CSS-pixel minimum, and buttons render a visible target at rest rather than only on hover.
• Zoom and reflow to 400% without loss of content, and a layout that adapts from a phone to a wide desktop.
• Motion. Animation respects prefers-reduced-motion.
• Themes. Dark and light, chosen in Settings, each with its own colour set rather than an inverted copy of the other. The list a dropdown opens is coloured from the same set, so its options are readable in the dark theme rather than taking the platform's white.
• Choices announce what kind they are. Where exactly one option may be picked — starting a scenario, for instance — the list is a radio group and each row reports whether it is the chosen one; where several may be, they are checkboxes. Picking is separate from confirming, so nothing is committed by the act of moving through the list.

Known gaps

• No formal screen-reader study has been completed. Current checks combine automated tooling, keyboard traversal, contrast measurement and accessibility-tree inspection.
• The standalone policy and support pages use a dark presentation rather than following the light/dark preference saved inside the app.
• The downloadable PDF is untagged; the equivalent in-app Results view remains the accessible human-readable version.

The PDF report

The generated report contains selectable text, a document language and a title, but it has no PDF structure tree: headings, tables and reading order are therefore not reliably conveyed to assistive technology. Use the equivalent in-app Results view for an accessible human-readable report; JSON export is also available for structured data.

Telling us about a problem

Email support@yellowsunsystems.com with what you were trying to do, what happened, and the assistive technology and browser you were using. The build stamp at the foot of the About box — for example Build Aug-17-2026 @ 2:26AM — tells us exactly which version you are on and is safe to share; it says nothing about you or your figures.

We aim to reply within five working days. There is no formal enforcement procedure for this app; if you are not satisfied with the response, say so and it will be escalated within Yellow Sun Systems LLC.

See also the Terms of Use, the Privacy Policy and Support.