vital-scans open quality ledger

www.cdc.gov: technology ↔ issues

Accessibility findings that appear disproportionately on pages running a given technology, across the 299 page(s) in 2026-W39 where both technology detection and an accessibility engine ran. Lift is how many times more likely a finding is on pages with the technology than on pages overall — a value of 2× means twice the baseline rate.

This is an association, not proof of cause. Technologies that are detected on the same set of pages (e.g. a CMS, its host, and its language) will share identical lift values; the listing groups by technology but cannot tell which one in a co-located stack is responsible. Treat high-lift pairs as leads for a human to confirm — a barrier that recurs with the same technology, especially across multiple sites, is likely a bug in that technology rather than in any one page's content.

Moment.js 14 pages

Findings over-represented on pages running Moment.js (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe) 21.36× 14 / 14 14
Form field has accessible name (alfa) 21.36× 6 / 14 6
Form field label is visible (alfa) 9.86× 6 / 14 13
Text has minimum contrast ratio of 4.5:1 (alfa) 4.00× 6 / 14 32
Each page should have exactly one <main> landmark. (axe) 3.83× 14 / 14 78
Target size is at least 24×24 CSS pixels or has spacing (Minimum) (alfa) 3.77× 6 / 14 34
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe) 2.77× 7 / 14 54
Text has enhanced contrast (alfa) 1.80× 6 / 14 71
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.54× 6 / 14 83

DreamWeaver 19 pages

Findings over-represented on pages running DreamWeaver (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe) 15.74× 14 / 19 14
Form field has accessible name (alfa) 15.74× 6 / 19 6
Form field label is visible (alfa) 9.68× 8 / 19 13
Text has minimum contrast ratio of 4.5:1 (alfa) 3.93× 8 / 19 32
Each page should have exactly one <main> landmark. (axe) 3.83× 19 / 19 78
Target size is at least 24×24 CSS pixels or has spacing (Minimum) (alfa) 3.70× 8 / 19 34
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe) 3.50× 12 / 19 54
No obsolete or deprecated elements are used (alfa) 3.42× 5 / 19 23
Link is distinguishable without relying on color (alfa) 1.92× 5 / 19 41
Text has enhanced contrast (alfa) 1.77× 8 / 19 71
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.52× 8 / 19 83

D3 20 pages

Findings over-represented on pages running D3 (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 2.90× 19 / 20 98

Bootstrap 222 pages

Findings over-represented on pages running Bootstrap (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
When a landmark role/type repeats (e.g (axe) 1.35× 100 / 222 100
Scrolling content can be accessed by keyboard (alfa) 1.35× 57 / 222 57
aria attribute is permitted for element role (alfa) 1.35× 38 / 222 38
Text has sufficient color contrast (Enhanced) (alfa) 1.35× 25 / 222 25
Remove or change the ARIA role — it isn't allowed on this element type. (axe) 1.35× 18 / 222 18
Ensure the skip link targets a real, focusable element (its href must match an existing id). (axe) 1.35× 12 / 222 12
landmark-contentinfo-is-top-level (axe) 1.35× 11 / 222 11
Use only one banner landmark (<header> at the top level) per page. (axe) 1.35× 11 / 222 11
Use only one contentinfo landmark (<footer> at the top level) per page. (axe) 1.35× 11 / 222 11
Avoid tabindex values greater than 0; they create a confusing tab order. (axe) 1.35× 11 / 222 11
Accessible name of link or button matches visible label (alfa) 1.35× 7 / 222 7
link-in-text-block (axe) 1.35× 7 / 222 7
page-has-heading-one (axe) 1.17× 13 / 222 15

jQuery 240 pages

Findings over-represented on pages running jQuery (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
When a landmark role/type repeats (e.g (axe) 1.25× 100 / 240 100
aria attribute is permitted for element role (alfa) 1.25× 38 / 240 38
Remove or change the ARIA role — it isn't allowed on this element type. (axe) 1.25× 18 / 240 18
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe) 1.25× 14 / 240 14
Form field label is visible (alfa) 1.25× 13 / 240 13
landmark-contentinfo-is-top-level (axe) 1.25× 11 / 240 11
Use only one banner landmark (<header> at the top level) per page. (axe) 1.25× 11 / 240 11
Use only one contentinfo landmark (<footer> at the top level) per page. (axe) 1.25× 11 / 240 11
Avoid tabindex values greater than 0; they create a confusing tab order. (axe) 1.25× 11 / 240 11
Accessible name of link or button matches visible label (alfa) 1.25× 7 / 240 7
link-in-text-block (axe) 1.25× 7 / 240 7
Form field has accessible name (alfa) 1.25× 6 / 240 6
Scrolling content can be accessed by keyboard (alfa) 1.22× 56 / 240 57
Text has sufficient color contrast (Enhanced) (alfa) 1.20× 24 / 240 25
Ensure the skip link targets a real, focusable element (its href must match an existing id). (axe) 1.14× 11 / 240 12
Text has enhanced contrast (alfa) 1.12× 64 / 240 71