Skip to content
https://ptc.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓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
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
h2 Unlock the Full Potential of Your Engine…
1.31:1
#000000
on
#341C06
needs 3.0:1 (large text)
24px · mid-page
h2 Unlock the Full Potential of Your Servic…
1.47:1
#000000
on
#272B2C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 PTC named outright Leader for enterprise…
1.74:1
#000000
on
#333735
needs 3.0:1 (large text)
19px · mid-page · over background image/gradient
h3 Enterprise ALM accelerates the pace of i…
2.16:1
#000000
on
#3F4548
needs 3.0:1 (large text)
19px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AI is Fueling What's…15.12:13.0:1
#000000
#DCDADD
Pass
h2 Unlock the Full Pote…1.31:13.0:1
#000000
#341C06
Fail
h2 Unlock the Full Pote…1.47:13.0:1
#000000
#272B2C
Fail
h2 FY25 Impact Report: …15.12:13.0:1
#000000
#DCDADD
Pass
h2 Product Sustainabili…15.12:13.0:1
#000000
#DCDADD
Pass
h2 PTC for Startups: CA…15.12:13.0:1
#000000
#DCDADD
Pass
h2 Deliver more value t…15.12:13.0:1
#000000
#DCDADD
Pass
h2 Digital thread: Esse…15.12:13.0:1
#000000
#DCDADD
Pass
h2 Brands you rely on, …15.12:13.0:1
#000000
#DCDADD
Pass
h2 Committed to your su…15.12:13.0:1
#000000
#DCDADD
Pass
h3 PTC named outright L…1.74:13.0:1
#000000
#333735
Fail
h3 Enterprise ALM accel…2.16:13.0:1
#000000
#3F4548
Fail
h3 PTC launches Service…15.12:13.0:1
#000000
#DCDADD
Pass
h3 PTC named a leader i…15.12:13.0:1
#000000
#DCDADD
Pass
h3 Tune in to Speaking …15.12:13.0:1
#000000
#DCDADD
Pass
h3 Manage product compl…15.12:13.0:1
#000000
#DCDADD
Pass
h3 Reduce costs by tran…15.12:13.0:1
#000000
#DCDADD
Pass
h3 Deliver high quality…15.12:13.0:1
#000000
#DCDADD
Pass
h3 Drive growth and inn…15.12:13.0:1
#000000
#DCDADD
Pass
h3 Transform the custom…15.12:13.0:1
#000000
#DCDADD
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
20 headings
PASS
20 headings
Info::
Single H1 present
  • H2 Unlock the Full Potential of Your Engineering Data With AI
  • H3 PTC named outright Leader for enterprise PLM
  • H3 Enterprise ALM accelerates the pace of innovation—see how
  • H2 Unlock the Full Potential of Your Service Operations With AI
  • H3 PTC launches ServiceMax AI
  • H3 PTC named a leader in IDC Marketscape for SLM
  • H3 Tune in to Speaking of Service
  • H1 AI is Fueling What's Possible in Product Development
  • H2 FY25 Impact Report: Read about our ongoing sustainability efforts
  • H2 Product Sustainability For Dummies, PTC Special Edition
  • H2 PTC for Startups: CAD, PLM, ALM at no cost for qualifying startups. Apply Now!
  • H2 Deliver more value through your products
  • H3 Manage product complexity with the right solutions
  • H3 Reduce costs by transforming your product development processes
  • H3 Deliver high quality products with consistency
  • H3 Drive growth and innovation
  • H3 Transform the customer experience
  • H2 Digital thread: Essential enabler of digital transformation
  • H2 Brands you rely on, rely on PTC
  • H2 Committed to your success
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
2 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
23 images 21 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 21 passed
PASS
91

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
AI assistant body.background-white > q-focus-sentinel > div
After AI assistant body.background-white > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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.

Names and labels

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#jumbotron-tile-1 > a.link-overlay div#jumbotron-tile-1 > a.link-overlay
div#jumbotron-tile-2 > a.link-overlay div#jumbotron-tile-2 > a.link-overlay
div#jumbotron-tile-3 > a.link-overlay div#jumbotron-tile-3 > a.link-overlay
div.card-links > div.card-section > div#homepage-video-background-cta-1 > a.link-cover div.card-links > div.card-section > div#homepage-video-background-cta-1 > a.link-cover
div.card-links > div.card-section > div#homepage-video-background-cta-2 > a.link-cover div.card-links > div.card-section > div#homepage-video-background-cta-2 > a.link-cover
div.card-links > div.card-section > div#homepage-video-background-cta-3 > a.link-cover div.card-links > div.card-section > div#homepage-video-background-cta-3 > a.link-cover
div.card-links > div.card-section > div#homepage-video-background-cta-4 > a.link-cover div.card-links > div.card-section > div#homepage-video-background-cta-4 > a.link-cover

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

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.hydrated html.hydrated

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
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
○`[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 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
○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
○Form elements have associated labels
○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.
○`<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.
○Identical links have the same purpose.
○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