Skip to content
https://aip.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ 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::
7 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 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
7 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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 (missing!) 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

B
Alt Text Quality
18 of 31 images have issues
REVIEW
18 of 31 images have issues
Warning::
18 image(s) with filename as alt text
Info::
1 image(s) with alt text over 125 characters
Info::
12 image(s) with good alt text
31 images 12 good alt text 18 generic
IssueCount
filename18 image(s)
too long1 image(s)
B
Form Accessibility
2 of 7 controls have issues
REVIEW
2 of 7 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q">
Info::
5 control(s) properly labeled
7 controls
5 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_STORAGEcheckboxnone
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
email_addressemailnone
qtext(Search)placeholder only
qtext(Search)placeholder only

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

<input type="text" name="q">; <input type="text" name="q">

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

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: Schrödinger’s cat at play - AIP.ORG ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 26 passed
REVIEW
83

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.Page-header-container > div.Page-header-bar > div.Page-header-bar-wrapper > button#burger-bar div.Page-header-container > div.Page-header-bar > div.Page-header-bar-wrapper > button#burger-bar
bsp-search-overlay.SearchOverlay > form.SearchOverlay__form > div.SearchOverlay__buttons > button.SearchOverlay__submit bsp-search-overlay.SearchOverlay > form.SearchOverlay__form > div.SearchOverlay__buttons > button.SearchOverlay__submit
bsp-search-overlay.SearchOverlay > form.SearchOverlay__form > div.SearchOverlay__buttons > button.SearchOverlay__close bsp-search-overlay.SearchOverlay > form.SearchOverlay__form > div.SearchOverlay__buttons > button.SearchOverlay__close
div.PagePromoInterest > div.PagePromoInterest__content > div.PagePromoInterest__subscribe > button.PagePromoInterest__btn div.PagePromoInterest > div.PagePromoInterest__content > div.PagePromoInterest__subscribe > button.PagePromoInterest__btn
div.PagePromoInterest > div.PagePromoInterest__content > div.PagePromoInterest__subscribe > button.PagePromoInterest__btn div.PagePromoInterest > div.PagePromoInterest__content > div.PagePromoInterest__subscribe > button.PagePromoInterest__btn
div.PagePromoInterest > div.PagePromoInterest__content > div.PagePromoInterest__subscribe > button.PagePromoInterest__btn div.PagePromoInterest > div.PagePromoInterest__content > div.PagePromoInterest__subscribe > button.PagePromoInterest__btn

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.

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
Cookie Policy div.osano-cm-window > div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__content > a.osano-cm-storage-policy
Storage Preferences div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Third Parties div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Storage ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Targeted Advertising ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Personalization ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Analytics ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Save div.osano-cm-window > div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__buttons > button.osano-cm-save
Accept All div.osano-cm-window > div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all
Reject Non-Essential div.osano-cm-window > div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__buttons > button.osano-cm-denyAll

These are opportunities to improve the legibility of your content.

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
Storage Preferences div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Third Parties div#76184b9d-303c-4d39-8f28-bec6399aa702 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
AIP div.PagePromoModuleInfo-content > div.PagePromoCategoryAndType > div.PagePromoCategoryAndType__category > a.Link
EX LIBRIS UNIVERSUM div.PagePromoModuleInfo-content > div.PagePromoCategoryAndType > div.PagePromoCategoryAndType__category > a.Link

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
●Form elements have associated labels
●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
●`<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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●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 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
○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.
○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.
A+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Sections
  • H1 Empowering Physical Scientists
  • H2 Tune into Advocacy Actions Being Taken Across the AIP Federation to Support and Mobilize Our Community
  • H2 Featured News
  • H2 (empty)
  • H2 AIP Foundation Stories of Impact: Learn How We Empower Physical Scientists
  • H2 Subscribe for Updates
  • H3 Stay in touch
  • H3 Member societies
  • H3 Member societies
  • H3 Stay in touch

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

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
h2 Tune into Advocacy A…18.27:13.0:1
#000000
#EDEFF5
Pass
h2 Featured News18.27:13.0:1
#000000
#EDEFF5
Pass
h2 AIP Foundation Stori…18.27:13.0:1
#000000
#EDEFF5
Pass
h2 Subscribe for Update…18.27:13.0:1
#000000
#EDEFF5
Pass
h3 Sections18.27:13.0:1
#000000
#EDEFF5
Pass
h3 Stay in touch18.27:13.0:1
#000000
#EDEFF5
Pass
h3 Member societies18.27:13.0:1
#000000
#EDEFF5
Pass
h3 Member societies18.27:13.0:1
#000000
#EDEFF5
Pass
h3 Stay in touch18.27:13.0:1
#000000
#EDEFF5
Pass
title AIP.ORG18.27:14.5:1
#000000
#EDEFF5
Pass
span Opens in a new windo…18.27:14.5:1
#000000
#EDEFF5
Pass
span Opens an external we…18.27:14.5:1
#000000
#EDEFF5
Pass
span Opens an external we…18.27:14.5:1
#000000
#EDEFF5
Pass
span We and our 1 IAB TCF…18.27:14.5:1
#000000
#EDEFF5
Pass
span Personal data may be…18.27:14.5:1
#000000
#EDEFF5
Pass
span Our third party IAB …18.27:14.5:1
#000000
#EDEFF5
Pass
span You may change your …18.27:14.5:1
#000000
#EDEFF5
Pass
span You may close this b…18.27:14.5:1
#000000
#EDEFF5
Pass
a Cookie Policy18.27:14.5:1
#000000
#EDEFF5
Pass
a Storage Preferences18.27:14.5:1
#000000
#EDEFF5
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