/

0
critical
0
serious
2
moderate
0
minor
41
checks passed
No automated violations found on this page for the selected standard. Manual 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.

LinksAll announce as
3bekee gibson
2Say 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

What this looks like on the page
The page with every keyboard stop numbered in the order focus visits it. Red badges mark stops that are invisible when focused, have no accessible name, or show no focus indicator.
Every keyboard stop, numbered in the order focus actually visits it. Red marks a stop that is itself a problem.
The same page with its layout preserved but its content replaced by what a screen reader announces. Hatched areas carry no information for a screen reader user.
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.

moderate Heading: Making websites since dial-up.AcceptedIntentional brand voice; homepage hero.

SC 2.4.6 (AA) AI-assisted

This h1 reads as a tagline or marketing slogan rather than a description of the page or site. A visitor who relies on headings to orient themselves cannot tell what the site offers or who it belongs to from this heading alone.

Suggested: Bekee Gibson: Accessibility-Serious WordPress Development in Madison, WI

moderate Heading: Things I've made when I should have been resting.

SC 2.4.6 (AA) AI-assisted

This h3 is the sole heading for the Ventures section body. It is a witty descriptor but does not describe what kind of content or projects follow. A user scanning headings would not understand what 'Ventures' contains from this heading.

Suggested: Side projects and independent products