Skip to content
https://healthychildren.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
43
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
F
Alt Text Quality
Action
19 of 25 images have issues
FIX
19 of 25 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
15 image(s) with filename as alt text
Info::
3 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
25 images 3 good alt text 3 decorative 15 generic 4 missing
IssueCount
missing4 image(s)
filename15 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

F
Form Accessibility
Action
9 of 9 controls have issues
FIX
9 of 9 controls have issues
Critical::
7 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="ctl00$aapTopNavigation$txtMobileSearch" id="sidr-id-ctl00_aapTopNavigation_txtMobileSearch">; <input type="submit" name="ctl00$aapTopNavigation$btnMobileSearch" id="sidr-id-ctl00_aapTopNavigation_btnMobileSearch">; <input type="submit" name="ctl00$aapTopNavigation$btnGlobalSearch" id="ctl00_aapTopNavigation_btnGlobalSearch">; <input type="text" name="ctl00$aapTopNavigation$txtMobileSearch" id="ctl00_aapTopNavigation_txtMobileSearch">; <input type="submit" name="ctl00$aapTopNavigation$btnMobileSearch" id="ctl00_aapTopNavigation_btnMobileSearch">; <input type="text" name="__spDummyText1">; <input type="text" name="__spDummyText2">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="ctl00$aapTopNavigation$txtGlobalSearch" id="ctl00_aapTopNavigation_txtGlobalSearch">; <input type="text" name="ctl00$SPWebPartManager1$g_440e9c00_ad49_4904_8ee5_0f756a3d9630$ctl00$txtFAPSearch" id="ctl00_SPWebPartManager1_g_440e9c00_ad49_4904_8ee5_0f756a3d9630_ctl00_txtFAPSearch">
9 controls
0 labeled
2 placeholder only
7 unlabeled
ControlTypeLabelMethod
#ctl00_aapTopNavigation_txtGlobalSearchtext(Search for safety, tips, illness, etc.)placeholder only
#ctl00_SPWebPartManager1_g_440e9c00_ad49_4904_8ee5_0f756a3d9630_ctl00_txtFAPSearchtext(Enter Zip Code)placeholder only
#sidr-id-ctl00_aapTopNavigation_txtMobileSearchtext(none)none
#ctl00_aapTopNavigation_btnGlobalSearchsubmit(none)none
#ctl00_aapTopNavigation_txtMobileSearchtext(none)none
#ctl00_aapTopNavigation_btnMobileSearchsubmit(none)none
#sidr-id-ctl00_aapTopNavigation_btnMobileSearchsubmit(none)none
__spDummyText1text(none)none
__spDummyText2text(none)none

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

<input type="text" name="ctl00$aapTopNavigation$txtMobileSearch" id="sidr-id-ctl00_aapTopNavigation_txtMobileSearch">; <input type="submit" name="ctl00$aapTopNavigation$btnMobileSearch" id="sidr-id-ctl00_aapTopNavigation_btnMobileSearch">; <input type="submit" name="ctl00$aapTopNavigation$btnGlobalSearch" id="ctl00_aapTopNavigation_btnGlobalSearch">; <input type="text" name="ctl00$aapTopNavigation$txtMobileSearch" id="ctl00_aapTopNavigation_txtMobileSearch">; <input type="submit" name="ctl00$aapTopNavigation$btnMobileSearch" id="ctl00_aapTopNavigation_btnMobileSearch">; <input type="text" name="__spDummyText1">; <input type="text" name="__spDummyText2">

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="ctl00$aapTopNavigation$txtGlobalSearch" id="ctl00_aapTopNavigation_txtGlobalSearch">; <input type="text" name="ctl00$SPWebPartManager1$g_440e9c00_ad49_4904_8ee5_0f756a3d9630$ctl00$txtFAPSearch" id="ctl00_SPWebPartManager1_g_440e9c00_ad49_4904_8ee5_0f756a3d9630_ctl00_txtFAPSearch">

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 Custom Styling Navigation Homepage Link Search Form
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://healthychildren.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://healthychildren.org/manifest.json

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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
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 1 <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
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 2 pass AA only
a Delivery and Beyond
1.63:1
#000000
on
#293433
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title HealthyChildren.org …20.21:14.5:1
#000000
#FCFBF1
Pass
span Skip to main content20.29:14.5:1
#000000
#FBFBFB
Pass
span Enable accessibility…21.00:14.5:1
#000000
#FFFFFF
Pass
span Open the accessibili…21.00:14.5:1
#000000
#FFFFFF
Pass
a Log in21.00:14.5:1
#000000
#FFFFFF
Pass
a Register21.00:14.5:1
#000000
#FFFFFF
Pass
a Home21.00:14.5:1
#000000
#FFFFFF
Pass
a Our Sponsors21.00:14.5:1
#000000
#FFFFFF
Pass
span Ages & Stages21.00:14.5:1
#000000
#FFFFFF
Pass
span Ages & Stages21.00:14.5:1
#000000
#FFFFFF
Pass
a Ages and Stages21.00:14.5:1
#000000
#FFFFFF
Pass
a Your Child’s Check…21.00:14.5:1
#000000
#FFFFFF
Pass
a Prenatal21.00:14.5:1
#000000
#FFFFFF
Pass
a Decisions to Make4.59:14.5:1
#000000
#717773
Pass
a Delivery and Beyond1.63:14.5:1
#000000
#293433
Fail
a Baby (0-12 mos.)4.94:14.5:1
#000000
#767C7B
Pass
a Bathing & Skin Car…16.83:14.5:1
#000000
#E6E6E6
Pass
a Breastfeeding9.77:14.5:1
#000000
#E0A65A
Pass
a Crying & Colic21.00:14.5:1
#000000
#FFFFFF
Pass
a Diapers & Clothing21.00:14.5:1
#000000
#FFFFFF
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+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 The AAP Parenting Website
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /_layouts/15/AAP.HealthyChildren/styles/print.css?v=4.0
Print Stylesheet Print Optimized
Print stylesheet /_layouts/15/AAP.HealthyChildren/styles/print.css?v=4.0 Inline @media print Not detected
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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
Open this option section.page-content > div#hcMainContainer > div#DeltaPlaceHolderMain > a#mainContent

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
Want to receive our FREE parent newsletter? div#ctl00_RegistrationBanner_pnlRegistrationBanner > div.registration-banner-wrap > div.registration-banner-inner > div.title
​Register now and get updates about children's health delivered right to your i… div.registration-banner-wrap > div.registration-banner-inner > div.description > p

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html#ctl00_Html1 html#ctl00_Html1

These items highlight common accessibility best practices.

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
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.
`[accesskey]` values are unique
`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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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
Buttons have an accessible name
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
Links are distinguishable without relying on color.
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
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