www.cdc.gov: technology ↔ issues
Accessibility findings that appear disproportionately on pages running a given technology, across the 288 page(s) in 2026-W37 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 6 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)
48.00×
6 / 6
6
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
5.33×
6 / 6
54
Each page should have exactly one <main> landmark. (axe)
3.79×
6 / 6
76
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)
36.00×
6 / 8
6
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
5.33×
8 / 8
54
Each page should have exactly one <main> landmark. (axe)
3.79×
8 / 8
76
D3 18 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.64×
15 / 18
91
YouTube 14 pages
Findings over-represented on pages running YouTube (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria attribute is permitted for element role (alfa)
2.45×
5 / 14
42
When a landmark role/type repeats (e.g (axe)
2.20×
9 / 14
84
Scrolling content can be accessed by keyboard (alfa)
1.66×
5 / 14
62
Text has enhanced contrast (alfa)
1.43×
5 / 14
72
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.20×
5 / 14
86
Bootstrap 211 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.36×
84 / 211
84
aria attribute is permitted for element role (alfa)
1.36×
42 / 211
42
Remove or change the ARIA role — it isn't allowed on this element type. (axe)
1.36×
14 / 211
14
Presentational children of an element are not focusable (alfa)
1.36×
9 / 211
9
Make scrollable regions keyboard-focusable (tabindex="0") so keyboard users can scroll them. (axe)
1.36×
5 / 211
5
Accessible name of link or button matches visible label (alfa)
1.36×
5 / 211
5
Element has required aria-owns (alfa)
1.36×
5 / 211
5
Scrolling content can be accessed by keyboard (alfa)
1.34×
61 / 211
62
Text has sufficient color contrast (Enhanced) (alfa)
1.32×
27 / 211
28
page-has-heading-one (axe)
1.24×
10 / 211
11
link-in-text-block (axe)
1.21×
8 / 211
9
Text has enhanced contrast (alfa)
1.16×
61 / 211
72
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
211 / 211
288
jQuery 219 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.32×
84 / 219
84
aria attribute is permitted for element role (alfa)
1.32×
42 / 219
42
Remove or change the ARIA role — it isn't allowed on this element type. (axe)
1.32×
14 / 219
14
link-in-text-block (axe)
1.32×
9 / 219
9
Presentational children of an element are not focusable (alfa)
1.32×
9 / 219
9
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe)
1.32×
6 / 219
6
Form field label is visible (alfa)
1.32×
6 / 219
6
Make scrollable regions keyboard-focusable (tabindex="0") so keyboard users can scroll them. (axe)
1.32×
5 / 219
5
Accessible name of link or button matches visible label (alfa)
1.32×
5 / 219
5
Element has required aria-owns (alfa)
1.32×
5 / 219
5
Scrolling content can be accessed by keyboard (alfa)
1.29×
61 / 219
62
Text has sufficient color contrast (Enhanced) (alfa)
1.27×
27 / 219
28
page-has-heading-one (axe)
1.20×
10 / 219
11
Text has enhanced contrast (alfa)
1.17×
64 / 219
72
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
219 / 219
288
Google Analytics 288 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×
288 / 288
288
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
91 / 288
91
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
86 / 288
86
Azure Front Door 288 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×
288 / 288
288
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
91 / 288
91
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
86 / 288
86
Azure 288 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×
288 / 288
288
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
91 / 288
91
HSTS 288 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×
288 / 288
288
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
91 / 288
91