Accessibility audit · bekee.com
gibson•works

/scan/next-steps/

https://bekee.com/scan/next-steps/
0
critical
0
serious
4
moderate
0
minor
42
checks passed
No automated violations found on this page for the selected standard. Manual review still recommended.

Needs manual 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 form on this page Manual review

SC 1.4.1 (A)

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, 23 fields total, 2 marked required.

Keyboard and focus order (32 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.
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: Would you rather hand it off?

SC 2.4.6 (AA) AI-assisted

The sole h1 on the page is phrased as a question that presupposes context the visitor may not have. On its own it does not identify the page's topic or purpose (a contact/next-steps form for hiring a web professional). A user navigating by headings gets no clear sense of what the page is about or what action they can take.

Suggested: Give the heading a clearer subject, for example: 'Get in touch: next steps for working with bekee gibson' or 'Ready to work together? Tell me about your project'.

moderate Form label: Yes

SC 3.3.2 (A) AI-assisted

The radio button labelled 'Yes' (and its siblings 'No' and 'Not sure') lack sufficient context in their labels alone. Without knowing the question these radios answer, a screen-reader user navigating directly to the field hears only 'Yes', 'No', or 'Not sure' with no indication of what is being asked. The group needs a visible and programmatic group label (e.g. a <legend> or aria-labelledby pointing to the question text).

Suggested: Wrap the radio group in a <fieldset> with a <legend> that states the question, for example: '<legend>Do you have an existing site?</legend>' so that each option is announced as 'Do you have an existing site? Yes / No / Not sure'.

moderate Form label: No rush

SC 3.3.2 (A) AI-assisted

The radio buttons labelled 'No rush', 'Within a month', and 'It's urgent' form a timeline group with no programmatic group label. A screen-reader user navigating to these controls hears only the option value with no indication that the question is about timeline or urgency.

Suggested: Wrap these radios in a <fieldset> with a <legend> such as 'How soon do you need this done?' so each option is announced in full context.

moderate Form label: Ready to invest in fixing it

SC 3.3.2 (A) AI-assisted

The radio buttons labelled 'Ready to invest in fixing it' and 'Still exploring' form a budget-or-commitment group with no programmatic group label. Without a group label, a screen-reader user cannot tell what question these options are answering.

Suggested: Wrap these radios in a <fieldset> with a <legend> that states the question, for example: 'Where are you in the decision process?' or 'What best describes your situation?'.