Skip to content
https://asme.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
Heading Hierarchy
Action
45 headings, 5 skip(s)
FIX
45 headings, 5 skip(s)
Info::
Single H1 present
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 → 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.
  • H2 Setting the Standard
  • H1 The American Society of Mechanical Engineers
  • H2 Standards
  • H5 Process Piping skipped
  • H5 Ropes
  • H5 Thermoplastic Piping Systems
  • H5 Model Organization Practices
  • H5 MFC-21.1 Standard—Find, Compare, & Purc...
  • H5 B94.33.1 Jig Bushings (Metric)
  • H2 Courses
  • H2 Publications
  • H2 Certifications
  • H5 Locate ASME Certified Companies skipped
  • H5 How to Start a Certificate Application
  • H5 Personnel Certification
  • H2 Resources
  • H5 Seek and Use Feedback for Successful Engineering Career skipped
  • H5 Cloaking Sensitive Tech from Magnetic Fields
  • H5 The Importance of Mechatronics for Modern Engineering
  • H5 Quiz: Successful Splashdown of Apollo 13
  • H2 Events
  • H5 Verification, Validation, and Uncertainty Quantification Symposium 2026 - VVUQ 2026 skipped
  • H5 Beyond the Risk Register: Portfolio Decisions that Hold Up Under Pressure
  • H5 International ICE Forward Symposium 2026
  • H4 Explore More Events
  • H2 Becoming an ASME Member
  • H2 Sections and Divisions
  • H2 Your Engineering Career Destination
  • H4 Quick Job Search skipped
  • H5 About ASME
  • H5 Codes & Standards
  • H5 Certification & Accreditation
  • H5 Learning & Development
  • H5 Publications & Submissions
  • H5 Conferences & Events
  • H5 Topics & Resources
  • H5 ASME Membership
  • H3 About ASME
  • H3 Codes & Standards
  • H3 Certification & Accreditation
  • H3 Learning & Development
  • H3 Publications & Submissions
  • H3 Conferences & Events
  • H3 Topics & Resources
  • H3 ASME Membership

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

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 20 passed
REVIEW
86

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
Standards div.container > div.row > div.col-lg-3 > h2
About ASME div.container > div.row > div.popular-tags > a.btn
Business and Career Support div.container > div.row > div.popular-tags > a.btn
Conferences and Events div.container > div.row > div.popular-tags > a.btn
Engineering div.container > div.row > div.popular-tags > a.btn
Membership div.container > div.row > div.popular-tags > a.btn
Standards Development div.container > div.row > div.popular-tags > a.btn
ASME Information div.container > div.row > div.popular-tags > a.btn
Publications div.container > div.row > div.popular-tags > a.btn
Events main#home > section.events > div.container > h2

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
Process Piping div.col-lg-9 > div.standard-cards > a.card-highlight > h5
Locate ASME Certified Companies div.col-lg-4 > a.certificationCard > div.contentContainer > h5
Seek and Use Feedback for Successful Engineering Career div.col-lg-5 > a.featured-resource > div.featured-resource-item > h5
Verification, Validation, and Uncertainty Quantification Symposium 2026 - VVUQ … a > div.event-card > div.event-info > h5
Quick Job Search div.container > div.row > div.col-md-3 > h4

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu div#react_0HNKVAV24I82S > div.index-module__siteheader--AsLaV > div.index-module__navbar--nGYMQ > li.NavMenuButton-module__nav-button--luGwB

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

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
Show Slide 0 div#pagination-dots > ul.asme-dots > li#asme_dot_0 > button#asme_dot_button_0
Show Slide 1 div#pagination-dots > ul.asme-dots > li#asme_dot_1 > button#asme_dot_button_1
Show Slide 2 div#pagination-dots > ul.asme-dots > li#asme_dot_2 > button#asme_dot_button_2
Show Slide 3 div#pagination-dots > ul.asme-dots > li#asme_dot_3 > button#asme_dot_button_3
Show Slide 4 div#pagination-dots > ul.asme-dots > li#asme_dot_4 > button#asme_dot_button_4
Show Slide 5 div#pagination-dots > ul.asme-dots > li#asme_dot_5 > button#asme_dot_button_5
Show Slide 6 div#pagination-dots > ul.asme-dots > li#asme_dot_6 > button#asme_dot_button_6
Professional div.d-flex > div.division-description > p.title > a
Student div.d-flex > div.division-description > p.title > a
Technical div.d-flex > div.division-description > p.title > a

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●ARIA attributes are used as specified for the element's role
●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>`).
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○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
○`<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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 CONTENTINFO footer

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

A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
17 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
24 images 7 good alt text 17 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="home-search">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#jobkeywordstextKeywords:for/id
#titlecheckboxcheckboxSearch job title onlyfor/id
#joblocationtextLocation:for/id
#home-searchsearch(Search products, events, courses, resource categories...)placeholder only

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

<input type="search" id="home-search">

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

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 The American Society…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Setting the Standard20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Standards20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Courses20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Publications20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Certifications20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Resources20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Events20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Becoming an ASME Mem…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Sections and Divisio…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Your Engineering Car…20.12:13.0:1
#000000
#FAFAFA
Pass
title The American Society…21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
span ASME21.00:14.5:1
#000000
#FFFFFF
Pass
span The American Society…20.55:14.5:1
#000000
#FAFDFE
Pass
a ASME Foundation19.55:14.5:1
#000000
#ECF9FE
Pass
a Sections & Divisions19.55:14.5:1
#000000
#ECF9FE
Pass
a Programs19.55:14.5:1
#000000
#ECF9FE
Pass
a Sign In/Create Accou…19.55:14.5:1
#000000
#ECF9FE
Pass
span Cart19.55:14.5:1
#000000
#ECF9FE
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