www.medicare.gov: technology ↔ issues
Accessibility findings that appear disproportionately on pages running a given technology, across the 216 page(s) in 2026-W32 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.
Facebook Pixel 10 pages
Findings over-represented on pages running Facebook Pixel (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.19×
10 / 10
182
Drupal 187 pages
Findings over-represented on pages running Drupal (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.16×
39 / 187
39
Table header has scope (alfa)
1.16×
15 / 187
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.16×
8 / 187
8
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.15×
181 / 187
182
Scrolling content can be accessed by keyboard (alfa)
1.13×
39 / 187
40
Font Awesome 187 pages
Findings over-represented on pages running Font Awesome (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.16×
39 / 187
39
Table header has scope (alfa)
1.16×
15 / 187
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.16×
8 / 187
8
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.15×
181 / 187
182
Scrolling content can be accessed by keyboard (alfa)
1.13×
39 / 187
40
Acquia Cloud Platform 187 pages
Findings over-represented on pages running Acquia Cloud Platform (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.16×
39 / 187
39
Table header has scope (alfa)
1.16×
15 / 187
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.16×
8 / 187
8
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.15×
181 / 187
182
Scrolling content can be accessed by keyboard (alfa)
1.13×
39 / 187
40
Amazon Web Services 187 pages
Findings over-represented on pages running Amazon Web Services (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.16×
39 / 187
39
Table header has scope (alfa)
1.16×
15 / 187
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.16×
8 / 187
8
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.15×
181 / 187
182
Scrolling content can be accessed by keyboard (alfa)
1.13×
39 / 187
40
PHP 187 pages
Findings over-represented on pages running PHP (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.16×
39 / 187
39
Table header has scope (alfa)
1.16×
15 / 187
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.16×
8 / 187
8
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.15×
181 / 187
182
Scrolling content can be accessed by keyboard (alfa)
1.13×
39 / 187
40
Nextdoor Ads 199 pages
Findings over-represented on pages running Nextdoor Ads (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.09×
39 / 199
39
Table header has scope (alfa)
1.09×
15 / 199
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.09×
8 / 199
8
Scrolling content can be accessed by keyboard (alfa)
1.06×
39 / 199
40
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.05×
176 / 199
182
Akamai Web Application Protector 10 pages
Findings over-represented on pages running Akamai Web Application Protector (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.07×
9 / 10
182
HSTS 200 pages
Findings over-represented on pages running HSTS (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.01×
45 / 200
48
Text has minimum contrast ratio of 4.5:1 (alfa)
1.01×
43 / 200
46
Qualtrics 214 pages
Findings over-represented on pages running Qualtrics (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
aria-hidden element does not contain focusable elements (alfa)
1.01×
39 / 214
39
Table header has scope (alfa)
1.01×
15 / 214
15
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.01×
8 / 214
8
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
181 / 214
182
Microsoft Advertising 216 pages
Findings over-represented on pages running Microsoft Advertising (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×
182 / 216
182
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
48 / 216
48
Google Analytics 216 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×
182 / 216
182
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
48 / 216
48
Akamai 216 pages
Findings over-represented on pages running Akamai (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×
182 / 216
182
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
48 / 216
48
Akamai Bot Manager 216 pages
Findings over-represented on pages running Akamai Bot Manager (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×
182 / 216
182
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
48 / 216
48
Tealium 216 pages
Findings over-represented on pages running Tealium (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×
182 / 216
182
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
48 / 216
48
Bootstrap 216 pages
Findings over-represented on pages running Bootstrap (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×
182 / 216
182
YouTube 216 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.00×
182 / 216
182