The standard we build to
This website targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium.
That standard is the reference point for the frameworks that apply to a company like ours across the markets we operate in — the Americans with Disabilities Act and Section 508 of the Rehabilitation Act in the United States, EN 301 549 and the European Accessibility Act in the European Union, the Accessibility for Ontarians with Disabilities Act in Canada, and comparable law elsewhere. Rather than track each separately, we build to the standard they converge on.
Conformance status
This site is, to the best of our assessment, fully conformant with WCAG 2.2 Level AA: it meets the success criteria at that level. We state that with one qualification.
The assessment is our own. It is based on self-evaluation during development — automated checks in the build, manual keyboard testing, screen reader testing, and programmatic verification of the colour palette. It has not been audited by an independent third party. A self-assessment is not an audit, and we will not describe it as one. If a formal evaluation is commissioned, its result will be published here whatever it says.
What we have actually done
Accessibility here is an engineering requirement with tests behind it, not a paragraph in a policy. Specifically:
- Semantic HTML with correct landmarks and a heading order that does not skip levels, so the page structure is navigable rather than merely visible.
- Full keyboard operability, with a visible focus indicator on every interactive element and a skip-to-content link as the first stop in the tab order.
- Colour contrast that meets or exceeds the AA thresholds. This one is enforced rather than asserted: the build reads the real colour tokens out of the stylesheet and computes their contrast ratios, and it fails if a palette change would break a threshold. The sentence you are reading cannot become untrue without the build going red.
- Text that reflows and scales to 200% and beyond without loss of content or function, and layouts that do not require horizontal scrolling.
- Reduced motion honoured through the prefers-reduced-motion media query, for visitors whose systems ask for it.
- Meaningful alternative text on images that carry information, and correct hiding of decoration that does not.
- Language declared programmatically on every page, so screen readers pronounce content correctly — and correctly per language as the site expands beyond English.
- No content that flashes, no auto-playing media, no time limits, and no interruptions the visitor did not ask for.
Technical requirements
This site relies on HTML, CSS and JavaScript. Its content is server-rendered and readable without JavaScript. It is built to work with current versions of major browsers and with assistive technologies used alongside them. Where an older browser or assistive technology does not support a feature, the content degrades to something still readable rather than breaking.
Known limitations
We know of no accessibility barriers on this site at the date of this statement. That claim has two limits: our testing is not exhaustive, and no self-assessment catches everything a real user encounters.
One category is outside our control: content on third-party sites we link to. We do not govern their accessibility, and following a link may take you somewhere less accessible than here.
When a barrier is found — by us or by you — it is recorded here until it is fixed, rather than quietly resolved. A limitations section that is permanently empty is usually a sign that nobody is looking.
Products
Each Primanza product is responsible for accessibility within its own application, and this statement does not cover any product: an application with accounts, forms and data tables raises questions this informational site never faces, and they cannot be answered by proxy from here.
To report an accessibility barrier in a product, write to that product's own support — support@replytune.com for ReplyTune. If that does not resolve it, write to hello@primanza.com.
Feedback and how we respond
If any part of this site is difficult or impossible for you to use, tell us at hello@primanza.com. Include the page and what happened; your assistive technology and browser help but are not required, and you do not need to diagnose the problem for us.
We aim to acknowledge within two business days and to give you a substantive response, with either a fix or a date, within ten business days. Accessibility reports are logged and prioritised as defects.
If our response does not satisfy you, say so and it will be escalated to the company's member directly, at the same address. Beyond that, you retain any right you have to complain to the enforcement body in your jurisdiction, and nothing in this statement asks you to exhaust our process first.
About this statement
This statement applies to primanza.com. It was prepared on 15 July 2026 on the basis of a self-evaluation carried out by Primanza, revised on 4 October 2026, and is reviewed when the site changes materially and at least annually.