Accessibility statement

Our standard

We build wealthceo.com and the WealthCEO app to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. You should be able to use every page with a keyboard alone, with a screen reader, zoomed in to 400%, and with your own settings for color, contrast and motion.

We don’t use accessibility overlays or plug-ins. Accessibility is part of how each page is built, not a layer added on top.

How we check it

• Every change to our code is checked automatically before it ships: accessibility rules in the code itself, an automated scan of every interface component, and a scan of every page of this site in both the light and the dark theme.
• Our colors are tested for contrast: at least 4.5 to 1 for text, and 3 to 1 for the edges of form fields and the outline that shows where you are on the page.
• We check new pages by hand with a keyboard and a screen reader before they ship.
• The calculators speak a short summary of their results when you pause typing, and every chart has its figures in text as well.

What we know isn’t right yet

• Videos in our Insights posts play in YouTube’s player, which we don’t control. Every video has captions or a transcript before we publish it, but the player itself may not work fully with every screen reader.
• Some documents we share as PDFs may not be fully readable by a screen reader. If you need one in another format, ask us and we’ll send it.
• In the light theme, some text sits on patterned backgrounds that automated tools can’t measure, so we check those by hand. If you find anything hard to read, tell us.
• We haven’t had an independent accessibility audit yet.

Tell us about a problem

If something on this site or in the app doesn’t work for you, we want to know. Use the access request form: write what went wrong, and on which page, in the last box, and tick “I’d like a call” if you’d rather talk it through. You don’t have to be joining the beta to use it, and our team reads every request.

A direct address for accessibility questions will be published here before the site launches.

We review this statement at least once a year, and whenever the site or the app changes in a way that affects it.