Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 2 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA

h1 Cygwin

1.76:1

#000000

#373737

needs 3.0:1 (large text)

32px · bottom of viewport

h1 This is the home of the Cygwin project

1.76:1

#000000

#373737

needs 3.0:1 (large text)

32px · bottom of viewport

h2 What...

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ...is it?

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ...isn't it?

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cygwin version

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Note to users of older Windows versions

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Installing Cygwin

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support for Cygwin

1.76:1

#000000

#373737

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Cygwin	1.76:1	3.0:1	#000000	#373737	Fail
h1 This is the home of …	1.76:1	3.0:1	#000000	#373737	Fail
h2 What...	1.76:1	3.0:1	#000000	#373737	Fail
h2 ...is it?	1.76:1	3.0:1	#000000	#373737	Fail
h2 ...isn't it?	1.76:1	3.0:1	#000000	#373737	Fail
h2 Cygwin version	1.76:1	3.0:1	#000000	#373737	Fail
h2 Note to users of old…	1.76:1	3.0:1	#000000	#373737	Fail
h2 Installing Cygwin	1.76:1	3.0:1	#000000	#373737	Fail
h2 Support for Cygwin	1.76:1	3.0:1	#000000	#373737	Fail
title Cygwin	18.59:1	4.5:1	#000000	#F1F1F1	Pass
a Cygwin	17.14:1	4.5:1	#000000	#E8E8E8	Pass
a Install Cygwin	9.04:1	4.5:1	#000000	#AAAAAA	Pass
a Update Cygwin	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Search Packages	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Licensing Terms	19.43:1	4.5:1	#000000	#F6F6F6	Pass
a Cygwin/X	18.59:1	4.5:1	#000000	#F1F1F1	Pass
a Community	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Reporting Problems	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Mailing Lists	16.21:1	4.5:1	#000000	#E2E2E2	Pass
a Newsgroups	19.43:1	4.5:1	#000000	#F6F6F6	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.

Lighthouse Accessibility Audits

Action

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

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
Cygwin `div#navbar > ul > li > a`
Install Cygwin `li.nohover > ul > li > a`
Update Cygwin `li.nohover > ul > li > a`
Search Packages `li.nohover > ul > li > a`
Licensing Terms `li.nohover > ul > li > a`
Cygwin/X `div#navbar > ul > li > a`
Community `div#navbar > ul > li > a`
Reporting Problems `li.nohover > ul > li > a`
Mailing Lists `li.nohover > ul > li > a`
Newsgroups `li.nohover > ul > li > a`
IRC channels `li.nohover > ul > li > a`
Gold Stars `li.nohover > ul > li > a.gold`
Mirror Sites `li.nohover > ul > li > a`
Donations `li.nohover > ul > li > a`
Documentation `div#navbar > ul > li > a`
FAQ `li.nohover > ul > li > a`
User's Guide `li.nohover > ul > li > a`
API Reference `li.nohover > ul > li > a`
Acronyms `li.nohover > ul > li > a`
Contributing `div#navbar > ul > li > a`
Source in Git `li.nohover > ul > li > a`
Cygwin DLL `li.nohover > ul > li > a`
Cygwin Packages `li.nohover > ul > li > a`
Cygwin Apps `li.nohover > ul > li > a`
Related Sites `div#navbar > ul > li > a`

These are opportunities to improve the legibility of your content.

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
Cygwin `div#navbar > ul > li > a`
Install Cygwin `li.nohover > ul > li > a`
Update Cygwin `li.nohover > ul > li > a`
Search Packages `li.nohover > ul > li > a`
Licensing Terms `li.nohover > ul > li > a`
Community `div#navbar > ul > li > a`
Reporting Problems `li.nohover > ul > li > a`
Mailing Lists `li.nohover > ul > li > a`
Newsgroups `li.nohover > ul > li > a`
IRC channels `li.nohover > ul > li > a`
Gold Stars `li.nohover > ul > li > a.gold`
Mirror Sites `li.nohover > ul > li > a`
Donations `li.nohover > ul > li > a`
FAQ `li.nohover > ul > li > a`
User's Guide `li.nohover > ul > li > a`
API Reference `li.nohover > ul > li > a`
Acronyms `li.nohover > ul > li > a`
Contributing `div#navbar > ul > li > a`
Source in Git `li.nohover > ul > li > a`
Cygwin DLL `li.nohover > ul > li > a`
Cygwin Packages `li.nohover > ul > li > a`
Cygwin Apps `li.nohover > ul > li > a`

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

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-hidden="true"]` is not present on the document `<body>`

●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

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

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

○Image elements have `[alt]` attributes

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

○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

○Identical links have the same purpose.

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

Heading Hierarchy

9 headings

PASS

9 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Cygwin
H1 This is the home of the Cygwin project duplicate H1
H2 What...
H2 ...is it?
H2 ...isn't it?
H2 Cygwin version
H2 Note to users of older Windows versions
H2 Installing Cygwin
H2 Support for Cygwin

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

39 links, 0 buttons — all OK

PASS

39 links, 0 buttons — all OK

39 link(s) with descriptive text

39 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

39 links and buttons have descriptive text

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