www.cdc.gov: technology ↔ issues
Accessibility findings that appear disproportionately on pages running a given technology, across the 180 page(s) in 2026-W35 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 16 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)
11.25×
16 / 16
16
Each page should have exactly one <main> landmark. (axe)
3.46×
16 / 16
52
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
2.65×
8 / 16
34
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
16 / 16
179
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)
9.47×
16 / 19
16
Each page should have exactly one <main> landmark. (axe)
3.46×
19 / 19
52
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
3.07×
11 / 19
34
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
19 / 19
179
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)
3.16×
14 / 14
57
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
14 / 14
179
Bootstrap 128 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×
51 / 128
51
Scrolling content can be accessed by keyboard (alfa)
1.41×
35 / 128
35
Text has sufficient color contrast (Enhanced) (alfa)
1.41×
13 / 128
13
Remove or change the ARIA role — it isn't allowed on this element type. (axe)
1.41×
7 / 128
7
aria attribute is permitted for element role (alfa)
1.34×
20 / 128
21
Presentational children of an element are not focusable (alfa)
1.23×
7 / 128
8
Text has enhanced contrast (alfa)
1.17×
35 / 128
42
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
128 / 128
179
jQuery 147 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.22×
51 / 147
51
Scrolling content can be accessed by keyboard (alfa)
1.22×
35 / 147
35
aria attribute is permitted for element role (alfa)
1.22×
21 / 147
21
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe)
1.22×
16 / 147
16
Text has sufficient color contrast (Enhanced) (alfa)
1.22×
13 / 147
13
Presentational children of an element are not focusable (alfa)
1.22×
8 / 147
8
Remove or change the ARIA role — it isn't allowed on this element type. (axe)
1.22×
7 / 147
7
Text has enhanced contrast (alfa)
1.11×
38 / 147
42
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.01×
147 / 147
179
Google Analytics 180 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×
179 / 180
179
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
57 / 180
57
Each page should have exactly one <main> landmark. (axe)
1.00×
52 / 180
52
When a landmark role/type repeats (e.g (axe)
1.00×
51 / 180
51
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
50 / 180
50
Text has enhanced contrast (alfa)
1.00×
42 / 180
42
Azure Front Door 180 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×
179 / 180
179
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
57 / 180
57
Each page should have exactly one <main> landmark. (axe)
1.00×
52 / 180
52
When a landmark role/type repeats (e.g (axe)
1.00×
51 / 180
51
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
50 / 180
50
Text has enhanced contrast (alfa)
1.00×
42 / 180
42
Azure 180 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×
179 / 180
179
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
57 / 180
57
Each page should have exactly one <main> landmark. (axe)
1.00×
52 / 180
52
When a landmark role/type repeats (e.g (axe)
1.00×
51 / 180
51
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
50 / 180
50
Text has enhanced contrast (alfa)
1.00×
42 / 180
42
HSTS 180 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×
179 / 180
179
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
57 / 180
57
Each page should have exactly one <main> landmark. (axe)
1.00×
52 / 180
52
When a landmark role/type repeats (e.g (axe)
1.00×
51 / 180
51
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
50 / 180
50