We want OutlastRetirement to work for everyone who plans for retirement, including people who use a screen reader, navigate with a keyboard, magnify the screen, or have low vision. If anything in the app gets in your way, please tell us. We treat it as a bug.
The Standard We Work To
Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium. It is the standard most accessibility laws and courts in the United States point to.
What We Have Done
- Automated testing of every screen. We check each page of the app, in both the dark and light themes, with axe-core, a widely used accessibility testing engine, against WCAG 2.0, 2.1 and 2.2 Level A and AA rules. As of the date above it reports no failures. Since October 21, 2026 every release is also scanned in a real browser before it goes live, covering this site’s public pages and the app’s main screens, and a serious or critical failure stops the release.
- Names for screen readers. Every slider, dropdown, checkbox, text box and icon-only button carries a name a screen reader announces, such as “Annual lifestyle spending” or “Delete scenario.” A check in our test suite stops a new control from shipping without one.
- Readable contrast. Text is tested to meet the 4.5:1 contrast ratio WCAG requires, in both themes, and a test checks the colors we use for it.
- Large Text. Preferences → Display has a Large Text setting that enlarges type across the app, alongside a choice of dark or light theme.
- A hands-on screen-reader check. We walked through the main tasks with VoiceOver in Safari on a Mac: moving between tabs, reading headings, adjusting the spending slider, filling in plan fields, using Find a setting, confirming and canceling a dialog, reading the heatmaps and Year-by-Year tables, and scrolling the per-heir table. Each one worked, and the one thing it turned up (sliders read as a bare number) is fixed: they now say “$48,000 per year” or “3.5 percent.”
- A written summary for every chart. Each chart has a one- or two-sentence summary of what it shows, such as where savings start, peak and end, which a screen reader reads as the chart’s name. Most are also shown under the chart. The figures behind the portfolio chart are in the Year-by-Year tables as well.
- Chart details on touch screens. On a phone or tablet, tapping a chart opens its details, and they stay open until you tap somewhere else.
- Status in words, not color alone. The plan’s status is always given as words, such as “On track,” including in the phone’s top bar.
- Keyboard use. Controls are standard buttons and form fields you can reach with Tab. Heatmap cells respond to Enter and Space, tables that scroll sideways can be focused and scrolled with the arrow keys, and Ctrl+K (Cmd+K on a Mac) opens “Find a setting” so you can jump straight to any field.
What Still Falls Short
Automated tools find only part of what matters, so we want to be plain about what we know and what we have not yet confirmed:
- Other screen readers. Our hands-on review so far has been with VoiceOver in Safari on a Mac. We have not yet tested with NVDA or JAWS on Windows, or with VoiceOver on an iPhone, so something may read less smoothly there.
- Printed and saved reports. A report saved as a PDF from your browser’s print dialog is not a tagged PDF, so a screen reader may read it poorly. The same information is available in the app itself.
We will update this page as each of these is addressed.
Tell Us About a Barrier
If something is hard or impossible to use, email us at hello@outlastretirement.com with “Accessibility” in the subject. It helps to include:
- the page or tab you were on, and what you were trying to do;
- what happened instead;
- the browser, device and any assistive technology you use (for example, VoiceOver on an iPhone, or NVDA with Firefox).
We read every message and reply as soon as we can. If a barrier stops you from getting information you need from the app, we will work with you to provide it another way while we fix it.
Compatibility
OutlastRetirement runs in current versions of Chrome, Edge, Firefox and Safari on desktop and mobile. It relies on standard web technologies (HTML, CSS, JavaScript and the WAI-ARIA attributes that tell assistive technology what each control is) and needs no plug-ins.
How We Assessed This
This statement is based on our own evaluation: automated testing with axe-core across every page and both themes, plus review of the source code. It has not been audited by an outside accessibility firm.