1. Conformance status

ShowCloser is partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. "Partially conformant" means that some of the content meets the requirements and some has not been evaluated yet.

We are working towards level AA, but we do not certify full conformance today and we have not commissioned any external evaluation. We put it this way on purpose: a statement promising full conformance would be false, and that is worse than having no statement at all.

2. What we have verified, and on exactly what

2.1 The legal pages — this one, privacy, terms and cookies

Manual audit of 24 July 2026. Every point below was measured, not eyeballed:

• The footer contrast was 3.94:1, below the 4.5:1 minimum for level AA. Fixed.
• The border of the form fields was 1.31:1, when it is the only thing that draws the field against the background and guideline 1.4.11 requires 3:1. Fixed.
• The keyboard focus indicator was painted gold on a light background: 1.56:1. It existed and could not be seen, which for anyone navigating by keyboard is the same as not having one. It is now black with a halo, and it is visible.
• There was no small-screen adaptation at all: at 320 px wide, the header and the cookie table overflowed the viewport. Fixed.

2.2 The rest of the product — the application you use once you sign in

• Colour contrast, measured automatically on every release. An in-house check resolves every interface colour to the actual value the browser ends up painting, in both the light and the dark theme, and blocks the release if any text falls below the level AA minimum (4.5:1 for normal text, 3:1 for large text and for control borders). Latest measurement: 2,149 colour combinations checked across both themes, zero failures.
• Labels for screen readers. 28 interface files carry ARIA attributes: accessible names on buttons and icons, state for controls that toggle on and off, notices that announce themselves when they change, and declared roles for the calendar, the tabs and the drop-down lists.
• Keyboard navigation. The focus indicator is defined explicitly in the global stylesheet and in the interactive components, so that where you are is always visible.
• Motion. If your system asks for reduced motion, the entrance animations do not run.
• Images. The two images in the product — your profile photo and the preview while you crop it — carry alternative text; the preview’s is deliberately empty, as it is decorative.
• Languages. The interface is available in Spanish, English, Portuguese and French.

3. What is NOT verified

This is the part to read, and being honest here matters more than the list above.

• The product has not undergone any complete accessibility audit. What is described in 2.2 is colour contrast measured automatically, plus measures applied by hand during development. That is not the same as an audit.
• We have not tested it with screen readers — NVDA, JAWS, VoiceOver or TalkBack — nor with magnification software, nor with voice control.
• We have not done a complete keyboard-only pass over every screen.
• We have not carried out testing with people with disabilities.
• There is no "skip to content" link at the start of the application screens.
• The declared page language is adjusted once the page finishes loading, not before. The application's lang attribute follows the chosen language (verified on 6 September 2026: with the interface in English, the attribute becomes en), and each legal document declares its own. What the server sends declares Spanish and shows Spanish, so there is no mismatch there; a very brief moment remains, between the text switching to the chosen language and the attribute being updated, in which the two do not match. Fixing it completely requires the server to know the language before responding, and that is pending.
• The automatic contrast check has a known limit: it does not see which background an element ends up on when that background is set by a distant element, nor inherited transparency. It measures against the worst possible surface, which is the conservative criterion, but it does not replace a check on screen.
• The product is in beta and changes often. A new screen may introduce a barrier we have not detected yet.

4. If you run into a barrier

Write to us at hola@showcloser.app and tell us which screen it happens on, what you were trying to do, and which assistive technology you use, if any.

We reply within a maximum of 10 working days. If the fix is simple, we do it sooner; if it needs more time, we tell you how much and why.

And if a barrier is stopping you from doing something you need to do on the platform, tell us anyway: we will look for a way to sort it out with you while we fix the cause.

5. How this statement was prepared

This is a self-assessment, carried out by our own team on 4 September 2026 against the application code. No independent third party was involved. It draws on the contrast audit of 24 July 2026 and on the automatic measurement described in 2.2. It will be reviewed when the product changes significantly or when a more complete evaluation is carried out.

6. Related documents

• Privacy Policy
• Terms and Conditions
• Cookies and local storage