Skip to content
https://ama-assn.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
Heading Hierarchy
Action
81 headings, 5 skip(s)
FIX
81 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 What is good nutrition?
  • H2 How Rush dermatology rebuilt culture, access and growth
  • H2 New initiatives shape the next phase of well-being work
  • H2 How much of your physician compensation will come from salary?
  • H2 Academic coaching in medical education
  • H2 Medical education webinars
  • H2 Section Involvement Grant Event of the Month
  • H2 Looking to ace Step 1? Here’s how these medical students did it
  • H2 AMA Ethics Fellowship
  • H2 What employed physicians should know about noncompete clauses
  • H2 Top stories of Advocacy Update: April 2026
  • H2 April 17, 2026: National Advocacy Update
  • H2 AMA STEPS Forward® Innovation Academy Learning Collaborative: Reducing Administrative Burden
  • H2 Building Effective Brain Health Care Teams
  • H6 Organization skipped
  • H2 2026 Annual Meeting of the HOD: Speakers' updates overview
  • H2 2026 Annual Meeting of the HOD: April 20 Speakers' Update
  • H2 Telehealth: Council on Medical Service reports
  • H2 Medical education leadership opportunities
  • H2 Integrated Physician Practice (IPPS) policymaking
  • H2 Resident and Fellow Section (RFS) policymaking
  • H2 Top news stories from AMA Morning Rounds®: Week of April 13, 2026
  • H2 AMA upcoming appearances
  • H6 Explore Products skipped
  • H4 Popular Searches
  • H2 Organizational Nav
  • H1 American Medical Association
  • H2 7 things patients should know about protein maxxing
  • H3 Who should perform intricate surgeries on or around the eye?
  • H3 These 9 physician specialties report highest burnout rates
  • H3 New initiatives shape the next phase of well-being work
  • H3 What doctors wish patients knew about appendicitis
  • H3 Looking to ace Step 1? Here’s how these medical students did it
  • H3 6 specialties that value away rotations in GME interview invites
  • H3 How much of your physician compensation will come from salary?
  • H3 Free CME for members
  • H2 AMA Annual Meeting
  • H3 Annual Meeting of the House of Delegates
  • H3 Member Groups (Sections) Meetings
  • H4 Future HOD Meeting Dates
  • H2 During uncertain times, one thing is certain—the AMA is fighting for you.
  • H3 Fixing prior authorization
  • H3 Reforming Medicare payment
  • H3 Promoting physician-led care
  • H3 Reducing physician burnout
  • H3 Making technology work for physicians
  • H3 Progress Report
  • H2 Member benefits: Exclusive savings & resources
  • H3 6 reasons to join the AMA
  • H3 Auto & transportation
  • H3 Home & lifestyle offers
  • H3 Med student membership
  • H3 Loans & financial services
  • H3 Member dues
  • H2 Upcoming Events
  • H5 baseline-insert_invitation-24px Created with Sketch. skipped
  • H5 baseline-insert_invitation-24px Created with Sketch.
  • H5 baseline-insert_invitation-24px Created with Sketch.
  • H3 Get your daily dose of medical news
  • H2 Essential Tools & Resources
  • H5 CME from AMA Ed Hub™ skipped
  • H5 CME from AMA Ed Hub™
  • H5 Advocating for Physicians
  • H5 Advocating for Physicians
  • H5 Guides
  • H5 Guides
  • H5 Member Benefits
  • H5 Member Benefits
  • H2 (empty)
  • H2 FREIDA™, the AMA Residency and Fellowship Database®
  • H2 Your Membership Moves Medicine™
  • H2 Raising the Voice of Our Members
  • H4 Amber Shirley, DO skipped
  • H4 Steve Lee, MD
  • H2 Stay updated with AMA
  • H2 Our Work Our Work
  • H2 Career Resources Career Resources
  • H2 About About
  • H2 Affiliates & Subsidiaries Affiliates & Subsidiaries
  • H2 Follow Us
  • H2 Follow Us

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Form Accessibility
Action
6 of 9 controls have issues
FIX
6 of 9 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="global-menu">; <input type="submit" id="edit-submit-acquia-search-solr">; <input type="submit" name="op" id="edit-page-mr-submit">; <input type="submit" name="op" id="edit-footer-mr-submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search" id="edit-search">; <input type="email" name="footer_mr_email" id="edit-footer-mr-email">
Info::
3 control(s) properly labeled
9 controls
3 labeled
2 placeholder only
4 unlabeled
ControlTypeLabelMethod
#edit-page-mr-emailtextEmailfor/id
#edit-page-mr-us-citizencheckboxnone
#edit-footer-mr-us-citizencheckboxnone
#edit-searchtext(Search)placeholder only
#edit-footer-mr-emailemail(Enter your email address)placeholder only
#edit-submit-acquia-search-solrsubmit(none)none
#global-menucheckbox(none)none
#edit-page-mr-submitsubmit(none)none
#edit-footer-mr-submitsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="global-menu">; <input type="submit" id="edit-submit-acquia-search-solr">; <input type="submit" name="op" id="edit-page-mr-submit">; <input type="submit" name="op" id="edit-footer-mr-submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="search" id="edit-search">; <input type="email" name="footer_mr_email" id="edit-footer-mr-email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #fff
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 ModePartial Dark Mode
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
C
Alt Text Quality
Action
4 of 28 images have issues
REVIEW
4 of 28 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
28 images 23 good alt text 1 decorative 4 missing
IssueCount
missing4 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page Not Found | American Medical Association ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
13 icon(s) detected
REVIEW
13 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 American Medical Ass…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 What is good nutriti…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 How Rush dermatology…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 New initiatives shap…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 How much of your phy…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Academic coaching in…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Medical education we…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Section Involvement …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Looking to ace Step …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 AMA Ethics Fellowshi…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 What employed physic…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Top stories of Advoc…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 April 17, 2026: Nati…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 AMA STEPS Forward® …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Building Effective B…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 2026 Annual Meeting …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 2026 Annual Meeting …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Telehealth: Council …19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Medical education le…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Integrated Physician…19.26:13.0:1
#000000
#F5F5F5
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
Lighthouse Accessibility Audits
Score 93/100 — 4 failing, 30 passed
PASS
93

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Toggle search menu div.ama__main_nav_container > div.container > div.global-search-trigger > i.global-search-trigger__icon
Toggle sign in menu div.container > div#ama__sign-in-dropdown > div.ama__sign-in-dropdown__trigger > i.ama__sign-in-dropdown__trigger__icon

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
AMA Physician Profiles div.container > ul > li > a.ama__link--white
Why We Fight section.ama__products > div.title-bar > a.ama__link--blue > span
Apr 23, 2026 div.ama__upcoming-event > div.ama__upcoming-event__text > p.ama__upcoming-event__date > time
Virtual div > div.ama__upcoming-event > div.ama__upcoming-event__text > p.ama__upcoming-event__location
Apr 28, 2026 div.ama__upcoming-event > div.ama__upcoming-event__text > p.ama__upcoming-event__date > time
Virtual div > div.ama__upcoming-event > div.ama__upcoming-event__text > p.ama__upcoming-event__location
Apr 29, 2026 div.ama__upcoming-event > div.ama__upcoming-event__text > p.ama__upcoming-event__date > time
Hybrid div > div.ama__upcoming-event > div.ama__upcoming-event__text > p.ama__upcoming-event__location
View All Events div > section.js-view-dom-id-bfee72c755430e0cae71d854262845144943716ce996bf25c8a88323e9c6f7d4 > a.ama__link--blue > span

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Infectious Diseases Routine Screening for Patients with SUD section.js-view-dom-id-bfee72c755430e0cae71d854262845144943716ce996bf25c8a88323e9c6f7d4 > div > div.ama__upcoming-event > h5.ama__h5
Amber Shirley, DO div.homepage-social-module__container > div.profile > div.profile--content > h4

These are opportunities to improve keyboard navigation in your application.

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
Privacy Policy. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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
●`[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
●Input buttons have discernible text.
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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 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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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