Callvero aims for WCAG 2.2 AA accessibility. This is a design target, not a certification or a claim that every assistive-technology combination has been audited.
How we design
The public site uses semantic headings, labeled forms, visible keyboard focus, readable contrast and responsive layouts. Product tabs support keyboard navigation. Form errors are announced, and motion is reduced when your device requests it. We do not use an accessibility overlay.
What we test
We check key pages at desktop and mobile sizes, keyboard interactions and automated accessibility rules. Automated checks do not replace testing with people who use assistive technologies.
Report a barrier
If something is difficult to use, tell us through the contact page. Include the page, the action you were trying to take, and your browser or assistive technology if you’re comfortable sharing it. We’ll review the issue and discuss another way to help.