Accessibility

Everyone should be able to use this site, on any device, browser, or assistive tool. Here is the standard it is built to, how it was tested, and what is still open.

The standard

This site is built to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That is the target. Automated tools and keyboard tests check it, and anything that falls short is named on this page.

What was done

  • Every page has a skip link, one main heading, and a name on every button and link.
  • No text is smaller than 14px, and text meets the 4.5:1 contrast rule.
  • Every photo has a short description in English and Spanish. Drawings that only decorate are hidden from screen readers. The Before and After labels on the photos are real text, so they translate.
  • The EN/ES buttons switch the whole page and set its language, so screen readers read it in the right voice. On English pages, the phrase Hablamos español is marked as Spanish.
  • The phone menu button tells screen readers if the menu is open. Escape closes it and puts focus back on the button.
  • The services list on the home page uses real buttons that say if each service is open or closed. One opens at a time, by mouse, touch, or keyboard.
  • The before and after slider has named Previous and Next buttons, and each one turns off at the end of the row. It never moves on its own.
  • Every field on the booking form has a label, and the four services are grouped under one heading. If a required field is empty, the browser points it out and puts focus on it. If no service is picked, the form says so, screen readers hear the message, and focus moves to the services.
  • Keyboard focus shows a thick outline on every link, button, and field.
  • There is no video, and nothing plays on its own. When your device asks for reduced motion, fades and smooth scrolling are turned off.
  • No accessibility widget or overlay. The site is built to work without one.

Known limits

  • The date field on the booking form is your browser's own date picker, so its language and format follow your browser, not the EN/ES buttons.
  • A screen reader pass by a person (NVDA on Windows, VoiceOver on iPhone) is still to do.

Test log

October 7, 2026. All 7 pages scanned with axe-core 4.14 against WCAG 2.2 A and AA at desktop (1280px) and phone (390px) widths, in English and in Spanish: 0 failures. The first scan found one, on every page: the spoken name of the logo did not match its visible words. Fixed the same day. Text that axe could not check on its own (over the hero photo and the footer drawing) was checked from screenshots. The footer drawing was dimmed so the text over it meets 4.5:1. No sideways scrolling and no text under 14px at five widths from 1920px down to 390px. The phone menu, services list, slider, booking form, and EN/ES buttons were tested by keyboard in Chromium with an automated script: all checks passed, with 0 console errors. Tools: axe-core, Playwright, and the Back Rhodes Multimedia layout check.

Tell us

If anything on this site is hard to use, call or text (786) 428-8878 with the page and what happened. We will get you what you need another way.

Statement last tested October 7, 2026.