/notes/do-your-part-talk/

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

Contrast axe couldn't grade: measured (98)

axe set aside 98 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: 98 pass, 0 fail.

Needs human review (3)

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

Color use (SC 1.4.1)

2 links 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: “Do Your Part slides (PDF, 18 pages, 4.9 MB)” then “.”; “Run the free scan” then “.”.

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: Text newly overlapping at 320px: “I edited the recording. Where I got a fact wrong i” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(5), drawn over “So this is Do Your Part. After I sent it, I though” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(1)); “So this is Do Your Part. After I sent it, I though” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(1), drawn over “The slides are here: .” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(6)); “So this is Do Your Part. After I sent it, I though” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(1), drawn over “Do Your Part slides (PDF, 18 pages, 4.9 MB)” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(6) > a); “After the talk” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > h2.wp-block-heading:nth-of-type(2), drawn over “So I just told you a little bit of this, but there” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(2)); “So I just told you a little bit of this, but there” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(2), drawn over “A few more questions came in after I wrapped up. W” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(7)); and 29 more.

Text damaged when text alone is doubled in size Human review

The scan doubled every font size on the page, the way text-only zoom does, while leaving widths and heights alone, and this text was cut off or drawn over other text as a result when it was not at normal size. That is the named failure for SC 1.4.4 (text in a container sized in pixels). It is surfaced rather than failed because browser page zoom usually satisfies the criterion on its own: zoom the page to 200 percent and confirm whether the same text survives. If it survives page zoom, the criterion is met and these are worth fixing for readers who enlarge text only.

What we found: 36 overlapping: “I edited the recording. Where I got a fact wrong i” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(5), drawn over “So this is Do Your Part. After I sent it, I though” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(1)); “So I just told you a little bit of this, but there” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(2), drawn over “Do Your Part slides (PDF, 18 pages, 4.9 MB)” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(6) > a); “After the talk” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > h2.wp-block-heading:nth-of-type(2), drawn over “So I just told you a little bit of this, but there” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(2)); “So I just told you a little bit of this, but there” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(2), drawn over “A few more questions came in after I wrapped up. W” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(7)); “Are Lighthouse’s accessibility results comparable ” at main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > p.wp-block-paragraph:nth-of-type(8) > strong, drawn over “So I just told you a little bit of this, but there” (main#wp--skip-link--target > div.wp-block-group > div.entry-content:nth-of-type(2) > div.bekee-transcript > p:nth-of-type(2)); and 31 more.

Keyboard and focus order (26 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 21 links, 18 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)