Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Heading Hierarchy

Action

51 headings, 1 skip(s)

FIX

51 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

15 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 Introducing ULTRUS™
H3 Featured Products
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 Introducing ULTRUS™
H3 Featured Products
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 UL Solutions
H1 The faster AI moves, the more trust matters.
H2 Future-proofed innovation starts with safety
H3 Data Centers
H3 Energy Transition
H3 Streamline market access
H3 Retail
H3 UL Solutions experts are disruptors of the best kind in the business of working for a safer world
H2 What do we do for our customers?
H3 Certification services
H3 Testing services
H3 Verification services
H3 Auditing and inspections
H3 Software
H3 Learning and development
H3 Field evaluation services
H3 Advisory services
H2 (empty)
H2 Make science your advantage
H2 Can we help you find certification information?
H3 Find a product certification
H3 Find a sustainable product certification
H3 Follow-up certification services
H2 Customer resources
H3 Standards catalog
H3 myUL® Client Portal
H3 Marks and Label Hub
H2 Inside UL Solutions
H4 Our mission skipped
H4 Laboratories and offices
H4 Learning and development
H4 News
H4 Choose a region

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

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

Action

6 landmarks

REVIEW

6 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

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

Link & Button Quality

Action

15 issue(s) across 546 links and 12 buttons

REVIEW

15 issue(s) across 546 links and 12 buttons

15 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /software/ultrus ("Learn more"); /consumers ("Learn more"); /software/ultrus ("Learn more"); /services/certification ("Learn more"); /services/testing ("Learn more"); /services/verification ("Learn more"); /services/auditing-and-inspection ("Learn more"); /software/software-products ("Learn more"); /services/learning-and-development ("Learn more"); /services/field-evaluations ("Learn more") (+5 more)

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://productiq.ulprospector.com/en; https://spot.ul.com/; https://www.shopulstandards.com/; https://my.ul.com/; https://markshub.ul.com/

526 link(s) with descriptive text

546 links

0 empty

15 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/software/ultrus	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ultrus
/consumers	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Consumers
/software/ultrus	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ultrus
/services/certification	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Certification
/services/testing	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Testing
/services/verification	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Verification
/services/auditing-and-inspection	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Auditing And Inspection
/software/software-products	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Software Products
/services/learning-and-development	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Learning And Development
/services/field-evaluations	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Field Evaluations
/services/advisory	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advisory
https://productiq.ulprospector.com/en	Search now	new tab	Add '(opens in new tab)' to text
https://spot.ul.com/	Search now	new tab	Add '(opens in new tab)' to text
/resources/follow-up-services	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Follow Up Services
https://www.shopulstandards.com/	Search the catalog	new tab	Add '(opens in new tab)' to text
https://my.ul.com/	Sign in to myUL	new tab	Add '(opens in new tab)' to text
https://markshub.ul.com/	Go to Marks and Label Hub	new tab	Add '(opens in new tab)' to text
/about/mission	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Mission
/services/learning-and-development	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Learning And Development
https://www.ul.com/resources/online-poli…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: About Cookies

538 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/software/ultrus ("Learn more"); /consumers ("Learn more"); /software/ultrus ("Learn more"); /services/certification ("Learn more"); /services/testing ("Learn more"); /services/verification ("Learn more"); /services/auditing-and-inspection ("Learn more"); /software/software-products ("Learn more"); /services/learning-and-development ("Learn more"); /services/field-evaluations ("Learn more") (+5 more)

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://productiq.ulprospector.com/en; https://spot.ul.com/; https://www.shopulstandards.com/; https://my.ul.com/; https://markshub.ul.com/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title UL Logo ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 The faster AI moves, the more trust matt…

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Future-proofed innovation starts with sa…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What do we do for our customers?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Make science your advantage

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Can we help you find certification infor…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Customer resources

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Inside UL Solutions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Introducing ULTRUS™

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Featured Products

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Introducing ULTRUS™

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Featured Products

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 UL Solutions

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Data Centers

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Energy Transition

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Streamline market access

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Retail

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 UL Solutions experts are disruptors of t…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Certification services

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Testing services

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Verification services

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The faster AI moves,…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Future-proofed innov…	1.00:1	3.0:1	#000000	#000000	Fail
h2 What do we do for ou…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Make science your ad…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Can we help you find…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Customer resources	1.00:1	3.0:1	#000000	#000000	Fail
h2 Inside UL Solutions	1.00:1	3.0:1	#000000	#000000	Fail
h3 Introducing ULTRUS�…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Featured Products	1.00:1	3.0:1	#000000	#000000	Fail
h3 Introducing ULTRUS�…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Featured Products	1.00:1	3.0:1	#000000	#000000	Fail
h3 UL Solutions	1.00:1	3.0:1	#000000	#000000	Fail
h3 Data Centers	1.00:1	3.0:1	#000000	#000000	Fail
h3 Energy Transition	1.00:1	3.0:1	#000000	#000000	Fail
h3 Streamline market ac…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Retail	1.00:1	3.0:1	#000000	#000000	Fail
h3 UL Solutions experts…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Certification servic…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Testing services	1.00:1	3.0:1	#000000	#000000	Fail
h3 Verification service…	1.00:1	3.0:1	#000000	#000000	Fail

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+

Alt Text Quality

All 26 images OK

PASS

All 26 images OK

2 decorative image(s) correctly marked

24 image(s) with good alt text

26 images 24 good alt text 2 decorative

All images have appropriate alt text.

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 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--2">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-keys	search	Search	for/id
#choose-region	select	Choose a region	for/id
#edit-submit--2	submit	(none)	none

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

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

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 30 passed

PASS

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.

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
Our mission `div.span-6-t > div.card > div.content-container > h4`

These are opportunities to improve keyboard navigation in your application.

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`

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.js `html.js`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Select elements have associated label elements.

●`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

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●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.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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.

○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.

○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.