Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 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-sq2mlq

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.

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: com.pinterest

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

A+

Landmark Structure

3 landmarks

PASS

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input	text	Search	aria-label

Link & Button Quality

7 links, 2 buttons — all OK

PASS

7 links, 2 buttons — all OK

4 link(s) open in new tab without warning

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

Got: /_/_/about/; /_/_/business/?utm_campaign=pinterest_homepage_blogicon_all_evergreen&utm_med…; /_/_/create/; /_/_/blog/?utm_source=organicpins_pinsite_homepageicon&utm_campaign=pinterest…

3 link(s) with descriptive text

7 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/_/_/about/	About; Opens a new tab	new tab	Add '(opens in new tab)' to text
/_/_/business/?utm_campaign=pinterest_ho…	Businesses; Opens a new tab	new tab	Add '(opens in new tab)' to text
/_/_/create/	Create; Opens a new tab	new tab	Add '(opens in new tab)' to text
/_/_/blog/?utm_source=organicpins_pinsit…	News; Opens a new tab	new tab	Add '(opens in new tab)' to text

5 links and buttons have descriptive text

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

/_/_/about/; /_/_/business/?utm_campaign=pinterest_homepage_blogicon_all_evergreen&utm_med…; /_/_/create/; /_/_/blog/?utm_source=organicpins_pinsite_homepageicon&utm_campaign=pinterest…

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

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Pinterest

192x192 icon present

Display mode: minimal-ui

PWA Install Criteria ✓ Installable

Name Pinterest ✓192×192 icon ✓512×512 icon ✗Start URL /?utm_source=homescreen_icon ✓Display Mode minimal-ui ✓

Name Pinterest Display Mode minimal-ui Theme Color #FFFFFF Background Color #fff Icons 1 icon(s)

A+

Color Contrast (Screenshot)

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

14 pass

Show all checked elements (14)

Element	Ratio	Required	FG	BG	Result
title Pinterest	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div Skip to content	8.92:1	4.5:1	#000000	#A9A9A7	Pass
div Explore	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div When autocomplete re…	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div About	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div ; Opens a new tab	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div Businesses	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div ; Opens a new tab	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div Create	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div ; Opens a new tab	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div News	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div ; Opens a new tab	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div Log in	12.53:1	4.5:1	#000000	#C8C8C6	Pass
div Sign up	12.53:1	4.5:1	#000000	#C8C8C6	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+

Lighthouse Accessibility Audits

Score 97/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.

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
Pinterest App `div.ADXRXN > div.ADXRXN > div.ADXRXN > div.Q3hcOU`
Pinterest App `div.ADXRXN > div.Q3hcOU > div.ADXRXN > a.etmDmh`
div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN `div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN`
div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN `div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN`
div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN `div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN`
div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN `div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN`
div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN `div.ADXRXN > div.H2DtUH > div.oRZ5_s > div.ADXRXN`
Get started here `div.ADXRXN > div.H2DtUH > div.ADXRXN > a.etmDmh`

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

●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

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

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

●Elements use only permitted ARIA attributes

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

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

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