Version dated October 27, 2026.
Translation for convenience. If there is any difference, the Portuguese version prevails.
This statement shows what the WaitScope website and console currently offer in terms of accessibility, what is still missing and how to ask for help if something prevents you from using them.
1. Commitment and standard adopted
WaitScope wants the website and the console to be usable by everyone, including persons with disabilities and people who browse with a screen reader, screen magnification, keyboard or touch.
Article 63 of the Lei Brasileira de Inclusão (Lei nº 13.146/2015, Brazil's Law for the Inclusion of Persons with Disabilities) requires accessibility on the websites of companies headquartered or with commercial representation in Brazil, in accordance with international best practices and guidelines, and a prominently displayed accessibility symbol (§ 1). WaitScope adopts these rules as a goal for the website and the console. What is already met and what is still missing are described in sections 3 to 6.
The reference is the W3C's WCAG 2.2 (Web Content Accessibility Guidelines), at levels A and AA, which is the basis of the Brazilian standard ABNT NBR 17225:2025. The goal is to meet all of these criteria.
2. What this statement covers
- The website waitscope.com, in English, Portuguese and Spanish, including the sample reports.
- The console, at waitscope.io, where you upload traces and read reports.
The Android app is not part of this statement. Neither are third-party pages opened through links, such as the Oracle documentation cited in the reports.
3. Conformance status
The website and the console are partially conformant with WCAG 2.2 at levels A and AA: some of the content does not yet meet all the criteria. The known limitations are listed in section 6.
| Part | Status |
|---|---|
| Website | Partially conformant. Tested as described in section 5, not yet externally audited. |
| Website sample reports | Same status as the console, because they are reports exported from it. |
| Console | Partially conformant. Not yet audited. |
4. What has been done
On the website, except the sample reports
- Semantic HTML, with a single main heading per page and subheadings in order.
- Marked regions (header, navigation, main content and footer) and the “Skip to content” link at the top of the page.
- Language declared on each page, so that the screen reader uses the correct pronunciation.
- Visible keyboard focus.
- A phone and tablet menu that opens and closes with the keyboard. The website runs no JavaScript: the menu works with HTML and CSS only.
- Color contrast at level AA in the light and dark themes, which follow the system setting.
- Alternative text on images that carry content. The logo, which is decorative, is hidden from screen readers.
- Animations turned off when the system asks for reduced motion, and support for forced colors mode, such as Windows high contrast.
- A layout that works from a width of 320 px and with text enlarged to 200%.
- Touch targets of at least 44 px in the menus and bars.
- Accessibility symbol in the footer of every page, linking to this statement.
In the console
- Language declared on each page (Portuguese, English or Spanish) and visible keyboard focus.
- Main navigation labeled for screen readers, and notices and errors marked for assistive technologies.
- In the two-step verification setup, the QR code has alternative text and the key is also shown as text, so that it can be typed into the authenticator app without using the camera.
- The username, password and code fields accept autofill from the browser and the password manager, and the code can be pasted.
- Accessibility symbol in the footer of every page, linking to this statement.
- The analysis processing page updates the progress without reloading, in a region that screen readers announce.
5. How it was assessed
The website went through automated checks at screen widths from 320 to 1536 px, in the Chromium, Firefox and WebKit browser engines (those of Chrome and Edge, of Firefox and of Safari). It also went through usage tests with keyboard and touch.
There has not yet been an external audit of the website or the console. In the console, only the code and the colors were checked, without tests with a keyboard or a screen reader.
6. Known limitations
- Website, report images. They are screenshots of the console. The alternative text describes the image but does not include the numbers in the table. The full report, as text, opens through the “Open the sample report” link in the image caption.
- Website, sample reports. They are reports exported from the console as HTML and have the same limitations as the console.
- Console, contrast. Some text falls below the minimum contrast of 4.5:1 (criterion 1.4.3), such as the text of the primary buttons in the dark theme.
Without an audit, the console may have other barriers, including for keyboard and screen reader use.
7. How to report a barrier
If something on the website or in the console prevents or hinders your use, write to contato@waitscope.com, if possible with the subject line “Acessibilidade” (Portuguese for “accessibility”). It helps to include:
- the page address or the name of the console screen;
- what you tried to do and what happened;
- if you wish, the browser, the operating system and the assistive technology you use, such as a screen reader, magnifier or voice control.
You do not need to say whether you have a disability.
WaitScope replies within 15 days. If you need content from the website or the console in another format, such as plain text, ask through the same channel.
The message is processed as described in the Privacy Policy.
8. Date and next review
This statement was prepared on October 27, 2026 and describes the website and the console as of that date.
Next review: by April 27, 2027, or earlier if the console is audited or changes in a way that affects accessibility.