No automated violations found on this page for the selected standard. Manual review still recommended.
Keyboard and focus order (50 stops)
This is the only lane that drives the page instead of reading it: we pressed Tab and recorded where focus actually landed, until it wrapped. Roles and names come from Chrome's own accessibility tree, the same computation it hands a screen reader. A keyboard user passes 10 stops before reaching main content, and the page has a working skip link.
Nothing in this lane is a failure. The keyboard order was walked end to end and the deterministic checks came back clean.
Surfaced for review, no verdict rendered 1 item
These are not failures. A focus order that jumps around, or a third-party widget that dominates the keyboard journey, can be perfectly defensible; whether it is depends on meaning and operability, which is a human call. The evidence is here so that call can be made without re-tabbing the page by hand.
Keyboard focus moves upward on the page at 1 point(s) in the sequence, from 1 distinct cause(s). That is not automatically wrong, since markup order and visual order can legitimately differ, but it is where a confusing tab order shows up and it needs a human decision.
Suggested: Tab the page yourself at each transition below and ask whether the jump still makes sense to someone who cannot see the layout. If it does not, reorder the markup rather than adding tabindex.
Stop 15 to 16: moves up 153px, from "The Whole Picture" to "Remediation"
The links list, as a screen reader user gets it 29 links, 24 distinct names
Screen reader users navigate by pulling up every link on the page at once (Insert+F7 in NVDA and JAWS), stripped of the layout that surrounds them. This is that list. Read in place a link can borrow meaning from the heading above it; read here it has only its own name.
Links
All announce as
3
bekee gibson
3
Send a note
2
Say hello: contact page
Names appearing more than once, most repeated first. A repeated name is not automatically wrong: a "Home" link in the header and the footer is fine. It matters when the destinations differ and the name does not.
Heading outline, as announced
h1 Small Madison businesses should be able to take their website for granted.
h2 WHAT I TAKE ON
h3 Start with a diagnostic
h3 Build, move, or sell
h3 Stick around
h2 How I work
h3 The Usability Triangle
h3 The Self-Sufficient Site
h2 Common questions
h2 Accessibility audits and ADA compliance
h2 Working on something?
h3 How much does a project cost?
h3 What’s Site Triage?
h3 Do you offer ongoing support or retainers?
h3 Who can make my website ADA compliant in Madison?
h3 How much does a website accessibility audit cost?
h3 Do you audit every page on the site?
h3 What does an accessibility audit find that a free scanner doesn’t?
h3 My WordPress site failed an accessibility scan. Who can fix it?
h3 Accessibility overlay or a real audit: which do I need?
h3 I got an ADA demand letter about my website. What do I do?
h3 Our city website has to meet the ADA Title II deadline. Who can audit it?
h4 Site Triage
h4 Accessibility audit
h4 Technical SEO audit
h4 GEO/SEO ranking audit
h4 The Whole Picture
h4 Remediation
h4 Site builds and redesigns
h4 Migrations and rescues
h4 WooCommerce
h4 Ongoing support
What this looks like on the pageEvery keyboard stop, numbered in the order focus actually visits it. Red marks a stop that is itself a problem. Open full size (new tab)The same layout, showing what is announced instead of what is rendered. Hatched areas carry nothing for a screen reader user: background images, decorative graphics, and media with no text alternative. Interactive elements show the name Chrome computed; everything else is an illustrative approximation, not a finding. Open full size (new tab)
