Accessibility audit · bekee.com
gibson•works

/services/

https://bekee.com/services/
0
critical
0
serious
0
moderate
0
minor
45
checks passed
No automated violations found on this page for the selected standard. Human review still recommended.

Needs human review (1)

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

Color use (SC 1.4.1)

1 link trailed by stranded punctuation Human review

A screen reader chunks a block by its elements, so a text node left alone after a link becomes its own stop. Where that text node is nothing but a period, the listener swipes, hears “period,” and swipes again to reach the next real thing. Read each one and decide whether it is worth an edit: moving the punctuation inside the link removes the stop, and so does rewriting the sentence so the link is not last. This is craft rather than conformance; it maps to no success criterion, and nothing here is a failure.

What we found: “Good Standing” then “.”.

Keyboard and focus order (53 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.

Focus jumps back up the page

for review · SC 2.4.3 · SC 1.3.2

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 16 to 17: moves up 192px, from "Remediation" to "Site builds and redesigns"
The links list, as a screen reader user gets it 30 links, 25 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
3Send a note
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)