No automated violations found on this page for the selected standard. Manual review still recommended.
Contrast axe couldn't grade: measured (3)
axe set aside 3 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: 3 pass, 0 fail.
Keyboard and focus order (23 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 23 links, 20 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 Worked examples
h2 Working on something?
h2 Off the page builder, measurably faster.
h2 The whole menu, legible to everyone.
h2 A newsroom that runs its own newsletter.
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.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.
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.
The h1 'Worked examples' does not identify the specific type of content on the page. A visitor arriving via search or a screen-reader landmark list would not know these are case studies, which is the defined content category of the page.
Suggested: Case Studies
minor Page title: Case Studies Archive - bekee gibson
The word 'Archive' is a WordPress default taxonomy label that adds no meaning for users. The title adequately identifies the site and section, but 'Archive' is generic filler that does not describe the page's purpose any more precisely than 'Case Studies' alone does.
