Accessibility

Everyone who shares costs should be able to use Settled. Here is what we aim for, what we check, and what isn't right yet.

Last reviewed: 23 October 2026.

Our target

Settled aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, in the app, the guides and these pages.

What we do

• Automated checks on every change. The test suite runs the axe accessibility engine over the main screens, and continuous integration blocks a change that fails it.
• Checks in a real browser. Each review runs axe against WCAG 2.2 AA in Chrome, which also measures colour contrast and the size of things you tap. On 23 October 2026 the app, the guides and these pages passed on every screen checked: Home, a group's expenses, balances and members, a receipt, and a quick split.
• Keyboard and focus. Settled is built to be used with a keyboard: focus is always visible, and dialogs keep focus inside them and return it to where you were when they close.
• Reduced motion. If your device asks for less motion, Settled's animations are reduced and the landing page's demo video doesn't play on its own.
• Readable by design. Text colours are chosen to meet a 4.5:1 contrast ratio, layouts work from phone width up, and nothing depends on colour alone (balances say "you're owed" or "you owe", not just green or red).

Known gaps

• Receipt photos that people upload have no text description. The expense's items and prices, shown next to them, carry the same information.
• Screen reader testing. We haven't yet tested every flow end to end with a screen reader. If something doesn't make sense with yours, please tell us.

Tell us about a barrier

If something in Settled is hard or impossible for you to use, email support@settledsplit.com with the page and what happened. We'll reply within 5 business days, and help you get done what you were trying to do in the meantime.