/scan/

0
critical
0
serious
0
moderate
0
minor
43
checks passed
No automated violations found on this page for the selected standard. Human review still recommended.

Needs human review (2)

Some checks cannot be decided automatically; a human has to confirm these. No verdict is rendered here.

Color use (SC 1.4.1)

1 form on this page Human review

Submit the form with required fields left blank and confirm that required fields and any error states are indicated by more than color (asterisk, icon, label text, border thickness). Any color cue used must also meet contrast and must never be the only signal.

What we found: 1 form, 7 fields total, 2 marked required.

Reflow at 320 CSS pixels needs a look Human review

Set the window to 320 CSS pixels wide, or zoom a 1280 pixel window to 400 percent, and look at each item listed. Content that needs a two-dimensional layout to mean anything (a data table, a map, a diagram, video, code, a toolbar) is allowed to scroll sideways; ordinary text, forms, and navigation are not. Text reported as cut off or overlapping was measured against the same page at 1280 pixels, so only damage the narrow width introduced is listed. A carousel's peeking slide is excluded by design.

What we found: The page scrolls sideways to 348px, but no element or text was found past the edge, so the extra width comes from something the probe cannot name (a pseudo-element or a shadow root, for example); look at it at 320px.

Keyboard and focus order (13 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 15 links, 12 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. Open full size (new tab)
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. Open full size (new tab)