Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Alt Text Quality

Action

9 of 32 images have issues

FIX

9 of 32 images have issues

9 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

9 image-in-link without alt text

An image inside a link with no alt creates an empty link.

21 decorative image(s) correctly marked

2 image(s) with good alt text

32 images 2 good alt text 21 decorative 9 missing

Issue	Count
missing	9 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

9 issue(s) across 88 links and 3 buttons

FIX

9 issue(s) across 88 links and 3 buttons

9 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://facebook.com; https://reactjs.org; https://jestjs.io; https://yarnpkg.com; https://babeljs.io; https://webpack.js.org/; https://dropbox.com/; http://danger.systems/js/; https://storybook.js.org/

5 image-only link(s) without alt text

14 link(s) open in new tab without warning

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

Got: https://opencollective.com/prettier; https://github.com/prettier/prettier; https://tidelift.com/subscription/pkg/npm-prettier?utm_source=npm-prettier&utm_medium=referral&utm_campaign=website; https://github.com/prettier/prettier/edit/main/website/data/editors.yml; https://2021.stateofjs.com/en-US/other-tools/#utilities; https://2020.stateofjs.com/en-US/other-tools/#utilities; https://github.com/prettier/prettier/network/dependents; https://www.npmjs.com/browse/depended/prettier; https://www.netlify.com; http://stackoverflow.com/questions/tagged/prettier (+4 more)

60 link(s) with descriptive text

88 links

9 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	Prettier	img no alt	Add alt attribute to the image
https://opencollective.com/prettier	Donate	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier	GitHub repository	new tab	Add '(opens in new tab)' to text
https://tidelift.com/subscription/pkg/np…	PRETTIER FOR ENTERPRISE	new tab	Add '(opens in new tab)' to text
https://sentry.shop/products/syntax-pret…	Limited edition tshirts are no…	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier/edi…	Send a PR	new tab	Add '(opens in new tab)' to text
https://facebook.com	(empty)	empty	Add link text or aria-label
https://reactjs.org	(empty)	empty	Add link text or aria-label
https://jestjs.io	(empty)	empty	Add link text or aria-label
https://yarnpkg.com	(empty)	empty	Add link text or aria-label
https://babeljs.io	(empty)	empty	Add link text or aria-label
https://webpack.js.org/	(empty)	empty	Add link text or aria-label
https://dropbox.com/	(empty)	empty	Add link text or aria-label
http://danger.systems/js/	(empty)	empty	Add link text or aria-label
https://storybook.js.org/	(empty)	empty	Add link text or aria-label
https://2021.stateofjs.com/en-US/other-t…	Statistic for utility tools in…	new tab	Add '(opens in new tab)' to text
https://2021.stateofjs.com/en-US/other-t…	More than 83% of respondents t…	new tab	Add '(opens in new tab)' to text
https://2020.stateofjs.com/en-US/other-t…	More than 70% of respondents t…	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier	Prettier on GitHub	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier/net…	Check Them Out	new tab	Add '(opens in new tab)' to text
https://npmjs.com/package/prettier	Prettier on NPM	new tab	Add '(opens in new tab)' to text
https://www.npmjs.com/browse/depended/pr…	See every dependent npm packag…	new tab	Add '(opens in new tab)' to text
https://www.netlify.com	Deploys by Netlify	new tab	Add '(opens in new tab)' to text
http://stackoverflow.com/questions/tagge…	Stack Overflow	new tab	Add '(opens in new tab)' to text
https://x.com/PrettierCode	@PrettierCode on X	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier	GitHub	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier/iss…	Issues	new tab	Add '(opens in new tab)' to text
https://github.com/prettier/prettier	Star this project on GitHub	new tab	Add '(opens in new tab)' to text

63 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://facebook.com; https://reactjs.org; https://jestjs.io; https://yarnpkg.com; https://babeljs.io; https://webpack.js.org/; https://dropbox.com/; http://danger.systems/js/; https://storybook.js.org/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://opencollective.com/prettier; https://github.com/prettier/prettier; https://tidelift.com/subscription/pkg/npm-prettier?utm_source=npm-prettier&utm_medium=referral&utm_campaign=website; https://github.com/prettier/prettier/edit/main/website/data/editors.yml; https://2021.stateofjs.com/en-US/other-tools/#utilities; https://2020.stateofjs.com/en-US/other-tools/#utilities; https://github.com/prettier/prettier/network/dependents; https://www.npmjs.com/browse/depended/prettier; https://www.netlify.com; http://stackoverflow.com/questions/tagged/prettier (+4 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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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 Present

✗ Multiple Sizes Missing

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: Prettier

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name Prettier ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode browser ✗

Name Prettier Display Mode browser Theme Color #1A2B34 Icons 1 icon(s)

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

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

Heading Hierarchy

14 headings

REVIEW

14 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 What is Prettier?
H2 Why?
H2 Works with the Tools You Use
H2 Editor Support
H3 Emacs
H3 Espresso
H3 Nova
H3 Sublime Text
H3 Vim
H3 Visual Studio
H3 VS Code
H3 WebStorm
H2 Used By People You Rely On
H2 Established in the Ecosystem

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 Page Not Found · Prettier ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 Works with the Tools You Use

1.27:1

#000000

#182025

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Editor Support

1.27:1

#000000

#182025

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Used By People You Rely On

1.27:1

#000000

#182025

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Established in the Ecosystem

1.27:1

#000000

#182025

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Emacs

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Espresso

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Nova

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sublime Text

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vim

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Visual Studio

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 VS Code

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 WebStorm

1.27:1

#000000

#182025

needs 3.0:1 (large text)

19px · bottom of viewport

title Prettier · Opinionated Code Formatter �…

1.44:1

#000000

#1A2B34

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.44:1

#000000

#1A2B34

needs 4.5:1 (normal text)

16px · top of page (header area)

a stable

3.05:1

#000000

#72543E

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a next

1.44:1

#000000

#1A2B34

needs 4.5:1 (normal text)

16px · above the fold

a stable

1.44:1

#000000

#1A2B34

needs 4.5:1 (normal text)

16px · above the fold

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)

Element	Ratio	Required	FG	BG	Result
h2 What is Prettier?	12.27:1	3.0:1	#000000	#F8BC45	Pass
h2 Why?	12.27:1	3.0:1	#000000	#F8BC45	Pass
h2 Works with the Tools…	1.27:1	3.0:1	#000000	#182025	Fail
h2 Editor Support	1.27:1	3.0:1	#000000	#182025	Fail
h2 Used By People You R…	1.27:1	3.0:1	#000000	#182025	Fail
h2 Established in the E…	1.27:1	3.0:1	#000000	#182025	Fail
h3 Emacs	1.27:1	3.0:1	#000000	#182025	Fail
h3 Espresso	1.27:1	3.0:1	#000000	#182025	Fail
h3 Nova	1.27:1	3.0:1	#000000	#182025	Fail
h3 Sublime Text	1.27:1	3.0:1	#000000	#182025	Fail
h3 Vim	1.27:1	3.0:1	#000000	#182025	Fail
h3 Visual Studio	1.27:1	3.0:1	#000000	#182025	Fail
h3 VS Code	1.27:1	3.0:1	#000000	#182025	Fail
h3 WebStorm	1.27:1	3.0:1	#000000	#182025	Fail
title Prettier · Opiniona…	1.44:1	4.5:1	#000000	#1A2B34	Fail
a Skip to main content	1.44:1	4.5:1	#000000	#1A2B34	Fail
b Prettier	4.51:1	3.0:1	#000000	#9E6843	Pass
a stable	3.05:1	4.5:1	#000000	#72543E	Fail
a next	1.44:1	4.5:1	#000000	#1A2B34	Fail
a stable	1.44:1	4.5:1	#000000	#1A2B34	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+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 22 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.

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
See others `div.container > div.userSectionButtonContainer_A7EE > div > a.button`
Check Them Out `div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > div > a.button`
See them all `div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > div > a.button`

These are opportunities to improve the legibility of your content.

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.plugin-pages `html.plugin-pages`

These items highlight common accessibility best practices.

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
See them all `div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > div > a.button`

○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

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

●Elements use only permitted ARIA attributes

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Skip links are focusable.

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

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

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