Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Link & Button Quality

Action

5 issue(s) across 184 links and 34 buttons

FIX

5 issue(s) across 184 links and 34 buttons

3 link(s) with generic text

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

Got: /platform/ai-agents/ ("Learn more"); /platform/incident-management/ ("Learn more"); /integrations/ ("Learn more")

27 link(s) open in new tab without warning

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

Got: https://developer.pagerduty.com/; https://careers.pagerduty.com/home; https://investor.pagerduty.com/overview/default.aspx; https://university.pagerduty.com; https://community.pagerduty.com/; https://support.pagerduty.com/; /integrations/?search=slack; /integrations/?search=github; /integrations/?search=aws; /integrations/?search=cursor (+17 more)

2 button(s) with no accessible text

154 link(s) with descriptive text

184 links

0 empty

3 generic text

27 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://developer.pagerduty.com/	Developer PlatformCustomize yo…	new tab	Add '(opens in new tab)' to text
https://careers.pagerduty.com/home	Careers	new tab	Add '(opens in new tab)' to text
https://investor.pagerduty.com/overview/…	Investor Relations	new tab	Add '(opens in new tab)' to text
https://university.pagerduty.com	PagerDuty University	new tab	Add '(opens in new tab)' to text
https://community.pagerduty.com/	Community	new tab	Add '(opens in new tab)' to text
https://support.pagerduty.com/	Knowledge Base	new tab	Add '(opens in new tab)' to text
/platform/ai-agents/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Agents
/platform/incident-management/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Incident Management
/integrations/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Integrations
/integrations/?search=slack	Slack	new tab	Add '(opens in new tab)' to text
/integrations/?search=github	GitHub	new tab	Add '(opens in new tab)' to text
/integrations/?search=aws	AWS	new tab	Add '(opens in new tab)' to text
/integrations/?search=cursor	Cursor	new tab	Add '(opens in new tab)' to text
/integrations/?search=datadog	Datadog	new tab	Add '(opens in new tab)' to text
/integrations/?search=zoom	Zoom	new tab	Add '(opens in new tab)' to text
/integrations/?search=jira	Jira	new tab	Add '(opens in new tab)' to text
/integrations/?search=azure	Microsoft Azure	new tab	Add '(opens in new tab)' to text
/integrations/salesforce/	Salesforce	new tab	Add '(opens in new tab)' to text
/integrations/?search=claude	Anthropic Claude	new tab	Add '(opens in new tab)' to text
/integrations/zendesk/	Zendesk	new tab	Add '(opens in new tab)' to text
/integrations/?search=google%20cloud	Google Cloud	new tab	Add '(opens in new tab)' to text
https://developer.pagerduty.com/	Developer Platform	new tab	Add '(opens in new tab)' to text
https://community.pagerduty.com	Community Forum	new tab	Add '(opens in new tab)' to text
https://investor.pagerduty.com/	Investor Relations	new tab	Add '(opens in new tab)' to text
https://status.pagerduty.com/	System Status	new tab	Add '(opens in new tab)' to text
https://support.pagerduty.com	Knowledge Base	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/PagerDuty/	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/pagerduty	X	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/pagerduty/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/pagerdu…	LinkedIn	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

186 links and buttons have descriptive text

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

/platform/ai-agents/ ("Learn more"); /platform/incident-management/ ("Learn more"); /integrations/ ("Learn 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://developer.pagerduty.com/; https://careers.pagerduty.com/home; https://investor.pagerduty.com/overview/default.aspx; https://university.pagerduty.com; https://community.pagerduty.com/; https://support.pagerduty.com/; /integrations/?search=slack; /integrations/?search=github; /integrations/?search=aws; /integrations/?search=cursor (+17 more)

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Icons 2 icon(s)

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title LinkedIn ✓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 Ship faster, resolve smarter, sleep bett…

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Products

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

h2 Template and Prompt Library

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Platform

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Template and Prompt Library

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Solutions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Operational Integrity at FOX

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Company

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About us

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our Impact

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FY25 Impact Report

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 PagerDuty on Tour - On Demand

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Made for teams who want to build, not fi…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The platform for AI-first operations

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built on the industry's deepest data fou…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get agents working for people when it ma…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resolve incidents where you work

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Works with everything you already use

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Over 750 integrations

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Ship faster, resolve…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Products	1.00:1	3.0:1	#000000	#000000	Fail
h2 Template and Prompt …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Platform	1.00:1	3.0:1	#000000	#000000	Fail
h2 Template and Prompt …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Solutions	1.00:1	3.0:1	#000000	#000000	Fail
h2 Operational Integrit…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Company	1.00:1	3.0:1	#000000	#000000	Fail
h2 About us	1.00:1	3.0:1	#000000	#000000	Fail
h2 Our Impact	1.00:1	3.0:1	#000000	#000000	Fail
h2 FY25 Impact Report	1.00:1	3.0:1	#000000	#000000	Fail
h2 Resources	1.00:1	3.0:1	#000000	#000000	Fail
h2 PagerDuty on Tour - …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Made for teams who w…	1.00:1	3.0:1	#000000	#000000	Fail
h2 The platform for AI-…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Built on the industr…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Get agents working f…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Resolve incidents wh…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Works with everythin…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Over 750 integration…	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+

Heading Hierarchy

53 headings

PASS

53 headings

Single H1 present

H2 Products
H3 PagerDuty Operations Cloud
H3 Incident Management
H3 AI at PagerDuty
H3 Automation
H3 AI Agents
H3 Status Pages
H3 PagerDuty Advance
H3 Customer Service Ops
H3 AIOps
H2 Template and Prompt Library
H2 Platform
H3 PagerDuty Operations Cloud
H3 Developer Platform
H3 Professional Services
H3 Security
H3 Enterprise Class
H3 Integrations
H2 Template and Prompt Library
H2 Solutions
H3 Solutions
H3 Use Cases
H3 Industries
H2 Operational Integrity at FOX
H2 Company
H3 Who We Are
H2 About us
H2 Our Impact
H2 FY25 Impact Report
H2 Resources
H3 Resources
H3 Customer Stories
H3 Learning
H2 PagerDuty on Tour - On Demand
H1 Ship faster, resolve smarter, sleep better.
H2 Made for teams who want to build, not firefight
H2 The platform for AI-first operations
H2 Built on the industry's deepest data foundation
H3 12 Billion +
H3 952 Million +
H3 15.9 Million +
H2 Get agents working for people when it matters
H2 Resolve incidents where you work
H2 Works with everything you already use
H2 Over 750 integrations
H2 Proven by the world's leading engineering teams
H2 Why leading teams choose PagerDuty
H2 Ready to shift to autonomous operations?
H2 Platform
H2 Solutions
H2 Resources
H2 Company
H2 Support

A+

Alt Text Quality

All 117 images OK

PASS

All 117 images OK

16 decorative image(s) correctly marked

101 image(s) with good alt text

117 images 101 good alt text 16 decorative

All images have appropriate alt text.

Form Accessibility

1 of 21 controls have issues

PASS

1 of 21 controls have issues

1 control(s) without accessible label

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

Got: <select name="lang-switcher" id="lang-selector">

20 control(s) properly labeled

21 controls

20 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#target-dd-products	radio	Products	none
#target-dd-solutions	radio	Solutions	none
#target-dd-company	radio	Company	none
#target-dd-resources	radio	Resources	none
input	checkbox		none
input	checkbox		none
#target-products-products	radio		none
input	checkbox	Products	none
#target-products-platform	radio		none
input	checkbox	Platform	none
input	checkbox	Solutions	none
input	checkbox	Solutions	none
input	checkbox	Use Cases	none
input	checkbox	Industries	none
input	checkbox	Company	none
input	checkbox	Who We Are	none
input	checkbox	Resources	none
input	checkbox	Resources	none
input	checkbox	Customer Stories	none
input	checkbox	Learning	none
#lang-selector	select	(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

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 27 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.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Change language English Français Deutsch 日本語 `article > user-prefs > footer-lang-select#footer-lang-select > select#lang-selector`

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.

○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

●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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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 have a discernible name

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

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

●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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

○`[lang]` attributes have a valid value

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

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