Skip to content
https://brew.sh

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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.
Page Structure — as a screen reader sees it
BANNER header MAIN ASIDE CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found · GitHub Pages ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only
h2 Install Homebrew
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Does Homebrew Do?
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 command documentation
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Further Documentation
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Community Discussion
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Homebrew Blog
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Homebrew Packages
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Analytics Data
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Donate to Homebrew
1.47:1
#000000
on
#2E2A24
needs 3.0:1 (large text)
24px · bottom of viewport
title Homebrew — The Missing Package Manager…
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · top of page (header area)
a Homebrew
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · top of page (header area)
span Search
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · top of page (header area)
label Language
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
option العربية
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
option Azərbaycanca
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
option Беларуская
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
option Български
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
option Català
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
option Čeština
1.47:1
#000000
on
#2E2A24
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Install Homebrew1.47:13.0:1
#000000
#2E2A24
Fail
h2 What Does Homebrew D…1.47:13.0:1
#000000
#2E2A24
Fail
h2 command documentatio…1.47:13.0:1
#000000
#2E2A24
Fail
h2 Further Documentatio…1.47:13.0:1
#000000
#2E2A24
Fail
h2 Community Discussion1.47:13.0:1
#000000
#2E2A24
Fail
h2 Homebrew Blog1.47:13.0:1
#000000
#2E2A24
Fail
h2 Homebrew Packages1.47:13.0:1
#000000
#2E2A24
Fail
h2 Analytics Data1.47:13.0:1
#000000
#2E2A24
Fail
h2 Donate to Homebrew1.47:13.0:1
#000000
#2E2A24
Fail
title Homebrew — The Mis…1.47:14.5:1
#000000
#2E2A24
Fail
a Homebrew1.47:14.5:1
#000000
#2E2A24
Fail
strong The Missing Package …3.66:13.0:1
#000000
#666666
Pass
span Search1.47:14.5:1
#000000
#2E2A24
Fail
label Language1.47:14.5:1
#000000
#2E2A24
Fail
option العربية1.47:14.5:1
#000000
#2E2A24
Fail
option Azərbaycanca1.47:14.5:1
#000000
#2E2A24
Fail
option Беларуская1.47:14.5:1
#000000
#2E2A24
Fail
option Български1.47:14.5:1
#000000
#2E2A24
Fail
option Català1.47:14.5:1
#000000
#2E2A24
Fail
option Čeština1.47:14.5:1
#000000
#2E2A24
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
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 Homebrew
  • H2 Install Homebrew
  • H2 What Does Homebrew Do?
  • H2 brew command documentation
  • H2 Further Documentation
  • H2 Community Discussion
  • H2 Homebrew Blog
  • H2 Homebrew Packages
  • H2 Analytics Data
  • H2 Donate to Homebrew
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#languageselectLanguagearia-label
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 22 passed
PASS
96

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
-c figure.highlight > pre > code.language-bash > span.nt
-fsSL figure.highlight > pre > code.language-bash > span.nt
-l figure.highlight > pre > code.language-bash > span.nt
Formula figure.highlight > pre > code.language-ruby > span.no
"Internet file retriever" figure.highlight > pre > code.language-ruby > span.s2
"https://www.gnu.org/software/wget/" figure.highlight > pre > code.language-ruby > span.s2
"https://ftp.gnu.org/gnu/wget/wget-1.24.5.tar.gz" figure.highlight > pre > code.language-ruby > span.s2
"fa2dc35bab5184ecbc46a9ef83def2aaaa3f4c9f3c97d4bd19dcb07d4da637de" figure.highlight > pre > code.language-ruby > span.s2
"GPL-3.0-or-later" figure.highlight > pre > code.language-ruby > span.s2
"./configure" figure.highlight > pre > code.language-ruby > span.s2
"--prefix= figure.highlight > pre > code.language-ruby > span.s2
"make" figure.highlight > pre > code.language-ruby > span.s2
"install" figure.highlight > pre > code.language-ruby > span.s2
--cask figure.highlight > pre > code.language-bash > span.nt
--cask figure.highlight > pre > code.language-bash > span.nt
docs.brew.sh/Manpage section.group > div.button > p > a
docs.brew.sh section.group > div.button > p > a
Homebrew/discussions section.group > div.button > p > a
brew.sh/blog section.group > div.button > p > a
formulae.brew.sh section.group > div.button > p > a
formulae.brew.sh/analytics section.group > div.button > p > a
Homebrew/brew#donations section.group > div.button > p > a

These are opportunities to improve the legibility of your content.

○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.
●Select elements have associated label elements.
●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 are distinguishable without relying on color.
●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
●Document has a main landmark.
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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.

Send Feedback