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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-9vouyb

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.postman.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.postman.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ff6c37

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 ModePartial Dark Mode

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 ✗

Favicon & Branding

15 icon(s) detected

REVIEW

15 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 The AI-native API Platform

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The world's APIs are built and shipped o…

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Product

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 API Network

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Legal and Security

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Company

1.10:1

#000000

#140B1E

needs 3.0:1 (large text)

24px · bottom of viewport

span Home

4.30:1

#000000

#C44734

needs 4.5:1 (normal text)

16px · top of page (header area)

span Product

3.06:1

#000000

#9C3652

needs 4.5:1 (normal text)

16px · top of page (header area)

p Postman Platform

2.32:1

#000000

#78286D

needs 4.5:1 (normal text)

16px · above the fold

p What's New

1.94:1

#000000

#5C1C82

needs 4.5:1 (normal text)

16px · above the fold

p Security

1.71:1

#000000

#451489

needs 4.5:1 (normal text)

16px · above the fold

p Integrations

1.49:1

#000000

#39126E

needs 4.5:1 (normal text)

16px · above the fold

p Explore

1.31:1

#000000

#2D0F54

needs 4.5:1 (normal text)

16px · above the fold

p Postman API Network

1.18:1

#000000

#210D3A

needs 4.5:1 (normal text)

16px · above the fold

p MCP Catalog

1.10:1

#000000

#150B21

needs 4.5:1 (normal text)

16px · above the fold

span Download Postman →

1.09:1

#000000

#130A1D

needs 4.5:1 (normal text)

16px · above the fold

p Design

1.09:1

#000000

#130A1D

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The AI-native API Pl…	1.10:1	3.0:1	#000000	#140B1E	Fail
h2 The world's APIs are…	1.10:1	3.0:1	#000000	#140B1E	Fail
h2 Product	1.10:1	3.0:1	#000000	#140B1E	Fail
h2 API Network	1.10:1	3.0:1	#000000	#140B1E	Fail
h2 Resources	1.10:1	3.0:1	#000000	#140B1E	Fail
h2 Legal and Security	1.10:1	3.0:1	#000000	#140B1E	Fail
h2 Company	1.10:1	3.0:1	#000000	#140B1E	Fail
title Postman: The World's…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Home	4.30:1	4.5:1	#000000	#C44734	Fail
span Product	3.06:1	4.5:1	#000000	#9C3652	Fail
p Postman Platform	2.32:1	4.5:1	#000000	#78286D	Fail
p What's New	1.94:1	4.5:1	#000000	#5C1C82	Fail
p Security	1.71:1	4.5:1	#000000	#451489	Fail
p Integrations	1.49:1	4.5:1	#000000	#39126E	Fail
p Explore	1.31:1	4.5:1	#000000	#2D0F54	Fail
p Postman API Network	1.18:1	4.5:1	#000000	#210D3A	Fail
p MCP Catalog	1.10:1	4.5:1	#000000	#150B21	Fail
span Download Postman →	1.09:1	4.5:1	#000000	#130A1D	Fail
p Design	1.09:1	4.5:1	#000000	#130A1D	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.

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 23 passed

REVIEW

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Product POSTMAN PLATFORM What's New Security Integrations EXPLORE Postman… `nav.font-inter > div.flex > div.items-center > div#mobileNavPanel`

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
Starburst `div.relative > div > div.relative > div.h-full`

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.

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
Try the New Postman `section.relative > div.relative > div.inline-block > a#sign-up-for-free-new-postman`
Sign Up for Free `div.mt-4 > a#sign-up-for-free-homepage > span.GenericButton-module__SZgeuW__content > span.GenericButton-module__SZgeuW__text`
Download Postman `div.mx-auto > div.grid > div.col-span-12 > a.text-[14px]`
Privacy Policy `div.mx-auto > div.grid > div.col-span-12 > a.text-[14px]`
Cookie Preferences `div.mx-auto > div.grid > div.col-span-12 > button.cursor-pointer`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Postman Overview `nav > ul.Footer-module__w_7NBa__ul > li.Footer-module__w_7NBa__li > a.Footer-module__w_7NBa__link`
Terms of Service `nav > ul.Footer-module__w_7NBa__ul > li.Footer-module__w_7NBa__li > a.Footer-module__w_7NBa__link`
Postman Product Terms `nav > ul.Footer-module__w_7NBa__ul > li.Footer-module__w_7NBa__li > a.Footer-module__w_7NBa__link`
Customer Stories `nav > ul.Footer-module__w_7NBa__ul > li.Footer-module__w_7NBa__li > a.Footer-module__w_7NBa__link`
Cookie Preferences `div.mx-auto > div.grid > div.col-span-12 > button.cursor-pointer`

○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

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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Identical links have the same purpose.

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

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

7 <nav> landmark(s) found

1 of 7 <nav> elements are unlabeled

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

No banner (header) landmark

Skip navigation link present

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

A+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H1 The AI-native API Platform
H2 The world's APIs are built and shipped on Postman.
H2 Product
H2 API Network
H2 Resources
H2 Legal and Security
H2 Company

A+

Alt Text Quality

All 45 images OK

PASS

All 45 images OK

12 decorative image(s) correctly marked

33 image(s) with good alt text

45 images 33 good alt text 12 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

149 links, 8 buttons — all OK

PASS

149 links, 8 buttons — all OK

11 link(s) open in new tab without warning

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

Got: https://buildwithfern.com?utm_source=postman-product-dropdown; https://discord.com/invite/pqf9eVQwf7; https://buildwithfern.com?utm_source=postman-product-dropdown; https://discord.com/invite/pqf9eVQwf7; https://x.com/getpostman; https://www.linkedin.com/company/postman-platform; https://github.com/postmanlabs; https://www.youtube.com/postman; https://www.instagram.com/getpostman; https://discord.gg/rKZgwpZqqV (+1 more)

138 link(s) with descriptive text

149 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://buildwithfern.com?utm_source=pos…	FernPublish API docs and SDKs	new tab	Add '(opens in new tab)' to text
https://discord.com/invite/pqf9eVQwf7	Discord	new tab	Add '(opens in new tab)' to text
https://buildwithfern.com?utm_source=pos…	FernPublish API docs and SDKs	new tab	Add '(opens in new tab)' to text
https://discord.com/invite/pqf9eVQwf7	Discord	new tab	Add '(opens in new tab)' to text
https://x.com/getpostman	Follow Postman on X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/postman…	Follow Postman on Linked In	new tab	Add '(opens in new tab)' to text
https://github.com/postmanlabs	Contribute to Postman on Git H…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/postman	Watch our Postman You Tube cha…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/getpostman	Follow Postman on Instagram	new tab	Add '(opens in new tab)' to text
https://discord.gg/rKZgwpZqqV	Follow Postman on Discord	new tab	Add '(opens in new tab)' to text
https://privacy.postman.com/policies/	Read more about Postman's priv…	new tab	Add '(opens in new tab)' to text

146 links and buttons have descriptive text

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

https://buildwithfern.com?utm_source=postman-product-dropdown; https://discord.com/invite/pqf9eVQwf7; https://buildwithfern.com?utm_source=postman-product-dropdown; https://discord.com/invite/pqf9eVQwf7; https://x.com/getpostman; https://www.linkedin.com/company/postman-platform; https://github.com/postmanlabs; https://www.youtube.com/postman; https://www.instagram.com/getpostman; https://discord.gg/rKZgwpZqqV (+1 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

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