Studio DesignMiami Design DistrictHJ Studio Design

Legal

Accessibility

The level this site is built to, what was done to reach it, what is still missing, and how to tell us when something stops you.

Last updated: 18 August 2026.

The level we build to

WCAG 2.2, level AA. It is the standard most commonly used in the United States to measure whether a website can be used by everyone, and it is the one we work against on every page.

We do not claim to have finished. Everything below is either something we did and can be checked, or something we know is still open. The second list is the one most statements leave out.

What has been done

Each of these is verifiable. Open the page, test it, and tell us if it fails.

01

Contrast measured token by token

Every colour pair was measured before it was used, and the ratio sits next to the colour in the code: body text at 13.1 to 1, muted text at 5.39 to 1, the brass accent at 4.71 to 1 on light backgrounds and 8.36 to 1 on dark ones, field borders at 3.5 to 1. The minimum the standard asks for is 4.5 to 1 for text and 3 to 1 for controls.

02

Visible focus on every interactive element

A two pixel outline in the accent colour, three pixels clear of the element, on links, buttons, form fields, the language switch and the before and after slider. Nothing in the stylesheet removes it, on any state.

03

The whole site works from the keyboard

Tab reaches every link, button and field in the order they are read. The before and after comparator moves with the arrow keys because it is a real range input, not a script attached to a div. The navigation is five items long, so reaching the content from the top takes a handful of key presses.

04

Touch targets of at least 44 pixels

Buttons are 48 pixels tall, the compact ones 44, and so are the language switch and every item in the mobile contact bar. Nothing on this site needs a precise finger.

05

Real alternative text on informative images

Project photographs say what the room is and what was done to it, not "kitchen 1". Before and after pairs describe each state separately, so the comparison exists in text as well as in the image. Decorative elements are hidden from screen readers instead of being read out as noise.

06

Reduced motion is respected

If your system asks for less movement, transitions and entrance effects are switched off. There is nothing that loops, autoplays, rotates or moves on its own to begin with. The hero is a still photograph.

07

Headings in order, one h1 per page

You can move through a page by structure and get an outline that makes sense. Lists are marked up as lists, every form field has a label tied to it, hints are linked to their field, and validation errors are announced when they appear rather than only turning something red.

08

It survives zoom

Text stays readable at 200 percent and the layout reflows into one column instead of forcing you to scroll sideways. Sizes are set in relative units, so your browser font size is respected.

09

The content arrives before the scripts

Pages are rendered on the server. The text, the links and the form are there even if a script fails to load or is blocked.

10

Each language has its own address

English and Spanish are separate pages, and each declares its own language in the markup. A screen reader pronounces the Spanish pages in Spanish. The old site ran an automatic translation widget over an English document, which read as English with Spanish words in it.

What is still missing

Written down so you do not have to discover it yourself.

  • No independent audit yet. Everything above is our own work, tested with the keyboard and with automated checks. A review by someone who uses assistive technology every day has not happened. Until it does, treat this page as a description of what we built, not as a certificate.
  • Screen reader coverage is incomplete. We cannot yet say that every page behaves the same way in every combination of screen reader and browser.
  • The before and after comparator is visual at heart. Both photographs carry their own description, so the information exists in text, but the act of comparing them is not solved for someone who cannot see them.
  • Some project photographs deserve a longer description than an alt attribute holds comfortably. We are writing those.
  • What lives outside this site follows its own rules. WhatsApp, Instagram and Facebook are not ours, and we cannot fix their accessibility.
  • There is no video today. If we publish one, captions and a transcript go up with it, not later.

If something stops you

Tell us and we fix it. This is not a form that gets filed somewhere. It is an email that Heriberto reads.

You do not need to know the technical name of the problem. Describing it in your own words is enough.

  • Which page you were on.
  • What you were trying to do.
  • What happened instead.
  • Which browser, and which assistive technology if you use one. That helps us reproduce it.

What we commit to when you write

  1. We reply within two business days, from a person, not from an autoresponder.
  2. If the barrier blocks something specific, we do that thing with you by phone or email at once, while the fix is made. You should not have to wait for a code change to get a price or book a visit.
  3. We tell you what we are going to do and by when, or we say plainly that we cannot solve it yet, and why.
  4. When it is fixed, we write back to say so.

Report a barrier

Email, phone or WhatsApp, whichever suits you. All three reach the same person.

180 NE 41st Street, Miami FL 33137. Monday to Friday, 9.00 to 18.00. Saturday by appointment.

What we do with what you send us: Privacy policy

heriberto@hjstudiodesign.com305 942 7801WhatsApp
Start a projectShowroomWhatsAppCall