Accessibility statement

Goal

We aim for WCAG 2.2 level AA on the pages a designer's client uses: the brief (questionnaire), the client portal, booking a consultation, and their error states. The designer panel follows the same accessibility patterns (forms, dialogs, menus, keyboard-operable drag-and-drop), without a separate conformance target.

How we've checked it

Today we check conformance manually, by keyboard and with a screen reader on the key screens. Automated accessibility checks (axe, JSX lint rules) are in progress and do not yet run on every build, so some pages may have issues we haven't found.

Known limitations

PDF pages render as an image, with no selectable or readable text layer. Each page carries a numbered "Page" label for screen readers, and the "Open file" button opens the original file in another application, which reads its text if the file has any. That's the documented, accessible route to a PDF's content.

Pointing at an exact spot on a photo or a drawing (for example, in a comment on a material) with full precision needs a pointing device, such as a mouse or touch. From the keyboard you can still add a pin (it lands in the middle of the page), and the comment's text says which spot is meant.

Contact

Ran into an accessibility barrier, or have a question? Write to contact@projado.com.