No automated violations found on this page for the selected standard. Human review still recommended.
Contrast axe couldn't grade: measured (4)
axe set aside 4 color-contrast checks on this page because it cannot read the pixels behind text sitting on an image, gradient, or overlay. We measured every one against the rendered page at desktop (1280×720) and mobile (390×844), worst case: 4 pass, 0 fail.
Keyboard and focus order (29 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.
The links list, as a screen reader user gets it 29 links, 26 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
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 Making websites since dial-up.
h2 WHAT I TAKE ON
h3 Small organizations
h3 Accessibility-serious work
h3 Hand-built WordPress
h3 Long-term care
h2 SITE HEALTH SCAN
h3 A free first read on your site.
h2 Selected work
h2 FROM THE WORKBENCH
h2 VENTURES
h3 Things I’ve made when I should have been resting.
h2 Working on something?
h3 Off the page builder, measurably faster.
h3 Accessible, and still unmistakably Marigold.
h3 A newsroom that runs its own layout.
h3 One PHP bug, four servers, four different answers
h3 Do Your Part: four free ways to check a website for accessibility
h3 I assumed Google’s booking page was accessible
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)
AI-assisted findings (needs human confirmation)
These are judgment calls about link purpose and heading clarity that automated tools cannot make. A model flagged them; confirm before acting.
moderate Heading: A free first read on your site.AcceptedDeliberate: voice heading. The section topic is clear in context.
This element is marked up as a heading but reads as a tagline or subtitle for the 'Site Health Scan' section rather than a heading that describes the section's content. A reader scanning headings alone would not learn what the section covers; that information is supplied by the parent heading 'Site Health Scan'. As a standalone heading it adds no descriptive value beyond what the parent already says.
Suggested: Consider removing this as a heading and presenting it as body text beneath the 'Site Health Scan' heading, or rewrite it as a heading that describes what the scan does or finds, for example: 'What the Site Health Scan checks'.
moderate Heading: Things I've made when I should have been resting.AcceptedDeliberate: voice heading. The section topic is clear in context.
This heading introduces the Ventures section but describes the author's personal circumstance rather than the content of the section. A reader scanning headings cannot determine what types of ventures, products, or projects are covered. The context needed to interpret it comes entirely from the parent 'Ventures' heading.
Suggested: Remove this as a heading and treat it as body text, or rewrite it to describe the section content, for example: 'Side projects and independent products'.
