Accessibility

The standard this site is built to

This site is built to Level AA of the Web Content Accessibility Guidelines, version 2.2.

That is a target, not a certificate. Every measurement on this page is our own, taken by the people who built the site. What follows is what was actually done, written plainly enough that you can check it rather than take our word for it.

How it was checked

Two ways, on 3 September 2026, and again on 4 September after the top of the home page changed. An automated checker (axe-core) was run on every one of the site's 23 pages, and it reports nothing outstanding against Level A or AA. Then the things a machine cannot judge were gone through by hand: using every page with only a keyboard, checking where focus lands and whether anything covers it, checking that anything that moves can be stopped, and checking that text still fits when it is spaced out or enlarged. What that pass found was fixed the same day; the list of what is still open is below.

Colour that was measured, not eyeballed

Colour here was measured against the ground behind it rather than judged by eye. The grey used for running text sits at 5.67:1 on the pale background and 5.19:1 on the sand. The guideline asks for 4.5:1. Headings, links and the navy sit far higher.

The small uppercase labels on navy grounds, the numbers beside the treatment tabs, and the green of the star glyphs each measured a little short and were darkened or lightened until they clear the line. The faint prompt text and the thin rule under each form field were repaired earlier, on both the contact page and the home page.

The white words over the moving picture at the top of the home page and the contact page were measured against the brightest part of the still photograph behind them, with the navy tint laid over it: 4.6:1 and above for the small text, higher for the large title. The tint was deepened on 4 September to get there.

Colour is never the only signal. A form field with a problem gets a message in words underneath it, not just a red line.

Motion, and switching it off

If your device is set to reduce motion, this site listens. The setting lives in your operating system, not here: Reduce Motion on an iPhone or a Mac, Show animations on Windows. Every page checks it.

With it on:

• The video behind the top of the home page and the contact page does not play. A still photograph stands in its place. (With a data-saver setting on, the video is never downloaded at all and the same photograph is shown.)
• The row of insurance logos on the home page, the two rows of reviews on the smile gallery, and the strip of team photographs on the about page stop drifting.
• Sections stop sliding upward as you scroll. They are simply there.
• Hover effects, the navigation panel and the pricing quiz stop animating.

You do not need that setting to stop things, either. The video has a Pause video button on it. Each drifting row has a Pause button beside it. They stay where you put them.

There is one animated illustration on the site, on the page you land on when a link is broken. It loops, so it never settles on its own. With reduced motion switched on, the browser is handed a still frame of it instead.

The cookie notice

The small notice that asks about Google Analytics is not a pop-up that locks the page. Nothing behind it is disabled, focus is not trapped inside it, and you can scroll and read with it open. It does not take focus when a page loads.

Its two buttons are real buttons of the same size, at least 44 pixels tall, and the Tab key reaches them straight after the Skip to content link. Screen readers announce the notice as a region named Cookie choices.

Choosing Cookie settings at the foot of any page brings the notice back and puts focus on its first button, so the choice can be changed from the keyboard alone.

Using this site with a keyboard

Everything you can click here is a real link or a real button, which is what lets the Tab key reach it and Enter or the space bar work it. The two Services controls in the header and the menu are buttons, because they open a panel rather than leave the page.

The first thing the Tab key reaches on every page is a Skip to content link. It is hidden until you reach it, and it jumps past the header.

Where you are is meant to be obvious. Every form field, button and link draws a visible ring when it has keyboard focus, drawn in the site's navy or green so it clears 3:1 against whatever is behind it. The header at the top of the page is fixed in place, and the site is told to stop scrolling short of it, so a focused control is never parked underneath.

The before-and-after photographs are a slider. It is announced as one, the arrow keys move the divider, and a screen reader hears how much of each photograph is showing.

On a service page the treatment panels behave the way tabs are supposed to: arrow keys move between them, Home and End jump to either end. The panels you scroll sideways on those pages can be reached with Tab and moved with the arrow keys.

The pricing quiz and the booking calendar open in a dialog. Focus moves into it, stays inside it while it is open, and returns to the button that opened it when you close it. Escape closes either. Each quiz question is read out as it appears, and where choosing an answer moves you to the next question, the question says so first.

Headings, image descriptions and screen readers

Every page carries exactly one main heading, and the headings below it are written to run in order, so a screen reader can move heading to heading and get the shape of the page.

Each page is also built out of real regions rather than anonymous boxes: a header, a main area, a footer, navigation. That is what lets a screen reader skip past the menu and go straight to the content.

Every picture carries a description. Where the picture says something, a treatment illustration or a photograph of a room, that description is written out. Where it is decoration, the description is deliberately left empty, so a screen reader passes over it rather than reading a file name aloud. The little arrows on links are marked as decoration too, so a link reads as its words and nothing else. On the service pages, the smile gallery and the broken-link page this is enforced by the build itself. The moving picture behind the top of the home page and the contact page is decoration and is marked as such, so a screen reader passes over it; the words beside it carry everything it shows.

On a phone

Below 700 pixels wide, which covers phones, these are sized for a fingertip rather than a cursor:

• the links in the footer, and the contact details there
• the service links and the view all link
• the entries in the menu, and the menu button itself, which is 44 pixels
• the contents list beside a page like this one
• the two buttons in the bar along the bottom of the screen, which are 58
• the consent box on the forms, which is 24

On a phone the header keeps only the menu button; the phone number moves into the bar along the bottom, which slides up once you have scrolled past the top of the page and is out of the Tab order until it does. The number in the footer is the one that is there at every width. It is a link. Tap it and the call starts.

With JavaScript switched off

The words and the pictures do not need JavaScript. Turn it off and every page still reads, every link still works, and the contents list beside a page like this one still takes you to the right section.

Two things are built in JavaScript and will not work without it: the booking form and the pricing quiz. The bar along the bottom of a phone screen needs it too. So do the two Services buttons; without it, the services pages are still one link away in the footer of every page.

What is not right yet

We would rather write these down than let you find them.

• We have no record of anyone who uses a screen reader daily having tested this site. It was built to be read aloud and checked with the tools we have. That is not the same as somebody who depends on one sitting down with it. Until that happens, treat this page as unfinished.
• The map on the home page is Google's, not ours. It is a panel embedded from Google Maps. We gave it a title so it announces itself, but everything inside it is Google's to build and outside our reach. The address is written out in full beside it, and a plain link opens directions in whichever maps app you already use. Neither of those needs the map.
• The booking calendar is the practice's scheduling company's, not ours. It runs inside a frame on our page, and what is inside that frame is theirs to build. If it gives you trouble, the phone number above books the same appointments.
• The bot check on the appointment form and the pricing quiz is Cloudflare's. It usually runs without showing anything. When it does show a box to tick, that box is Cloudflare's to build: it can be reached with the keyboard and announces itself, but like the calendar it is outside our reach.
• Text is sized in pixels. It grows when you zoom the page, with Ctrl and plus or a pinch, and that is the route we would point you to. It will not follow a default text size set in your browser's own preferences.

Tell us what got in your way

If something here stopped you, we would like to know.

Call (520) 214-2484, Mon to Thu 9 AM to 5 PM, Fri 8 AM to 2 PM. Closed Saturday and Sunday.

Tell us which page you were on and what happened. The form would not take my phone number is enough.

If it is easier said in person, the practice is at 6288 E Grant Rd, Tucson, AZ 85712, and there is parking at the door. The contact page has the hours, the address and directions.