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