Document under review. The institutional details marked below are still to be completed and this version is not final.
Accessibility
A place that promises rest cannot be hard to cross.
This is a statement of partial conformance with WCAG 2.2, level AA. It says what already works, what does not yet work, and where to tell us when something stops you. We prefer a truthful statement to a handsome badge.
Last updated
Our commitment
Accessibility on this site is treated as part of the service, not as a checklist item — for the same reason a well-drawn ramp does not look like a ramp. Whoever arrives here should be able to read, decide and speak to us, with the body, the device and the attention they have that day.
We publicly commit to pursuing WCAG 2.2 level AA on every page, and to saying plainly where we have not arrived yet.
Level of conformance
We declare the following, without rounding up:
- Reference standard: WCAG 2.2, level AA, published by the W3C.
- Declared level: partial conformance — most level AA criteria are met, with the reservations listed below.
- Scope: the public pages of this site, in the three languages in which it is published.
Partial conformance means the level AA criteria are met across most of the site, but points remain unverified or unresolved. While one of them stands, we do not declare full conformance.
What is already in place
Every item below is in the code, not in the plan:
- Server-side rendering: all essential content arrives in the initial HTML and stays readable with JavaScript turned off.
- A skip link to the main content as the first focusable element of every page.
- Full keyboard navigation, with predictable focus order and no traps.
- A visible focus ring, drawn to stay legible over graphite, over sand and over photography — and which hands control back to the system in high contrast mode.
- Contrast verified by calculation, not by impression: the palette carries functional variants created to reach 4.5:1 on small text and 3:1 on large text.
- Respect for the system reduced motion preference: the opening animation is suppressed and reveals go straight to their final state.
- A language selector without country flags: visible code, the full language name for screen readers, and lang and hreflang attributes on each option.
- A single h1 per page, a heading hierarchy without skipped levels, and the page language declared on the root element.
Forms carry a real label bound to the field, an error message in text — never by colour alone — and controls operable by keyboard.
Known limitations
This is the part most statements leave out. Our reservations, today:
- No independent external audit has been completed. This statement rests on self-assessment.
- Some image descriptions are still being written: a few photographs carry generic alternative text, short of what the scene deserves.
- The booking engine and other third-party services reached from here are outside our control, and their conformance is not guaranteed by us.
- The motion pause control depends on JavaScript. With JavaScript turned off, the brake on continuous animation is left to the system reduced motion preference.
- Assistive technology testing so far has been occasional and does not systematically cover every screen reader in use.
- Passages in a foreign language inside a text do not always carry the language marking, which may affect pronunciation in screen readers.
None of these limitations is permanent. They are listed because they are in the queue — and leaving this list is what measures our progress.
Compatibility with assistive technology
This site is built with semantic HTML and no widget that replaces a native control. It is designed to work with:
- Recent browsers, on desktop and on mobile, in their last two stable versions.
- Screen readers that honour the conventions of semantic HTML and the WAI-ARIA specifications.
- Zoom up to 200% and reflow at 320 pixels wide, with no loss of content and no horizontal scrolling.
We use no accessibility overlay — those bars that promise to fix a site from the outside. They tend to get in the way of people who already master their own assistive technology. We prefer to fix the code.
How we evaluate
The method is self-assessment, and we say so in plain words. It rests on three steps:
- Manual review of the code of every published page against the level A and AA criteria.
- Contrast verification calculated over the palette, with the figure recorded beside each functional colour.
- A complete keyboard run through each page, from the first skip link to the last link in the footer.
No independent external audit has been completed as of the date of this statement. When there is one, we will publish the result here — including whatever it finds wrong.
Reporting a barrier
If something here stopped you from doing what you came to do, the fault is ours and we want to hear about it.
- Write to [A PREENCHER: e-mail para relatos de acessibilidade].
- Describe the page, what you tried to do and what happened. If you know them, tell us the browser and the assistive technology in use.
- If you prefer another format — telephone, audio, message — say so in the first line, and we will reply through whichever channel suits you best.
We reply within [A PREENCHER: prazo de resposta a relatos de acessibilidade] and tell you what has been fixed, what is being fixed and what we could not resolve — with the reason.
Review of this statement
This statement is reviewed whenever a new page goes live or a reported barrier is fixed. The date at the top marks the last review.
It covers the institutional site of GOA Hospitality Group. Third-party systems reached from here, such as the booking engine, have statements of their own — or ought to, and we press them for it.
Accessibility is not declared. It is demonstrated.
If you have met a barrier, a confusing sentence or a focus ring that vanished, write to [A PREENCHER: e-mail para relatos de acessibilidade]. A barrier report jumps our queue — ahead of any aesthetic improvement.