Our Commitment to Access

Accessibility Statement

We want everyone, including people with disabilities, to be able to use this website, learn about our care, and contact our office. This page explains what we have done, how we test, and what is still open.

Current status

Highly compliant with WCAG 2.2 Level AA

Last audit: November 1, 2026 · Fixes released: November 11, 2026 · Automated checks: 0 of 358 page runs with a WCAG failure

This statement was last updated on November 12, 2026.

Our Commitment to ADA Compliance

Finesse Plastic Surgery treats this website as part of how we serve patients, and we work to make it usable by people who are blind or have low vision, are deaf or hard of hearing, or have motor or cognitive disabilities. We are working to make the site meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

This website is highly compliant with WCAG 2.2 Level AA. Every page passes our automated accessibility checks on desktop and mobile, and the critical and serious items from our November 2026 audit have been fixed. In the formal W3C terms, a site with any open item is described as partially conformant, so we list the few remaining items below and are working through them.

Applicable Laws and Standards

  • Americans with Disabilities Act (ADA), Title III

    Citation: 42 U.S.C. § 12181 et seq. · Jurisdiction: Federal

    Businesses open to the public must give people with disabilities equal access to their goods and services.

  • California Unruh Civil Rights Act

    Citation: California Civil Code § 51 · Jurisdiction: California

    Businesses in California must offer full and equal access to everyone, including people with disabilities. A violation of the ADA is also a violation of this Act.

  • Section 508 of the Rehabilitation Act

    Citation: 29 U.S.C. § 794d · Jurisdiction: Federal (reference standard)

    Sets accessibility rules for federal technology. We use it as a reference, not as a rule that applies to us.

  • Web Content Accessibility Guidelines (WCAG) 2.2

    Citation: W3C Recommendation, October 2023 · Jurisdiction: International standard

    The technical standard we work toward, at Level AA.

What Our Latest Audit Found, and What Changed

On November 1, 2026 our website team audited every page of the live site. On November 11, 2026 we released fixes and ran the same checks again. These numbers come from axe-core 4.14. Every page on the live site, each on a desktop screen (1440 pixels wide) and a mobile phone screen (iPhone 13 size).

Before fixes, November 1, 2026

244 of 352

page runs had at least one automated WCAG failure

After fixes, November 11, 2026

0 of 354

page runs had an automated WCAG failure

MeasureBeforeAfter
Page runs with any automated WCAG failure244 of 3520 of 354
Elements with low text contrast2840
Elements whose name does not match the visible label2780
Keyboard focus stops hidden under the cookie notice32 of 700 of 70
Small touch targets150
Pages with text cut off at 320 pixels180

Before: November 1, 2026, 176 pages. After: November 11, 2026, 177 pages (the new accessible New Patient Packet page was added). Automated checks cover only part of WCAG.

At a Glance

7

Reviews and fix releases since November 2025

37

Improvements released

177

Pages checked on desktop and mobile

2

Business days to answer accessibility requests

Audit History and Measures Taken

This is the record of our accessibility work since November 2025: each review, what it found, and what we changed. WCAG criteria are listed so you can see which part of the standard each change addresses.

  1. November 2025: Baseline accessibility features

    Internal review

    Our website team added the core accessibility features the site is built on: skip links, keyboard support, landmarks, labels and alternative text.

    • Skip links

      Three skip links at the top of every page: skip to main content, skip to navigation, and skip to contact information. They appear when you press Tab.

      WCAG 2.4.1 Bypass BlocksLevel AComplete

    • Keyboard focus styles

      Visible focus styles for keyboard users. These were replaced in November 2026 by a stronger two-tone outline that shows on every background.

      WCAG 2.4.7 Focus VisibleLevel AAComplete

    • Page landmarks

      Header, navigation and footer regions marked up so screen reader users can move between them.

      WCAG 1.3.1 Info and RelationshipsLevel AComplete

    • Alternative text for images

      Descriptive alternative text added to meaningful images. Decorative images are hidden from screen readers.

      WCAG 1.1.1 Non-text ContentLevel AComplete

    • Mobile menu keyboard support

      The mobile menu opens and closes by keyboard and returns focus to the menu button.

      WCAG 2.1.1 KeyboardLevel AComplete

    • Audio player controls

      The audio player on blog posts has play, pause, skip and volume controls that work by keyboard.

      WCAG 2.1.1 KeyboardLevel AComplete

    • Form labels

      Form fields have labels tied to them in code, and required fields are marked.

      WCAG 3.3.2 Labels or InstructionsLevel AComplete

  2. February 2, 2026: Privacy and consent review

    Internal review

    A wider site review covering accessibility, privacy and search. The accessibility-related change was a way to change cookie choices at any time.

    • Cookie Preferences link

      A Cookie Preferences link in the footer reopens the cookie choices so you can change or withdraw consent.

      Complete

    • FAQ structure

      Frequently asked questions use a consistent question and answer structure in the code.

      WCAG 1.3.1 Info and RelationshipsLevel AComplete

  3. February 13, 2026: Forms, dialogs and written process

    Internal review

    A review of forms, dialogs and page announcements, with fixes released the same day, and the first version of this statement.

    • Accessibility statement published

      This page was created, with a contact method, a two business day response goal and known limitations.

      Complete

    • Form error announcements

      Contact form errors are announced to screen readers and linked to the fields they describe, and invalid fields are marked as invalid.

      WCAG 3.3.1 Error IdentificationLevel AComplete

    • Autofill on form fields

      Name, email and phone fields tell browsers what they are for, so they can be filled in automatically.

      WCAG 1.3.5 Identify Input PurposeLevel AAComplete

    • Treatment planner dialog focus

      When the treatment planner opens, focus moves into it and stays there while it is open, and returns to the button you used when it closes.

      WCAG 2.4.3 Focus OrderLevel AComplete

    • Reduced motion

      When your device asks for reduced motion, page animations and smooth scrolling are turned off.

      WCAG 2.3.3 Animation from InteractionsLevel AAAComplete

    • New tab warnings

      Links that open in a new tab, such as maps and review sites, say so to screen reader users.

      WCAG 3.2.5 Change on RequestLevel AAAComplete

    • Current page in the menu

      Menu links mark the page you are on, so screen readers announce it as the current page.

      WCAG 4.1.2 Name, Role, ValueLevel AComplete

    • Page change announcements

      When you move to a new page, its title is announced to screen reader users.

      WCAG 4.1.3 Status MessagesLevel AAComplete

    • Written accessibility process

      Internal documents written for handling accessibility feedback, a pre-release checklist, a remediation log and an internal policy.

      Complete

  4. February 14, 2026: Brand color contrast and first automated test run

    Remediation

    The brand text color was darkened to meet contrast minimums, and automated tests were run on a sample of pages.

    Result: axe-core 4.10 reported no violations on the 10 pages tested, and Google Lighthouse gave the home page an accessibility score of 100 (automated checks only). The November 2026 audit of every page later found problems these sample checks did not cover.

    • Brand color darkened

      The brand color used for text was changed from #9B8B7E (3.29 to 1 on white) to #807368 (4.60 to 1), using a script that calculates contrast with the WCAG formula.

      WCAG 1.4.3 Contrast (Minimum)Level AAComplete

    • Blog page buttons named

      The previous and next page buttons on the blog, which show only arrows on phones, now have names.

      WCAG 4.1.2 Name, Role, ValueLevel AComplete

    • Automated test scripts

      Scripts for axe-core and Lighthouse were fixed and added to the project so the checks can be repeated.

      Complete

  5. November 1, 2026: Full-site WCAG 2.2 AA audit

    Internal audit

    Our website team reviewed all 176 pages of the live site against WCAG 2.2 Level AA, each on a desktop screen and a mobile phone screen, with axe-core 4.14, Google Lighthouse 13.6, and browser checks of keyboard use, focus visibility, reflow at 320 pixels, zoom and reduced motion.

    Result: 244 of 352 automated page runs had at least one WCAG failure. This was not a review by an independent firm and did not include screen reader testing.

    • Low contrast text

      284 elements had text or link colors below the 4.5 to 1 minimum, many in the footer and on legal pages.

      WCAG 1.4.3 Contrast (Minimum)Level AAFound in audit

    • Button and link names

      278 elements had accessible names that did not start with their visible label.

      WCAG 2.5.3 Label in NameLevel AFound in audit

    • Focus outline hard to see

      The focus outline disappeared on white sections and on the dark footer.

      WCAG 2.4.7 Focus VisibleLevel AAFound in audit

    • Cookie notice covered focused items

      32 of 70 keyboard focus stops on a tested page were hidden behind the cookie notice.

      WCAG 2.4.11 Focus Not Obscured (Minimum)Level AAFound in audit

    • Menus not keyboard friendly

      The About and Procedures submenus opened on hover only.

      WCAG 2.1.1 KeyboardLevel AFound in audit

    • Home page video could not be paused

      The background video on the home page played with no pause control.

      WCAG 2.2.2 Pause, Stop, HideLevel AFound in audit

    • Text cut off on small screens

      Large headings were clipped at 320 pixels wide on 18 pages.

      WCAG 1.4.10 ReflowLevel AAFound in audit

    • Embedded video players

      Embedded YouTube players had unnamed buttons and invalid attributes in 22 places.

      WCAG 4.1.2 Name, Role, ValueLevel AFound in audit

    • Scanned patient packet

      The New Patient Packet was available only as a scanned PDF that screen readers cannot read.

      WCAG 1.1.1 Non-text ContentLevel AFound in audit

    • Small touch targets

      Some footer links were smaller than the 24 by 24 pixel minimum in 15 places.

      WCAG 2.5.8 Target Size (Minimum)Level AAFound in audit

  6. November 11, 2026: Fixes for the November 1 audit

    Remediation

    We released fixes for every critical and serious issue the audit found that is within our control, then ran the same automated checks again on the live site.

    Result: After the fixes, 0 of 354 automated page runs had a WCAG failure (177 pages, desktop and mobile), down from 244 of 352. Automated checks find only some kinds of problems, so this does not mean every page is fully accessible.

    • Two-tone focus outline

      One focus outline for the whole site: a dark brown ring with a white band inside it, so it shows on light sections, the dark footer and dark buttons.

      WCAG 2.4.7 Focus Visible, 2.4.11 Focus Not ObscuredLevel AAComplete

    • Cookie notice

      The cookie notice is reached right after the skip links, closes with Escape, takes less room on phones, and no longer covers the item that has focus.

      WCAG 2.4.3 Focus Order, 2.4.11 Focus Not ObscuredLevel AAComplete

    • Keyboard menus

      The About and Procedures menus have buttons that open them by keyboard and move focus to the first link. Escape closes them and returns focus. The mobile menu also closes with Escape.

      WCAG 2.1.1 Keyboard, 4.1.2 Name, Role, ValueLevel AComplete

    • Home page video pause

      The home page video has a Pause and Play button, and it does not play when your device asks for reduced motion.

      WCAG 2.2.2 Pause, Stop, HideLevel AComplete

    • Darker text and link colors

      Footer text, footer links, the blog back link, landing page call buttons and links on legal pages were darkened to at least 4.5 to 1.

      WCAG 1.4.3 Contrast (Minimum)Level AAComplete

    • Reflow on small screens

      Headings resize to fit and long words wrap, so no text is cut off at 320 pixels wide.

      WCAG 1.4.10 ReflowLevel AAComplete

    • Names match visible labels

      Footer contact buttons, review links and the gallery filter have names that start with the words you see.

      WCAG 2.5.3 Label in NameLevel AComplete

    • Video player and transcripts

      Procedure videos load a YouTube player only when you press a named play button, and every procedure video has a full text transcript below it.

      WCAG 4.1.2 Name, Role, ValueLevel AComplete

    • New Patient Packet as a web page

      The New Patient Packet is available as an accessible web page next to the PDF, and our office offers other formats by phone.

      WCAG 1.1.1 Non-text Content, 1.3.1 Info and RelationshipsLevel AComplete

    • Keyboard scrolling

      On desktop, the page scrolls with the arrow keys, Page Up, Page Down, Space, Home and End.

      WCAG 2.1.1 KeyboardLevel AComplete

    • Larger footer targets

      Footer links and buttons are at least 24 by 24 pixels.

      WCAG 2.5.8 Target Size (Minimum)Level AAComplete

    • Forms, gallery and map

      Treatment planner errors are tied to their fields, gallery images have better alternative text and heading levels, and the embedded map is hidden from screen readers because the address is listed as text.

      WCAG 3.3.1 Error Identification, 1.1.1 Non-text ContentLevel AComplete

  7. November 12, 2026: Page structure and keyboard navigation with smooth scrolling

    Remediation

    We fixed the page structure items left from the November 1 audit and tested keyboard navigation with the smooth scrolling effect turned on, then ran the automated checks on every page again.

    Result: On the live site, 0 of 358 automated page runs had a WCAG failure (178 pages and the page-not-found page, desktop and mobile). Page runs without a single main content area went from 143 to 0, and page runs with skipped heading levels from 10 to 0. Our scripted keyboard test made 1,400 focus stops on the home, contact, breast augmentation, gallery and treatment planner pages, on desktop, a smaller laptop screen and a phone, with smooth scrolling on and with reduced motion, and no focused item was hidden.

    • One main content area on every page

      Every page now marks exactly one main content area, and the Skip to main content link moves focus to it. The site header and footer are marked as their own regions.

      WCAG 1.3.1 Info and Relationships, 2.4.1 Bypass BlocksLevel AComplete

    • Headings in order

      Four blog posts and the Patient Bill of Rights no longer skip heading levels. The headings look the same as before.

      WCAG 1.3.1 Info and RelationshipsLevel AComplete

    • Keyboard navigation with smooth scrolling

      Tab and Shift+Tab bring each focused item into view clear of the menu bar and the cookie notice, the menu bar slides back when one of its links gets focus, and Home and End still work after tabbing through a page.

      WCAG 2.4.3 Focus Order, 2.4.11 Focus Not ObscuredLevel AAComplete

    • Treatment planner scrolling

      On desktop, the whole treatment planner page now scrolls with the arrow keys, Page Down, Space and End.

      WCAG 2.1.1 KeyboardLevel AComplete

Measure Taken: Brand Color Contrast

The problem: our original brand color, #9B8B7E, had a contrast of 3.29 to 1 on white, below the WCAG minimum of 4.5 to 1 for normal text.

What we did: in February 2026 we used a script that applies the WCAG contrast formula to find the lightest version of the color that passes. It chose #807368 (4.60 to 1). In November 2026 we darkened more text to #6B5D52 where the audit found low contrast, including on this page.

Before

#9B8B7E

3.29 to 1 on white

Below WCAG AA

Brand color now

#807368

4.60 to 1 on white

Meets WCAG AA

Darker text color

#6B5D52

6.34 to 1 on white

Meets WCAG AA

Status by Category

Each category groups related WCAG success criteria. The status reflects what we have fixed and tested, not a score.

  • Keyboard Navigation

    Fixes released

    Menus, the cookie notice, the treatment planner and page scrolling work by keyboard, and keyboard navigation was tested with smooth scrolling on. A full walkthrough of every page by a person using only a keyboard is still to be done.

    WCAG 2.1.1WCAG 2.1.2WCAG 2.4.3

  • Focus Visibility

    Fixes released

    A two-tone outline shows which item has focus on every background, and the cookie notice no longer covers it.

    WCAG 2.4.7WCAG 2.4.11WCAG 1.4.11

  • Color and Contrast

    Partly addressed

    Automated checks find no low contrast text after the November fixes. Headings placed over photos have not all been checked by hand.

    WCAG 1.4.3WCAG 1.4.11

  • Small Screens and Zoom

    Fixes released

    Pages reflow at 320 pixels wide without cutting off text, and footer targets meet the 24 pixel minimum.

    WCAG 1.4.4WCAG 1.4.10WCAG 2.5.8

  • Forms and Input

    Fixes released

    Fields are labeled, errors are announced and tied to their fields, and contact fields support autofill.

    WCAG 1.3.5WCAG 3.3.1WCAG 3.3.2WCAG 4.1.3

  • Images and Documents

    Partly addressed

    Images have alternative text and every procedure video has a transcript. The printable New Patient Packet PDF is still a scan, with an accessible web version beside it.

    WCAG 1.1.1WCAG 1.3.1

  • Motion and Animation

    Fixes released

    The home page video can be paused, and animations stop when your device asks for reduced motion.

    WCAG 2.2.2WCAG 2.3.3

  • Screen Reader Support

    Not yet tested

    Every page has one main content area and headings in order, and names, roles and announcements pass automated checks. The site has not yet been tested with VoiceOver or NVDA.

    WCAG 1.3.1WCAG 4.1.2WCAG 4.1.3

Our Testing Tools and Methodology

Our audits combine automated checkers with checks in a real browser. The November 2026 audit was done by our own website team. It was not a review by an independent accessibility firm.

Automated tools find only some kinds of accessibility problems, so passing them does not mean a page is fully accessible. That is why we also check keyboard use, focus, small screens and motion by hand.

  • axe-core

    Automated

    Open source accessibility checker from Deque, run in a real browser on every page of the live site.

    Version: 4.14

    Last run: November 12, 2026

    Latest result: 0 of 358 page runs with a WCAG failure

  • Google Lighthouse

    Automated

    Google’s page audit tool. Its accessibility score covers automated checks only.

    Version: 13.6

    Last run: November 1, 2026

    Latest result: Used in the November 1 audit

  • Contrast calculator

    Automated

    A project script that applies the WCAG contrast formula to choose brand colors that meet the minimum.

    Last run: February 14, 2026

    Latest result: Brand text color set to #807368 (4.60 to 1 on white)

  • Keyboard and focus checks

    Browser checks

    Scripted keyboard runs in a real browser, reviewed by our team: focus order, focus visibility, menus, the cookie notice, the video pause button, and Tab, Shift+Tab, the skip link and scrolling keys with smooth scrolling on.

    Last run: November 12, 2026

    Latest result: 1,400 focus stops on 5 pages at 4 screen setups, none hidden

  • Reflow, zoom and reduced motion

    Browser checks

    Pages viewed at 320 pixels wide and zoomed, and with the reduced motion setting turned on.

    Last run: November 11, 2026

    Latest result: No clipped text on the 18 flagged pages, no video playing under reduced motion

  • Screen readers (VoiceOver, NVDA)

    Manual

    Testing with the screen readers built into Apple devices and the free NVDA reader for Windows.

    Last run: Not yet done

    Latest result: Planned

Our Testing Schedule

  • Every release

    We run automated accessibility checks on the pages a change touches before it goes live.

  • After major site changes

    When we redesign pages, add new page types or change the menus, we audit the site again.

  • At least once a year

    We repeat a full-site audit at least once a year and update this statement with the results.

What We Tested On

  • Desktop screen, 1440 pixels wide, in a Chromium browser
  • Mobile phone screen, iPhone 13 size, in a Chromium browser
  • Small screen reflow at 320 pixels wide
  • Keyboard only, with the reduced motion setting on and off
  • Keyboard navigation with smooth scrolling on: Tab, Shift+Tab, the skip link and scrolling keys

Not Yet Tested

  • Screen readers, such as VoiceOver, NVDA, JAWS and TalkBack
  • A full walkthrough of every page by a person using only a keyboard
  • Voice control and switch devices

Known Limitations

These parts of the site do not yet fully meet WCAG 2.2 Level AA. If any of them gets in your way, contact us and we will help you another way.

  • New Patient Packet PDF. The printable packet is a scanned document that screen readers cannot read. The same content is available as an accessible text version of the New Patient Packet, and our office can help you complete it.
  • Text over photos. We have not yet checked the contrast of every heading placed over a photo.
  • Third-party content. Embedded YouTube players and Google Maps are provided by other companies, and we cannot fully control their accessibility. Our address and directions are also listed as text on the contact page.
  • Screen reader testing. We have not yet tested the site with screen readers such as VoiceOver and NVDA.

Our Internal Policy

Accessibility is part of how we build and update this website, so fixes stay fixed and new pages start out accessible.

Who Does What

  • Website team: builds pages with labeled controls, keyboard support and the site-wide focus outline, and runs the automated checks
  • Content: new images get alternative text, and new pages use headings in order
  • Office staff: answer accessibility requests by phone and email, and provide information in other formats on request

Standards for New Work

  • Every link, button and form field shows the site-wide focus outline
  • Menus and dialogs open, close and move focus correctly by keyboard
  • Text meets 4.5 to 1 contrast, or 3 to 1 for large text
  • Videos added to procedure pages come with a full transcript
  • New patient documents get an accessible web version

Core policy: Accessibility is checked before each release

Before a change goes live, we run automated accessibility checks on the pages it touches. When those checks find a WCAG failure, we fix it before release.

Third-Party Vendor Accountability

Some content on this site comes from other companies. We are still responsible for your access to our information, so here is each one and what we do about it.

  • YouTube

    Mitigated
    Purpose
    Procedure videos
    Accessibility status
    Player controlled by Google
    What we do
    The player loads only when you press a named play button, and a full text transcript is under every procedure video.

  • Google Maps

    Mitigated
    Purpose
    Office location map
    Accessibility status
    Known limitations
    What we do
    The map is hidden from screen readers. Our address and phone number are listed as text, and a link opens the full Google Maps site.

  • Google Analytics

    N/A
    Purpose
    Website analytics
    Accessibility status
    Not applicable
    What we do
    Runs in the background with no visible controls.

No chat widgets. We do not use third-party chat widgets or embedded booking tools, which are often hard to use with a keyboard or screen reader. Our forms are built and tested by our own team.

Keyboard Shortcuts and Navigation Guide

You can use this website with a keyboard alone. These keys work across the site.

Basic Navigation

Tab
Move forward through links, buttons and fields
Shift + Tab
Move backward
Enter
Follow a link, press a button, or open a menu
Space
Press a button, or scroll down the page
Escape
Close menus, the treatment planner, and the cookie notice
Arrow keys, Page Up, Page Down, Home, End
Scroll the page

Skip Links

Press Tab when a page first loads to show links that jump to:

  • Skip to main content: the page content, past the menu
  • Skip to navigation: the main menu
  • Skip to contact information: our phone, email and address in the footer

Screen Reader Tips

  • Regions: Jump between the header, navigation, main content and footer with your screen reader’s landmark keys.
  • Headings: Move by heading to scan a page. Headings follow in order on every page.
  • Forms: Every field has a label, and errors are read out and linked to the field.
  • Images: Meaningful images have alternative text. Decorative images are skipped.
  • Links: Links that open a new tab say so.

Feedback and Help

If you have trouble using any part of this website, or need information in another format, please contact us. Tell us the page and the problem, and we will help you get the information or service another way.

Phone

Speak with our office:

(714) 978-2445

Email

Send feedback or report a problem:

krystle.cummins@finesseps.com

Response commitment

We aim to respond within two business days, and to fix the problem or tell you when it will be fixed.

Formal Complaints

To file a formal accessibility complaint, contact us by phone or email and include:

  • Your name and how to reach you
  • The page or feature where you had trouble
  • What happened, and how it affected you
  • The assistive technology you were using, if any

Technical Specifications

This website relies on HTML, CSS, WAI-ARIA and JavaScript. It is designed to work with:

Desktop browsers
Current versions of Chrome, Safari, Firefox and Edge
Mobile browsers
Safari on iOS, Chrome on Android
Operating systems
Windows, macOS, iOS, Android
Requirements
JavaScript turned on is recommended

About This Statement

Document information

Last updated:
November 12, 2026
Last audit:
November 1, 2026
Fixes released:
November 11, 2026
Next review:
After major site changes, and at least once a year

Review history

  • November 2025: Baseline accessibility features
  • February 2, 2026: Privacy and consent review
  • February 13, 2026: Forms, dialogs and written process
  • February 14, 2026: Brand color contrast and first automated test run
  • November 1, 2026: Full-site WCAG 2.2 AA audit
  • November 11, 2026: Fixes for the November 1 audit
  • November 12, 2026: Page structure and keyboard navigation with smooth scrolling

We update this statement after each audit and after significant accessibility fixes. Records of our testing and fixes are kept and are available on request.

Exclusively focused. Exceptionally refined.