nih.gov: technology ↔ issues
Accessibility findings that appear disproportionately on pages running a given technology, across the 294 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.
Cloudflare Browser Insights 294 pages
Findings over-represented on pages running Cloudflare Browser Insights (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Text has enhanced contrast (alfa)
1.00×
134 / 294
134
Text has minimum contrast ratio of 4.5:1 (alfa)
1.00×
134 / 294
134
Link in text block is visually distinguishable without color (alfa)
1.00×
134 / 294
134
aria attribute is permitted for element role (alfa)
1.00×
134 / 294
134
Form field label is visible (alfa)
1.00×
134 / 294
134
Scrolling content can be accessed by keyboard (alfa)
1.00×
134 / 294
134
Target size is at least 44×44 CSS pixels (Enhanced) (alfa)
1.00×
134 / 294
134
Crazy Egg 294 pages
Findings over-represented on pages running Crazy Egg (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Text has enhanced contrast (alfa)
1.00×
134 / 294
134
Google Analytics 294 pages
Findings over-represented on pages running Google Analytics (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Varnish 294 pages
Findings over-represented on pages running Varnish (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Cloudflare 294 pages
Findings over-represented on pages running Cloudflare (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Drupal 294 pages
Findings over-represented on pages running Drupal (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
jQuery 294 pages
Findings over-represented on pages running jQuery (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
HTTP/3 294 pages
Findings over-represented on pages running HTTP/3 (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Acquia Cloud Platform 294 pages
Findings over-represented on pages running Acquia Cloud Platform (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Amazon Web Services 294 pages
Findings over-represented on pages running Amazon Web Services (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
PHP 294 pages
Findings over-represented on pages running PHP (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
HSTS 294 pages
Findings over-represented on pages running HSTS (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
Google Tag Manager 294 pages
Findings over-represented on pages running Google Tag Manager (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217
USWDS 294 pages
Findings over-represented on pages running USWDS (lift ≥ 1, ≥5 pages support).
Finding
Lift
On tech pages
On all pages
link-in-text-block (axe)
1.00×
294 / 294
294
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe)
1.00×
294 / 294
294
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe)
1.00×
217 / 294
217