Skip to content
https://aaos.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Alt Text Quality
Action
8 of 26 images have issues
FIX
8 of 26 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
5 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
26 images 13 good alt text 5 decorative 8 missing
IssueCount
missing8 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
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
No navigation patterns
FIX
No navigation patterns
Info::
2 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 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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 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

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
Lighthouse Accessibility Audits
Action
Score 78/100 — 7 failing, 24 passed
REVIEW
78

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
Learn more div.cc-grower > div.cc-window > span#cookieconsent:desc > a.cc-link
AAOS Store div.box--row > div.txt > h3 > a#morestore
Learn more about partnering with AAOS. div.row > div.col-12 > p > a#partner

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-6 > a.logo > img div.row > div.col-6 > a.logo > img
ul.footer--panel > li > a.logo > img.img-responsive ul.footer--panel > li > a.logo > img.img-responsive
ul.footer-app-links > li.footer-app-link > a > img ul.footer-app-links > li.footer-app-link > a > img
ul.footer-app-links > li.footer-app-link > a > img ul.footer-app-links > li.footer-app-link > a > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.col-6 > a.logo div.container > div.row > div.col-6 > a.logo
div.container > ul.footer--panel > li > a.logo div.container > ul.footer--panel > li > a.logo
li > ul.btn-container > li > a.btn li > ul.btn-container > li > a.btn
li > ul.btn-container > li > a.btn li > ul.btn-container > li > a.btn
li > ul.btn-container > li > a.btn li > ul.btn-container > li > a.btn
li > ul.btn-container > li > a.btn li > ul.btn-container > li > a.btn
li > ul.btn-container > li > a.btn li > ul.btn-container > li > a.btn
li > ul.btn-container > li > a.btn li > ul.btn-container > li > a.btn
li > ul.footer-app-links > li.footer-app-link > a li > ul.footer-app-links > li.footer-app-link > a
li > ul.footer-app-links > li.footer-app-link > a li > ul.footer-app-links > li.footer-app-link > a

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search div.typeahead__container > div.typeahead__field > div.typeahead__query > button.btn

These items highlight common accessibility best practices.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content body > a.skip-to-content

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
I UNDERSTAND! div.cc-grower > div.cc-window > div.cc-compliance > a.cc-btn
○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
●Form elements have associated labels
●`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
●Elements use only permitted ARIA attributes
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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
○`<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.
○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.
A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H1 Big Ideas Start Here. Share Your Expertise at AAOS 2027!
  • H2 Quick Access
  • H3 Claim CME or Access Transcript
  • H3 My Online Learning Access
  • H3 JAAOS
  • H3 The Bone Beat Orthopaedic Podcast Channel
  • H3 Examination Center & ResStudy
  • H3 Orthopaedic Video Theater
  • H3 OrthoInfo - Patient Education
  • H3 Biologics Dashboard
  • H3 Clinical Practice Guidelines
  • H3 Career Center
  • H3 Orthopaedic Calendar
  • H3 ROCK
  • H2 Featured
  • H2 What's New
  • H3 Dive into the science shaping recovery and return to play for today’s athlete at the AAOS Biologics Symposium.
  • H3 The free AAOS Membership App is your gateway to essential resources, JAAOS® content, and CME tools.
  • H3 New 2-year risk-adjusted revision rate visuals reveal long-term outcomes and trends for AJRR participants.
  • H3 Ensure your AAOS personal and directory profiles are up to date so your colleagues and patients can easily find you.
  • H3 Plan ahead for AAOS 2027 with early hotel booking for better rates, ideal locations, and less hassle.
  • H3 Meet the 2026 AAOS award winners recognized for leadership, service, and impact in orthopaedic care.
  • H2 Journals, Podcasts & News
  • H3 JAAOS - April 15, 2026: Utilization of an Artificial Intelligence-Based Documentation System Improves Provider Efficiency in Outpatient Orthopaedic Clinics: Reducing the Afterhours Burden of the Elect
  • H3 The AAOS Now Podcast spotlights the AAOS Patient Engagement Task Force. Listen now!
  • H3 AAOS Now – March 2026: Inside AAOS’ patient engagement efforts with the Patient Engagement Task Force co-chairs
  • H2 CME Courses & Webinars
  • H3 AAOS Fundamentals of Hip and Knee Arthroplasty for Orthopaedic Residents | April 24-26 | Rosemont, IL
  • H3 Pain Management & Opioids: A Patient-Centered Approach | April 27 | Virtual
  • H3 AAOS Part II Board Prep & Review | May 30 | Virtual
  • H2 Shop the AAOS Store
  • H3 Find all courses, self-assessment, CME, and more at the AAOS Store
  • H2 Corporate Partners
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#aaos-general-search-barsearchSearcharia-label
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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 Big Ideas Start Here…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Quick Access21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What's New21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Journals, Podcasts &…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CME Courses & Webina…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop the AAOS Store21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Corporate Partners21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Claim CME or Access …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 My Online Learning A…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 JAAOS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The Bone Beat Orthop…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Examination Center &…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Orthopaedic Video Th…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 OrthoInfo - Patient …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Biologics Dashboard21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Clinical Practice Gu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Career Center21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Orthopaedic Calendar21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ROCK21.00:13.0: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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback