www.cdc.gov: technology ↔ issues
Accessibility findings that appear disproportionately on pages running a given technology, across the 293 page(s) in 2026-W36 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)
20.93×
14 / 14
14
Each page should have exactly one <main> landmark. (axe)
3.49×
14 / 14
84
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
3.04×
8 / 14
55
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
14 / 14
291
DreamWeaver 18 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)
16.28×
14 / 18
14
Each page should have exactly one <main> landmark. (axe)
3.29×
17 / 18
84
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
3.26×
11 / 18
55
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
18 / 18
291
D3 25 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×
24 / 25
100
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
25 / 25
291
Facebook Pixel 6 pages
Findings over-represented on pages running Facebook Pixel (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.44×
5 / 6
100
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
6 / 6
291
Google Tag Manager 7 pages
Findings over-represented on pages running Google Tag Manager (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.09×
5 / 7
100
Bootstrap 208 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.41×
66 / 208
66
Scrolling content can be accessed by keyboard (alfa)
1.41×
39 / 208
39
aria attribute is permitted for element role (alfa)
1.41×
26 / 208
26
Remove or change the ARIA role — it isn't allowed on this element type. (axe)
1.41×
19 / 208
19
Text has sufficient color contrast (Enhanced) (alfa)
1.41×
12 / 208
12
Accessible name of link or button matches visible label (alfa)
1.41×
8 / 208
8
Associate data cells with their headers correctly using headers/id or scope. (axe)
1.41×
6 / 208
6
Text has enhanced contrast (alfa)
1.19×
39 / 208
46
page-has-heading-one (axe)
1.17×
10 / 208
12
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
207 / 208
291
jQuery 225 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.30×
66 / 225
66
Scrolling content can be accessed by keyboard (alfa)
1.30×
39 / 225
39
aria attribute is permitted for element role (alfa)
1.30×
26 / 225
26
Remove or change the ARIA role — it isn't allowed on this element type. (axe)
1.30×
19 / 225
19
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe)
1.30×
14 / 225
14
Text has sufficient color contrast (Enhanced) (alfa)
1.30×
12 / 225
12
Accessible name of link or button matches visible label (alfa)
1.30×
8 / 225
8
Associate data cells with their headers correctly using headers/id or scope. (axe)
1.30×
6 / 225
6
Form field label is visible (alfa)
1.30×
6 / 225
6
link-in-text-block (axe)
1.30×
6 / 225
6
Presentational children of an element are not focusable (alfa)
1.30×
5 / 225
5
Text has enhanced contrast (alfa)
1.19×
42 / 225
46
page-has-heading-one (axe)
1.09×
10 / 225
12
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
224 / 225
291
YouTube 5 pages
Findings over-represented on pages running YouTube (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.01×
5 / 5
291
Google Analytics 293 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×
291 / 293
291
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
100 / 293
100
Each page should have exactly one <main> landmark. (axe)
1.00×
84 / 293
84
Azure Front Door 293 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×
291 / 293
291
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
100 / 293
100
Each page should have exactly one <main> landmark. (axe)
1.00×
84 / 293
84
Azure 293 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×
291 / 293
291
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
100 / 293
100
Each page should have exactly one <main> landmark. (axe)
1.00×
84 / 293
84
HSTS 293 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×
291 / 293
291
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
100 / 293
100
Each page should have exactly one <main> landmark. (axe)
1.00×
84 / 293
84