Accessibility

Our goal

We build towards the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That is the standard we design and test against. We do not claim to meet it perfectly everywhere, and we would rather tell you where we stand than publish a guarantee we cannot support.

What we have built

• A skip link to the main content, visible as soon as it receives keyboard focus.
• Visible keyboard focus on every interactive element. The focus color was chosen so the ring keeps its contrast against the page rather than against a button fill.
• Color contrast measured at build time from the design tokens rather than judged by eye. Every declared pairing meets WCAG 2.2 AA.
• Buttons, the header and footer navigation, in-page jump links and question lists are at least 44 pixels tall — comfortably above the 24-pixel minimum the guidelines set. Breadcrumbs and links inside a sentence take the height of the text they sit with, which the guidelines allow, and are spaced far enough apart to be easy to hit.
• Motion reduced, including scrolling behavior, when your browser or operating system asks for it.
• One main heading per page, with headings below it in order.
• Header, main content and footer marked as landmarks, and navigation regions named.
• A text alternative on every image.
• In-page links offset so the sticky header never covers the heading you jumped to.
• Layouts that reflow to a 320-pixel-wide screen without scrolling sideways.
• Amenity information and safety disclosures never hidden behind an accordion or a “show more” control.
• A mobile menu that opens and closes from the keyboard, reports whether it is open, closes with Escape, and returns focus to the button that opened it.
• Navigation and booking links that work without JavaScript.

What we have not done

This section matters as much as the one above it. These are real gaps, not disclaimers.

• We have not had a formal third-party accessibility audit or certification.
• We do not claim conformance. WCAG 2.2 AA is what we build towards, not something we guarantee.
• We have not tested every combination of browser, screen reader and assistive technology.
• The booking pages use components provided by OwnerRez, which we do not control. We report problems there to OwnerRez rather than being able to fix them ourselves.
• The site is still being built. Pages that have not been released yet have not been reviewed, and this page is updated as they are.

How we test

• Colour contrast is computed from the design tokens during every build, so the published values cannot drift from what was approved.
• Layout and target sizes are measured in an automated browser at representative widths from 320 to 1600 pixels.
• Keyboard walkthroughs and live checks in real browsers are carried out by the property owner.

Tell us about a problem

If something on this site is difficult or impossible for you to use, we want to know. Email contact@booksugarmountain.com and, if you can, tell us the page, what you were trying to do, and the browser or assistive technology you were using. That detail is usually what makes a problem findable.

If the site itself is the barrier, you can also reach us through the other methods on our contact page, and we will help you directly rather than asking you to use the part that is not working.