Skip to content
https://clinicaltrials.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-86t1s3
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://clinicaltrials.gov/site.webmanifest contains invalid JSON. Browsers cannot parse it.
Got: https://clinicaltrials.gov/site.webmanifest

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN CONTENTINFO (missing!)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
3 headings
REVIEW
3 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H4 Search for terms
  • H3 ClinicalTrials.gov is a place to learn about clinical studies from around the world.
  • H4 More Filters

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Alt Text Quality
1 of 10 images have issues
REVIEW
1 of 10 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
3 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
10 images 6 good alt text 3 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

17 pass 3 fail WCAG AA
h4 Search for terms
2.75:1
#000000
on
#205493
needs 3.0:1 (large text)
16px · top of page (header area)
span Hide glossary
2.17:1
#000000
on
#1A4579
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
p Study record managers: refer to the
1.53:1
#000000
on
#112E51
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 ClinicalTrials.gov i…19.25:13.0:1
#000000
#EFF6FB
Pass
title Home | ClinicalTrial…18.43:14.5:1
#000000
#F0F0F0
Pass
span Show glossary18.43:14.5:1
#000000
#F0F0F0
Pass
h4 Search for terms2.75:13.0:1
#000000
#205493
Fail
span Hide glossary2.17:14.5:1
#000000
#1A4579
Fail
p Study record manager…1.53:14.5:1
#000000
#112E51
Fail
span Data Element Definit…19.25:14.5:1
#000000
#EFF6FB
Pass
p if submitting regist…19.25:14.5:1
#000000
#EFF6FB
Pass
button Accepts healthy volu…19.25:14.5:1
#000000
#EFF6FB
Pass
div A type of16.82:14.5:1
#000000
#D9E8F6
Pass
span eligibility criteria18.20:14.5:1
#000000
#E6F0F9
Pass
div that indicates wheth…19.25:14.5:1
#000000
#EFF6FB
Pass
span condition/disease19.25:14.5:1
#000000
#EFF6FB
Pass
div being studied can pa…19.25:14.5:1
#000000
#EFF6FB
Pass
button Active comparator ar…19.25:14.5:1
#000000
#EFF6FB
Pass
span arm type19.25:14.5:1
#000000
#EFF6FB
Pass
div in which a group of …19.25:14.5:1
#000000
#EFF6FB
Pass
span intervention/treatme…19.25:14.5:1
#000000
#EFF6FB
Pass
div considered to be eff…19.25:14.5:1
#000000
#EFF6FB
Pass
button Adverse event19.25:14.5:1
#000000
#EFF6FB
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Form Accessibility
All 64 controls labeled
PASS
All 64 controls labeled
Info::
64 control(s) properly labeled
64 controls
64 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#advcondsearchCondition/diseasearia-label
#advtermsearchOther termsaria-label
#advintrsearchIntervention/treatmentaria-label
#location-inputsearchIn country, state, or cityaria-label
#adv-radio-status0radioAll studiesfor/id
#adv-radio-status1radioRecruiting and not yet recruiting studiesfor/id
#adv-radio-sex0radioAllfor/id
#adv-radio-sex1radioFemalefor/id
#adv-radio-sex2radioMalefor/id
#age-groups-radioradioSelect rangesfor/id
#adv-check-age-0checkboxChild (birth - 17)for/id
#adv-check-age-1checkboxAdult (18 - 64)for/id
#adv-check-age-2checkboxOlder adult (65+)for/id
#manual-age-range-radioradioManually enter rangefor/id
#from-age-inputinputFromfor/id
#from-age-selectselectFrom Agearia-label
#to-age-inputtextTofor/id
#to-age-selectselectTo Agearia-label
#adv-check0-healthy0checkboxYesfor/id
#adv-check0-phase0checkboxEarly Phase 1for/id
#adv-check0-phase1checkboxPhase 1for/id
#adv-check0-phase2checkboxPhase 2for/id
#adv-check0-phase3checkboxPhase 3for/id
#adv-check0-phase4checkboxPhase 4for/id
#adv-check0-phase5checkboxNot applicablefor/id
#adv-check0-studyType0checkboxInterventionalfor/id
#adv-check0-studyType1checkboxObservationalfor/id
#adv-check0-studyType1-0checkboxPatient registriesfor/id
#adv-check0-studyType2checkboxExpanded accessfor/id
#adv-check0-studyType2-0checkboxIndividual patientsfor/id
#adv-check0-studyType2-1checkboxIntermediate-size populationfor/id
#adv-check0-studyType2-2checkboxTreatment IND/Protocolfor/id
#adv-check0-results0checkboxWith resultsfor/id
#adv-check0-results1checkboxWithout resultsfor/id
#adv-check0-docs0checkboxStudy protocolsfor/id
#adv-check0-docs1checkboxStatistical analysis plans (SAPs)for/id
#adv-check0-docs2checkboxInformed consent forms (ICFs)for/id
#adv-check0-funderType0checkboxNIHfor/id
#adv-check0-funderType1checkboxOther U.S. federal agencyfor/id
#adv-check0-funderType2checkboxIndustryfor/id
#adv-check0-funderType3checkboxAll others (individuals, universities, organizations)for/id
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
inputtextDate Pickeraria-label
#advtitlessearchTitle,Title Acronymaria-label
#advoutcsearchOutcome measurearia-label
#advsponssearchSponsor,Collaboratoraria-label
#advleadsearchSponsor (Lead)aria-label
#advidsearchStudy IDsaria-label
#advlocnsearchFacility Namearia-label
#adv-check0-violation0checkboxYesfor/id
#adv-radio-ressub0radioNo selectionfor/id
#adv-radio-ressub1radioNo results submittedfor/id
#adv-radio-ressub2radioSubmitted, QC review not concludedfor/id
#adv-radio-child-ressub2-0radioSubmission with QC comments availablefor/id
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 26 passed
PASS
97

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(all filters optional) ctg-home-search-panel > div.home-search-panel > div.search-panel-header > span

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The U.S. government does not review or approve the safety and science of all st… div.usa-alert__body > div.usa-accordion > div.usa-accordion__heading > button.usa-accordion__button
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback