sourced
Accessibility · v1.0

Accessibility statement.

How we build for keyboard users, screen-reader users, reduced-motion users, and everyone else who interacts with Sourced.

Last updated

We design Sourced to be operable for the widest realistic range of users. The marketing pages, the product, and the polhia-hosted publish surface are all built against WCAG 2.1 AA as the baseline.

What we do.

Every interactive element is reachable by keyboard with a visible focus indicator. Icon-only buttons carry explicit aria-labels. Form inputs have labels in the DOM, never just a placeholder. Modals trap focus correctly and restore it on close. Animations respect prefers-reduced-motion; the editorial signature motions (the score flipboard, the marigold underline draw-in) land on their final state immediately when the system asks for reduced motion.

Body type is 16px or larger; line lengths sit at the 60-75 character measure recommended by readability research; the marigold accent is never load-bearing for meaning (it always accompanies a non-colour cue).

What we don't yet do.

We don't have a full third-party WCAG audit on file. We test with axe-core and the keyboard in every release; a formal external audit is scheduled before the end of the year. The in-app dashboard is also being broken out of its three-column editorial grid into a more linear small-screen flow — the marketing pages got there first.

If something doesn't work.

Please email hello@polhia.com and we will fix it or, if we can't, tell you why honestly.