Accessibility · Fragata Clube
How you navigate this house
The whole portal works without a mouse. This page explains how, shows what the house guarantees — with the measurement beside it — and says out loud what it does not guarantee yet.
The keys
- Tab
- Moves to the next link, button or field. Shift + Tab goes back.
- Enter
- Activates whatever is focused — opens the link, presses the button.
- Space
- Presses buttons and checks options. Outside a control, it scrolls the page.
- Esc
- Closes any open layer: the menu, the search, the showcase, the booking sheet, the style simulation, sign-in and the Maestro drawer. Focus returns to where it was.
- ← →
- In the showcase, it decides the card (left passes, right keeps). In the style simulation, it moves the divider between the real photo and the style.
- Tab (the first one on each page)
- Reveals “Skip to content”, which jumps the whole top bar. It exists on every page of the portal.
If you got here with the keyboard, you have already used the first one: the “Skip to content” that appears on the first Tab of any page.
What the house guarantees
Every item below was measured by an instrument that lives in the portal's repository and runs on every change. The measurement is from 24 de agosto de 2026.
Everything is reachable by keyboard
No control in the portal depends on a mouse. Every link, button and field is in the Tab order, and whatever is focused always shows a visible ring.
Measurement11 screens measured by actually pressing Tab: zero controls out of reach, zero invisible focus rings.prova:teclado
Contrast is measured at the pixel
The text contrast ratio is checked on the painted screen — not in the stylesheet. So the number holds even where there is a gradient, a veil or a photograph underneath.
Measurement140 text blocks across 10 screens × 2 themes. All pass the WCAG 2.1 ratio, with two declared exceptions (below).prova:contraste
44-pixel touch target
Every control has at least 44 × 44 pixels of finger area — on the phone and on the monitor too, because a small target is small for anyone with a tremor, anyone on a touchpad and anyone browsing on a TV.
MeasurementMeasured across 13 screens on the phone (360 and 390 px) and on the home page on a monitor: no control below 44.prova:mobile
No text below 13 pixels on the phone
The portal's small print (notes, table footers, notices) goes up to 13 px on narrow screens. No magnifier to read a remark.
Measurement13 screens × 2 themes, at 360 and 390 px wide.prova:mobile
Two themes, and your choice wins
The portal has a light and a dark theme. The choice made with the button at the top is remembered and overrides the house clock.
MeasurementBoth themes are measured by every check — none of them tests only one.prova:cor · prova:lei
Reduced motion is respected
If your system asks for less motion, the portal stops animating — carousels, transitions and shimmers.
MeasurementWith “prefers-reduced-motion: reduce” on, zero animations keep running on the home page.measured on Aug 24
The content does not depend on JavaScript
The pages are ready-made files. Without scripts, the text stays whole and navigation keeps working — what is lost are the layers (instant search, the showcase), never the content.
MeasurementWith JavaScript off, a development entry still serves 75 links and the full text.measured on Aug 24
The page withstands zoom
Zooming to 200% neither cuts content nor creates sideways scrolling: the text reflows into whatever width is left.
MeasurementA development entry in a 640 px window (the equivalent of 200% at 1280): no sideways scrolling.prova:mobile
Nothing sits behind a sign-up
No content on the portal requires a login — not today, not ever. Signing in adds (your favorites move between devices); it never unlocks what is already public.
MeasurementIt is house law, laid down on August 22, 2026.Council decision
What we do not guarantee yet
This section exists because an accessibility statement without limits is not a statement: it is an advertisement. Here is what we know is missing.
We have not run a screen-reader audit
Our checks measure structure — labels, order, focus, contrast. They do not replace someone browsing with NVDA, JAWS or VoiceOver. Until that test exists, we do not say the portal is “screen-reader compatible”: we say it was built to be, and that the proof is missing.
Two lines in the home hero fall below the ratio
The eyebrow and the supporting line of the first screen sit over a photograph. We measured 2.78:1 and 4.46:1 — below the 4.5:1 the standard asks for body text. The number changes with the photo, and fixing it means darkening the opening image. It is declared in the repository, with the measurement, rather than hidden.
We do not claim formal conformance
There has been no third-party audit, so we do not claim “WCAG 2.1 AA”. What we do claim is what is above: the criteria we measured, with the number and the instrument.
The search map is a support, not the path
The map view helps those who can see the area. Every piece of information it shows — address, neighbourhood, price — is also in the list beside it, reachable by keyboard. If that ever stops being true, it is a defect, and we want to know.
If something did not work
An accessibility defect only shows itself to the person who runs into it. If you ran into one — a control the keyboard cannot reach, text that disappears into the contrast, a layer that will not close — tell the house. It goes straight to the people who build the portal, and the answer comes with what was done about it.
