Skip to content
https://diabetes.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
9 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 9 <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
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-search">; <input type="submit" id="edit-submit-events">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-keywordstextkeywords Searchnone
#edit-field-event-type-exclude--3selectfield_event_type_exclude Exclude Event typenone
#edit-submit-searchsubmit(none)none
#edit-submit-eventssubmit(none)none

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

<input type="submit" id="edit-submit-search">; <input type="submit" id="edit-submit-events">

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | American Diabetes Association ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Resources Today for …3.56:13.0:1
#000000
#656464
Pass
h2 It All Matters3.56:13.0:1
#000000
#656464
Pass
h2 What's Happening?3.56:13.0:1
#000000
#656464
Pass
h2 Diabetes By-the-Numb…3.56:13.0:1
#000000
#656464
Pass
h2 Are you at risk?3.56:13.0:1
#000000
#656464
Pass
h2 Life with Diabetes3.56:13.0:1
#000000
#656464
Pass
h2 Health & Wellness3.56:13.0:1
#000000
#656464
Pass
h2 Food & Nutrition3.56:13.0:1
#000000
#656464
Pass
h2 Tools & Resources3.56:13.0:1
#000000
#656464
Pass
h2 Calendar of Events3.56:13.0:1
#000000
#656464
Pass
h2 Upcoming events3.56:13.0:1
#000000
#656464
Pass
h2 Stay Hydrated!3.56:13.0:1
#000000
#656464
Pass
h2 Get Involved3.56:13.0:1
#000000
#656464
Pass
h2 Donate Today3.56:13.0:1
#000000
#656464
Pass
h2 Sponsors3.56:13.0:1
#000000
#656464
Pass
h3 National Volunteer W…3.56:13.0:1
#000000
#656464
Pass
h3 Save 25% on Diabetes…3.56:13.0:1
#000000
#656464
Pass
h3 Take Steps to Preven…3.56:13.0:1
#000000
#656464
Pass
h3 2026 Scientific Sess…3.56:13.0:1
#000000
#656464
Pass
h3 Diabetes Technology …3.56:13.0:1
#000000
#656464
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+
Landmark Structure
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main menu" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
35 headings
PASS
35 headings
Info::
Single H1 present
  • H1 Resources Today for a Healthier Tomorrow
  • H2 It All Matters
  • H2 What's Happening?
  • H3 National Volunteer Week
  • H3 Save 25% on Diabetes Nutrition Tools
  • H3 Take Steps to Prevent Type 2 Diabetes
  • H3 2026 Scientific Sessions
  • H3 Diabetes Technology Meeting
  • H3 ADA Camp Registration is Open
  • H3 85 Years of Progress
  • H3 2024 Annual Report
  • H3 Your Diabetes Questions Answered
  • H3 Access to Obesity Treatment
  • H3 Diabetes Day by Day
  • H3 Control Your Meals
  • H2 Diabetes By-the-Numbers
  • H3 Meet Alex
  • H3 Meet Alex
  • H2 Are you at risk?
  • H2 Life with Diabetes
  • H2 Health & Wellness
  • H2 Food & Nutrition
  • H2 Tools & Resources
  • H2 Calendar of Events
  • H2 Upcoming events
  • H3 2026 Tour de Cure®: Mid-Atlantic
  • H3 2026 Step Out® Walk: North Texas
  • H3 Sending Your Child to a Non-Diabetes Camp—Need-to-Knows and Preparing the Camp Team
  • H2 Stay Hydrated!
  • H2 Get Involved
  • H3 Help Defeat Diabetes
  • H3 We Are Here for You
  • H2 Donate Today
  • H3 Give Today and Change lives!
  • H2 Sponsors
A
Alt Text Quality
1 of 64 images have issues
PASS
1 of 64 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
64 images 61 good alt text 2 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

A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 30 passed
PASS
91

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dialog-off-canvas-main-canvas > div.gradientBlack > div.large-container > button.close-btn div.dialog-off-canvas-main-canvas > div.gradientBlack > div.large-container > button.close-btn

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ask the Experts Class DIY Family Meet-Ups Live Cooking Classes State Of Diabete… label.js-form-item > div.form-item__content-wrapper > div.form-item__dropdown > select#edit-field-event-type-exclude--3

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Elements with visible text labels have matching accessible names.
○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