vital-scans open quality ledger

www.cms.gov: technology ↔ issues

Accessibility findings that appear disproportionately on pages running a given technology, across the 104 page(s) in 2026-W40 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.

reCAPTCHA 31 pages

Findings over-represented on pages running reCAPTCHA (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
link-in-text-block (axe) 3.10× 12 / 31 13
Use <ul>/<ol> with only <li> children for lists; don't fake lists with <div>s. (axe) 3.05× 10 / 31 11

jsDelivr 37 pages

Findings over-represented on pages running jsDelivr (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
link-in-text-block (axe) 2.81× 13 / 37 13
Use <ul>/<ol> with only <li> children for lists; don't fake lists with <div>s. (axe) 2.81× 11 / 37 11

Bootstrap 37 pages

Findings over-represented on pages running Bootstrap (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
link-in-text-block (axe) 2.81× 13 / 37 13
Use <ul>/<ol> with only <li> children for lists; don't fake lists with <div>s. (axe) 2.81× 11 / 37 11

Microsoft ASP.NET 37 pages

Findings over-represented on pages running Microsoft ASP.NET (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
link-in-text-block (axe) 2.81× 13 / 37 13
Use <ul>/<ol> with only <li> children for lists; don't fake lists with <div>s. (axe) 2.81× 11 / 37 11

Drupal 53 pages

Findings over-represented on pages running Drupal (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

Acquia Cloud Platform 53 pages

Findings over-represented on pages running Acquia Cloud Platform (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

Amazon Web Services 53 pages

Findings over-represented on pages running Amazon Web Services (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

PHP 53 pages

Findings over-represented on pages running PHP (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

Qualtrics 53 pages

Findings over-represented on pages running Qualtrics (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

Tealium 53 pages

Findings over-represented on pages running Tealium (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

YouTube 53 pages

Findings over-represented on pages running YouTube (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Text has minimum contrast ratio of 4.5:1 (alfa) 1.57× 8 / 53 10
Form field label is visible (alfa) 1.57× 8 / 53 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.57× 8 / 53 10
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.26× 9 / 53 14

jQuery 90 pages

Findings over-represented on pages running jQuery (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) 1.16× 14 / 90 14
link-in-text-block (axe) 1.16× 13 / 90 13
Use <ul>/<ol> with only <li> children for lists; don't fake lists with <div>s. (axe) 1.16× 11 / 90 11
Text has minimum contrast ratio of 4.5:1 (alfa) 1.16× 10 / 90 10
Form field label is visible (alfa) 1.16× 10 / 90 10
Target size is at least 44×44 CSS pixels (Enhanced) (alfa) 1.16× 10 / 90 10

Google Analytics 104 pages

Findings over-represented on pages running Google Analytics (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Remove empty headings or give them text (axe) 1.00× 16 / 104 16
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.00× 14 / 104 14
Add a lang attribute to <html> (e.g (axe) 1.00× 14 / 104 14
Give every <img> a meaningful alt attribute (axe) 1.00× 14 / 104 14
Each page should have exactly one <main> landmark. (axe) 1.00× 14 / 104 14
Wrap all page content in landmarks (header, nav, main, footer) so users can navigate by region. (axe) 1.00× 14 / 104 14

HSTS 104 pages

Findings over-represented on pages running HSTS (lift ≥ 1, ≥5 pages support).
Finding Lift On tech pages On all pages
Remove empty headings or give them text (axe) 1.00× 16 / 104 16
Use heading levels in order (h1 → h2 → h3) without skipping; structure, not size. (axe) 1.00× 14 / 104 14