Accessibility

Pages use semantic headings, labelled form controls, keyboard-operable native controls, responsive layouts, readable text, visible focus styles and text alternatives for meaningful images where implemented.

Colour is not intended to be the only way that important status or errors are communicated. Forms provide textual validation and should remain usable with browser zoom and common assistive technologies.

Accessibility review applies to signup, login, company setup, inventory, clients, events, quotes, invoices, payments, account settings, cookie choices, data-rights forms and document download controls.

Generated PDFs and imported customer documents can vary according to customer content and templates. Customers should review documents before sending them to people who require an accessible format.

A full independent WCAG conformance audit has not been completed, so Riera Studio does not claim formal WCAG certification or universal compatibility with every assistive technology.

Some complex operational tables, third-party Stripe or Supabase interfaces, customer-uploaded files and older generated documents may require further accessibility improvements or an alternative format.

If a person cannot complete a task because of an accessibility barrier, Riera Studio will consider a reasonable alternative, including guided support, a machine-readable export or another document format where practical and lawful.

Report the affected page, device, browser, assistive technology, expected result and urgency to RieraStudio@srfsystems.uk. Accessibility reports are treated as product issues and prioritised according to impact.

New public and core workflow changes should be checked for keyboard access, focus order, labels, error identification, contrast, zoom, responsive behaviour and screen-reader structure before release.

This statement is updated when a formal audit is completed or a material limitation changes.