vital-scans open quality ledger

www.cdc.gov: technology ↔ issues

Accessibility findings that appear disproportionately on pages running a given technology, across the 176 page(s) in 2026-W40 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 7 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) 25.14× 7 / 7 7
Each page should have exactly one <main> landmark. (axe) 4.51× 7 / 7 39

DreamWeaver 8 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) 22.00× 7 / 8 7
Each page should have exactly one <main> landmark. (axe) 4.51× 8 / 8 39
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe) 4.40× 5 / 8 25

YouTube 10 pages

Findings over-represented on pages running YouTube (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Give every <iframe> a descriptive title attribute. (axe) 17.60× 5 / 10 5
When a landmark role/type repeats (e.g (axe) 1.58× 6 / 10 67

D3 14 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.38× 11 / 14 58

Bootstrap 137 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.28× 67 / 137 67
Scrolling content can be accessed by keyboard (alfa) 1.28× 37 / 137 37
aria attribute is permitted for element role (alfa) 1.28× 26 / 137 26
Text has sufficient color contrast (Enhanced) (alfa) 1.28× 20 / 137 20
page-has-heading-one (axe) 1.28× 12 / 137 12
landmark-contentinfo-is-top-level (axe) 1.28× 10 / 137 10
Use only one banner landmark (<header> at the top level) per page. (axe) 1.28× 10 / 137 10
Use only one contentinfo landmark (<footer> at the top level) per page. (axe) 1.28× 10 / 137 10
Ensure the skip link targets a real, focusable element (its href must match an existing id). (axe) 1.28× 10 / 137 10
Avoid tabindex values greater than 0; they create a confusing tab order. (axe) 1.28× 10 / 137 10
Give every <iframe> a descriptive title attribute. (axe) 1.28× 5 / 137 5
Text has enhanced contrast (alfa) 1.13× 37 / 137 42
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.08× 37 / 137 44
link-in-text-block (axe) 1.07× 5 / 137 6
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 137 / 137 176

jQuery 145 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.21× 67 / 145 67
Scrolling content can be accessed by keyboard (alfa) 1.21× 37 / 145 37
aria attribute is permitted for element role (alfa) 1.21× 26 / 145 26
Text has sufficient color contrast (Enhanced) (alfa) 1.21× 20 / 145 20
page-has-heading-one (axe) 1.21× 12 / 145 12
landmark-contentinfo-is-top-level (axe) 1.21× 10 / 145 10
Use only one banner landmark (<header> at the top level) per page. (axe) 1.21× 10 / 145 10
Use only one contentinfo landmark (<footer> at the top level) per page. (axe) 1.21× 10 / 145 10
Ensure the skip link targets a real, focusable element (its href must match an existing id). (axe) 1.21× 10 / 145 10
Avoid tabindex values greater than 0; they create a confusing tab order. (axe) 1.21× 10 / 145 10
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe) 1.21× 7 / 145 7
Form field label is visible (alfa) 1.21× 6 / 145 6
link-in-text-block (axe) 1.21× 6 / 145 6
Table header has scope (alfa) 1.21× 5 / 145 5
Presentational children of an element are not focusable (alfa) 1.21× 5 / 145 5
Give every <iframe> a descriptive title attribute. (axe) 1.21× 5 / 145 5
Text has enhanced contrast (alfa) 1.13× 39 / 145 42
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.08× 39 / 145 44
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 145 / 145 176

Google Analytics 176 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× 176 / 176 176
When a landmark role/type repeats (e.g (axe) 1.00× 67 / 176 67

Azure Front Door 176 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× 176 / 176 176
When a landmark role/type repeats (e.g (axe) 1.00× 67 / 176 67

Azure 176 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× 176 / 176 176
When a landmark role/type repeats (e.g (axe) 1.00× 67 / 176 67

HSTS 176 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× 176 / 176 176
When a landmark role/type repeats (e.g (axe) 1.00× 67 / 176 67