vital-scans open quality ledger

www.cdc.gov: technology ↔ issues

Accessibility findings that appear disproportionately on pages running a given technology, across the 169 page(s) in 2026-W38 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.

DreamWeaver 14 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) 12.07× 14 / 14 14
Each page should have exactly one <main> landmark. (axe) 3.52× 14 / 14 48
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe) 3.20× 9 / 14 34

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) 12.07× 14 / 14 14
Each page should have exactly one <main> landmark. (axe) 3.52× 14 / 14 48
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe) 3.20× 9 / 14 34

D3 7 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.81× 5 / 7 43

YouTube 8 pages

Findings over-represented on pages running YouTube (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
When a landmark role/type repeats (e.g (axe) 2.25× 5 / 8 47

Bootstrap 121 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.40× 47 / 121 47
Scrolling content can be accessed by keyboard (alfa) 1.40× 34 / 121 34
aria attribute is permitted for element role (alfa) 1.40× 26 / 121 26
Text has sufficient color contrast (Enhanced) (alfa) 1.40× 16 / 121 16
Remove or change the ARIA role — it isn't allowed on this element type. (axe) 1.40× 11 / 121 11
Accessible name of link or button matches visible label (alfa) 1.40× 7 / 121 7
Presentational children of an element are not focusable (alfa) 1.40× 6 / 121 6
Text has enhanced contrast (alfa) 1.25× 34 / 121 38
link-in-text-block (axe) 1.20× 6 / 121 7
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.08× 34 / 121 44
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 121 / 121 169

jQuery 135 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× 47 / 135 47
Scrolling content can be accessed by keyboard (alfa) 1.25× 34 / 135 34
aria attribute is permitted for element role (alfa) 1.25× 26 / 135 26
Text has sufficient color contrast (Enhanced) (alfa) 1.25× 16 / 135 16
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe) 1.25× 14 / 135 14
Remove or change the ARIA role — it isn't allowed on this element type. (axe) 1.25× 11 / 135 11
link-in-text-block (axe) 1.25× 7 / 135 7
Accessible name of link or button matches visible label (alfa) 1.25× 7 / 135 7
Presentational children of an element are not focusable (alfa) 1.25× 6 / 135 6
Form field label is visible (alfa) 1.25× 5 / 135 5
Text has enhanced contrast (alfa) 1.22× 37 / 135 38
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.05× 37 / 135 44
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 135 / 135 169

Google Analytics 169 pages

Findings over-represented on pages running Google Analytics (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 169 / 169 169
Each page should have exactly one <main> landmark. (axe) 1.00× 48 / 169 48
When a landmark role/type repeats (e.g (axe) 1.00× 47 / 169 47
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.00× 44 / 169 44
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.00× 43 / 169 43

Azure Front Door 169 pages

Findings over-represented on pages running Azure Front Door (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 169 / 169 169
Each page should have exactly one <main> landmark. (axe) 1.00× 48 / 169 48
When a landmark role/type repeats (e.g (axe) 1.00× 47 / 169 47
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.00× 44 / 169 44
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.00× 43 / 169 43

Azure 169 pages

Findings over-represented on pages running Azure (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 169 / 169 169
Each page should have exactly one <main> landmark. (axe) 1.00× 48 / 169 48
When a landmark role/type repeats (e.g (axe) 1.00× 47 / 169 47
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.00× 44 / 169 44

HSTS 169 pages

Findings over-represented on pages running HSTS (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 169 / 169 169
Each page should have exactly one <main> landmark. (axe) 1.00× 48 / 169 48
When a landmark role/type repeats (e.g (axe) 1.00× 47 / 169 47
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.00× 44 / 169 44