Inclusive design

Accessibility

Last updated: June 2026

Standards we target: WCAG 2.1 AA

WCAG 2.1 AA (Web Content Accessibility Guidelines) is the internationally recognised benchmark for accessible web content. It is organised around four principles:

✓Perceivable — Information and interface components must be presentable to users in ways they can perceive — for example, providing text alternatives for images and captions for video.
✓Operable — Interface components and navigation must be operable by keyboard as well as mouse, and users must have enough time to read and use the content.
✓Understandable — Information and the operation of the interface must be understandable — predictable behavior, clear labels, and helpful error identification.
✓Robust — Content must be interpreted reliably by a wide variety of user agents, including current and future assistive technologies.

Our commitment

We want TrustVexa to be usable by everyone, including people who rely on assistive technologies. We aim to meet the WCAG 2.1 AA guidelines and treat accessibility as an ongoing effort rather than a one-time checkbox.

This means every product update goes through an accessibility review. When new components are added to the interface, they are checked for keyboard operability, screen reader compatibility, and sufficient color contrast before shipping.

What we do

We use semantic markup and labelled form controls, maintain keyboard operability and visible focus, support light and dark themes with sufficient color contrast, and respect your system reduced-motion preference.

Interactive elements carry descriptive ARIA labels and roles. Error messages are associated with their form fields programmatically so assistive technologies can surface them correctly. Page structure uses landmark regions — main, nav, footer — to help screen reader users navigate quickly.

Known limitations

Some complex interactive areas are still being improved. If you hit a barrier, telling us helps us prioritize a fix.

We are aware that certain data-rich tables and animated elements may not yet provide an ideal experience for all assistive technology users. We are actively working to address these areas in upcoming releases.

Feedback

If you experience any difficulty using the Service, please let us know the page and what went wrong so we can address it.

Detailed reports — including which browser, operating system, and assistive technology you are using — help us reproduce and fix issues faster. There is no barrier too small to report; even minor friction matters.

Accessible features

Keyboard navigation

Every interactive element — buttons, links, form fields, modal dialogs — can be reached and operated using only a keyboard. Focus order follows a logical reading sequence. Focus trapping is used inside modals so you don't accidentally leave them.

Screen reader support

Semantic HTML, ARIA landmarks, and descriptive labels give screen readers the context they need. Status updates — such as deal state changes — are announced via live regions so users don't have to navigate back to find them.

Reduced motion

Animations and transitions respect the prefers-reduced-motion media query. When you set your OS to reduce motion, decorative animations are disabled and transitions become instant, avoiding potential vestibular triggers.

Color contrast

Text and interactive elements meet the WCAG AA contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Both light and dark themes are validated. We never use color as the sole means of conveying information.

Testing

We test accessibility through a combination of keyboard-only walkthroughs and automated scanning tools integrated into our CI pipeline. Automated tools catch a meaningful portion of common issues — missing labels, low contrast, incorrect ARIA usage — and give us quick feedback on regressions.

We acknowledge that full accessibility validation requires manual testing with real assistive technologies — screen readers, switch controls, and voice input — and expert review. We are working toward more comprehensive manual testing coverage as the product matures. If you find something automated tools would miss, please let us know.

Reach us through the contact page with any accessibility feedback.

File an accessibility request

If you need a specific accommodation or want to report a barrier that is blocking your use of TrustVexa, email us directly. Include the page URL, a description of what you were trying to do, and the assistive technology you were using. We will respond within 5 business days.

support@trustvexa.com