Accessibility Statement

What's been built deliberately

These are real, verifiable choices already in the product — not aspirations.

• Keyboard focus is always visible. Every interactive element — buttons, links, form fields — gets the same clear outline when you tab to it: a solid 2-pixel ring with room around it, only when navigating by keyboard, not a browser default that varies by element and is easy to lose track of.
• Motion respects your system setting. If you’ve turned on “reduce motion,” sliding and scaling animations are removed throughout the app. Color changes — like a hover or focus state — still happen, since those aren’t the kind of motion that setting exists to avoid.
• The client/job/rate-rule picker used throughout the app is a real combobox, not a styled dropdown a screen reader can't parse. It's fully operable by keyboard — arrow keys move through results, Home and End jump to the ends, Enter picks, Escape backs out — and announces the highlighted option the way a native listbox does.
• Dialogs trap keyboard focus while open — recording a payment, editing a daily log — so Tab can't silently leave you behind the dialog. They close on Escape, return focus to whatever you opened them from, and stop the page underneath from scrolling while they're up.
• The main navigation marks the current page for assistive technology, not just with a visual highlight, and every nav label stays readable to a screen reader even at narrow widths where it's visually hidden to save space.
• Status is never color-only. “Paid,” “Overdue,” “Draft,” and every other status pill carries its own text label alongside the color. Nothing in the product asks you to tell states apart by hue alone.

What hasn't been verified yet

Being straight about this is the point of this page.

• No formal WCAG audit has been done.
• No testing with a real screen reader — VoiceOver, NVDA, or JAWS — has been done.
• Color contrast hasn't been systematically checked across every color combination the app uses.
• The mobile app hasn't been assessed for accessibility at all.

A structured accessibility audit is underway. When it's finished, this section gets replaced with what it actually found — including what needs fixing, not just what passed.

Reporting a problem

If something in Free-Lance doesn't work for you with a keyboard, a screen reader, or any other assistive technology, we want to know — specifically what you were trying to do, what happened instead, and what you were using. Email support@free-lance.app. We'll respond. If you need this page, or anything else in the product, in a different format, ask — we'll work it out with you directly.