Accessibility and Usability Statement

Our commitment

We want anyone to be able to use Trazza, including people who navigate with a keyboard, a screen reader, or magnification, or from a cell phone.

This statement covers Trazza's website, businesses' public sites, and the private dashboard, and explains what we have done, what is missing, and how to let us know about a problem.

Our goal

Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

It is a working goal, not a certification: we have not done a complete formal audit and we do not have a conformance seal.

What we have already done

We use semantic HTML, with headings in order, labeled regions, and accessible names on buttons that show only an icon.

Keyboard focus is visible and the main features can be used without a mouse. For example, in the schedule you can move an appointment with the keyboard, without dragging it.

The home page has a link to skip directly to the content.

Each page declares its language, so that screen readers pronounce text correctly in Spanish, English, or Portuguese.

We respect your system's reduced-motion preference and announce important changes, such as a save or an error, with status messages.

We fixed colors with insufficient contrast, and businesses can write alternative text for their team photos.

How we check it

An automated test verifies, in Spanish, English, and Portuguese, that the accessible name of icon controls contains their visible text (WCAG success criterion 2.5.3).

In August 2026, the public site of a demo business went from 93 to 100 points in Lighthouse accessibility, in its mobile version, after we fixed contrast and list structure.

Our internal development rules require form labels, accessible names, keyboard operation, and visible focus in every new interface.

Usability

Trazza is available in Spanish, English, and Portuguese, in clear language without unnecessary jargon.

Screens adapt to phones and computers without horizontal page scrolling. Some wide views, such as the schedule, scroll within their own area.

Actions that take time show their status and are disabled while they are being processed, to prevent duplicate submissions.

Many details, such as those of an appointment, open in side panels so that you do not lose the context of the screen you are on.

Known limitations

We have not done a formal WCAG audit of the private dashboard or of the platform's internal panel.

There is only a light theme: there is no dark mode or dedicated high-contrast mode yet.

Some complex tables, such as reports with many columns or the schedule with many professionals, can be hard to navigate with a screen reader or on small screens.

The private dashboard does not yet have a skip-to-content link.

Our automated accessibility tests cover only some criteria; the rest depends on manual reviews.

The accessibility of the content each business publishes on its site, such as images and text, depends on that business.

How to report a problem

If you find an accessibility barrier or something hard to use, write to us through the contact channel listed at the end of this page.

Tell us which page you were on, what you were trying to do and, if you can, which browser or assistive technology you use.

How we respond

We respond to every report and prioritize fixes according to their impact on people.

We cannot promise a fixed timeline for each fix, but we will keep you informed. In the meantime, we will help you complete the task another way if you need it.