Platform standard
Accessibility statement
How this reference is built for accessibility, what is not yet guaranteed, what it does not cover, and how to report a barrier.
This site is built toward the Web Content Accessibility Guidelines 2.1 at Level AA, and uses no accessibility overlay, toolbar or widget. Every decision tool is operable from the keyboard alone, every input carries a real label, and every result is announced to a screen reader when it changes instead of appearing silently on screen. Treatment comparisons and estimate breakdowns are real HTML tables with header cells associated to their columns, never images of tables. A screen reader can read a comparison cell by cell. Two limitations are stated plainly instead of glossed: a side-by-side comparison is harder to navigate linearly than prose however well it is marked up, and the provider-introduction form uses a third-party anti-abuse challenge that some people cannot complete: the email route below reaches the same place. Accessibility reports are handled through the same route as factual corrections, because a page nobody can read is a defect in the same sense that a wrong fact is.
What this site is built toward
Building toward WCAG 2.1 Level AA means a clear heading structure on every page, text that meets contrast requirements against its background, controls that can be reached and operated with a keyboard alone, links whose purpose is clear from their own wording, form fields with real labels, meaningful alternative text on images that carry information, and respect for a reduced-motion preference set in your operating system. These are commitments about how the site is built. They are not a legal guarantee that every page meets every criterion at every moment.
The decision tools are operable without a mouse
Every calculator input is a real labelled form field reachable by Tab, and every result updates in a region a screen reader announces, not changing silently. Nothing requires a drag, a hover or a pointer gesture, no tool imposes a time limit, and numeric fields accept typed values so a stepper is never the only way to reach a number. Because the tools run entirely in your browser, nothing about using an assistive technology changes what they compute or what they store.
Comparisons are tables, not pictures of tables
Every treatment comparison, estimate breakdown and insurance worked example is real text in a real HTML table with header cells associated to their columns, so a screen reader announces which value belongs to which heading instead of reading a wall of terms. Wide tables scroll inside their own container, which means the page itself never scrolls sideways and no column is cut off at high zoom. No comparison on this site is published as an image.
No accessibility overlay
The site does not use an accessibility overlay, toolbar or widget. Overlays are marketed as an instant fix and are widely reported by disabled users and by assistive-technology vendors to interfere with the screen readers, magnifiers and browser settings people have already configured. Building the underlying pages correctly is the approach taken here instead. If you use a screen reader, magnifier, voice control or any other assistive technology, this site is intended to work with the tools you already have set up.
Known limitations
Two are worth naming specifically instead of leaving to a general disclaimer. Both are real and both have a workaround.
- Side-by-side comparison tables carry two dimensions at once, which is harder to navigate with a screen reader than linear prose however well the table is marked up. The same information appears in the prose beside every comparison. The underlying figures can be sent as a plain list on request.
- The optional provider-introduction form uses a third-party anti-abuse challenge. If that challenge is difficult or impossible for you to complete, use the editorial contact address instead and the request will be handled the same way.
- Pages link to documents published by dental associations, insurers and government agencies. Those documents are outside this site's control and may not meet the same standard.
What automated checking cannot tell us
Automated checks find common problems but cannot judge whether a page is genuinely usable. A record can pass every mechanical check and still be impossible to work through with a screen reader, because the failure is in the order things are announced, not in the markup. Feedback from real use is the part that cannot be generated automatically, and it is treated here with the same seriousness as a reported factual error.
Reporting a barrier
If any page, tool, table, control or form on this site is difficult or impossible to use, write to the editorial contact address and begin the message with the word “Accessibility”. Include the page address and what happened: what you were trying to do, what your assistive technology did, and what you expected instead. Specific detail like that is what makes a report actionable. Reports are acknowledged within five business days with either a timeframe for a fix or another way to get the same information. Please do not include symptoms, diagnoses, medications or insurance identifiers in an accessibility report; none of that is needed to fix a page.
What this statement does not cover
This statement covers this website. It does not cover the websites, offices, printed treatment plans or communications of any dental practice introduced through the optional form. Each of those is a separate business responsible for its own accessibility, and physical access to a practice is a question worth asking that practice directly before an appointment is booked.
How this statement is maintained
Accessibility is reviewed whenever the shared record templates or a primary interaction change, instead of on a fixed calendar. A template change is what actually moves accessibility across every record at once. This statement was last reviewed on September 5, 2026. It will be revised when the site's structure changes materially, or when a reported barrier changes what can honestly be claimed here.