Our commitment
We want Priveloq Chat to be usable by everybody who needs it, including people who use a keyboard rather than a mouse, a screen reader, magnification, or reduced-motion settings.
We do not claim a conformance certification. We design against the Web Content Accessibility Guidelines and test as we build, but this product has not been through a formal independent accessibility audit, and we are not going to print a conformance badge we cannot stand behind. If that assessment matters for your procurement, tell us and we will be straight with you about where we are.
What is built in
- Semantic headings and landmarks, so a screen reader can navigate a page by structure.
- A skip link to the main content at the top of every public page.
- Keyboard access to interactive controls, with visible focus styling.
- Text alternatives for meaningful images, and empty alternatives for decorative ones.
- Form fields with associated labels, and validation messages tied to the field they describe.
- Colour choices checked for contrast, in both light and dark appearance.
- Respect for the operating system's reduced-motion preference: animation is suppressed when you have asked for less of it.
- Layouts that reflow down to small screens without a horizontal scrollbar, and that tolerate text being enlarged.
Where we know there is work to do
Being honest is more useful than a clean-looking statement. Areas we know need more attention:
- Dense data views in the administration and security areas, where tables with many columns are harder to navigate non-visually than the rest of the product.
- Real-time announcements: we do not yet announce every incoming message and presence change to assistive technology in a way we are confident is both useful and not overwhelming.
- The call surface, where controls appear and disappear with call state.
Tell us what is not working
If any part of Priveloq Chat is difficult or impossible for you to use, we want to know. A specific report — the page, what you were trying to do, the assistive technology and browser you use — helps us fix it fastest, but do not let the lack of detail stop you writing.
Report an accessibility problem
Or email hello@priveloq.com. We aim to acknowledge accessibility reports promptly and to tell you what we are able to do and when.
If you use the product through an organisation
Your organisation's administrators configure parts of the experience. If an accessibility problem comes from how your workspace is set up, telling them as well as us will usually get it resolved faster.