www.cdc.gov: technology ↔ issues
Accessibility findings that appear disproportionately on pages running a given technology, across the 169 page(s) in 2026-W27 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 6 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)
28.17×
6 / 6
6
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
4.83×
6 / 6
35
Each page should have exactly one <main> landmark. (axe)
4.23×
6 / 6
40
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)
28.17×
6 / 6
6
Increase the contrast between text and its background to at least 4.5:1 (3:1 for large text) (axe)
4.83×
6 / 6
35
Each page should have exactly one <main> landmark. (axe)
4.23×
6 / 6
40
D3 13 pages
Findings over-represented on pages running D3 (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
Headings are structured hierarchically (alfa)
2.60×
6 / 13
30
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
2.56×
12 / 13
61
Scrolling content can be accessed by keyboard (alfa)
1.22×
6 / 13
64
Text has enhanced contrast (alfa)
1.13×
6 / 13
69
Bootstrap 129 pages
Findings over-represented on pages running Bootstrap (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
Scrolling content can be accessed by keyboard (alfa)
1.31×
64 / 129
64
When a landmark role/type repeats (e.g (axe)
1.31×
59 / 129
59
aria attribute is permitted for element role (alfa)
1.31×
46 / 129
46
Text has sufficient color contrast (Enhanced) (alfa)
1.31×
31 / 129
31
Accessible name of link or button matches visible label (alfa)
1.31×
16 / 129
16
page-has-heading-one (axe)
1.31×
9 / 129
9
Presentational children of an element are not focusable (alfa)
1.31×
9 / 129
9
Table header has scope (alfa)
1.31×
6 / 129
6
Text has enhanced contrast (alfa)
1.22×
64 / 129
69
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
129 / 129
169
jQuery 135 pages
Findings over-represented on pages running jQuery (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
Scrolling content can be accessed by keyboard (alfa)
1.25×
64 / 135
64
When a landmark role/type repeats (e.g (axe)
1.25×
59 / 135
59
aria attribute is permitted for element role (alfa)
1.25×
46 / 135
46
Text has sufficient color contrast (Enhanced) (alfa)
1.25×
31 / 135
31
Accessible name of link or button matches visible label (alfa)
1.25×
16 / 135
16
page-has-heading-one (axe)
1.25×
9 / 135
9
Presentational children of an element are not focusable (alfa)
1.25×
9 / 135
9
Form field label is visible (alfa)
1.25×
8 / 135
8
Associate every form control with a <label> (via for/id) or an aria-label/aria-labelledby. (axe)
1.25×
6 / 135
6
Table header has scope (alfa)
1.25×
6 / 135
6
Text has enhanced contrast (alfa)
1.22×
67 / 135
69
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
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
85 / 169
85
Text has enhanced contrast (alfa)
1.00×
69 / 169
69
Scrolling content can be accessed by keyboard (alfa)
1.00×
64 / 169
64
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
61 / 169
61
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
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
85 / 169
85
Text has enhanced contrast (alfa)
1.00×
69 / 169
69
Scrolling content can be accessed by keyboard (alfa)
1.00×
64 / 169
64
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
61 / 169
61
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
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
85 / 169
85
Text has enhanced contrast (alfa)
1.00×
69 / 169
69
Scrolling content can be accessed by keyboard (alfa)
1.00×
64 / 169
64
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
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
85 / 169
85
Text has enhanced contrast (alfa)
1.00×
69 / 169
69
Scrolling content can be accessed by keyboard (alfa)
1.00×
64 / 169
64