Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Landmark Structure

Action

1 landmarks

FIX

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

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

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

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

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: #08c

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

16 headings

REVIEW

16 headings

No H1 heading found

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

H2 A simple, lightweight distribution
H3 Latest News
H4 kea >= 1:3.0.3-6 update requires manual intervention
H4 iptables now defaults to the nft backend
H4 NVIDIA 590 driver drops Pascal and lower support; main packages switch to Open Kernel Modules
H4 .NET packages may require manual intervention
H4 waydroid >= 1.5.4-3 update may require manual intervention
H3 Older News
H3 Recent Updates (more)
H4 Documentation
H4 Community
H4 Support
H4 Tools
H4 Development
H4 People
H4 More Resources

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

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only

title Arch Linux

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

a Arch Linux

2.56:1

#000000

#4F4F4F

needs 4.5:1 (normal text)

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

a Home

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

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 A simple, lightweigh…	18.59:1	3.0:1	#000000	#ECF2F5	Pass
h3 Recent Updates	19.87:1	3.0:1	#000000	#F6F9FC	Pass
title Arch Linux	1.66:1	4.5:1	#000000	#333333	Fail
a Arch Linux	2.56:1	4.5:1	#000000	#4F4F4F	Fail
a Home	1.66:1	4.5:1	#000000	#333333	Fail
a Packages	13.85:1	4.5:1	#000000	#A8D9F0	Pass
a Forums	7.93:1	4.5:1	#000000	#33AADD	Pass
a Wiki	19.87:1	4.5:1	#000000	#F6F9FC	Pass
a GitLab	12.47:1	4.5:1	#000000	#C4C8CB	Pass
a Security	6.86:1	4.5:1	#000000	#909495	Pass
a AUR	18.59:1	4.5:1	#000000	#ECF2F5	Pass
a Download	10.62:1	4.5:1	#000000	#B5B9BB	Pass
p You've reached the w…	13.49:1	4.5:1	#000000	#CBD0D2	Pass
strong Arch Linux	15.34:1	3.0:1	#000000	#D8DDE0	Pass
p , a lightweight …	18.59:1	4.5:1	#000000	#ECF2F5	Pass
p Currently we have of…	11.34:1	4.5:1	#000000	#BBBFC1	Pass
a community-operated p…	19.33:1	4.5:1	#000000	#F2F6F9	Pass
p that grows in size a…	10.19:1	4.5:1	#000000	#B2B5B7	Pass
p Our strong community…	19.87:1	4.5:1	#000000	#F6F9FC	Pass
a forums	19.87:1	4.5:1	#000000	#F6F9FC	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

Score 86/100 — 3 failing, 16 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
Packages `div#archnavbarmenu > ul#archnavbarlist > li#anb-packages > a`
Forums `div#archnavbarmenu > ul#archnavbarlist > li#anb-forums > a`
Wiki `div#archnavbarmenu > ul#archnavbarlist > li#anb-wiki > a`
GitLab `div#archnavbarmenu > ul#archnavbarlist > li#anb-gitlab > a`
Security `div#archnavbarmenu > ul#archnavbarlist > li#anb-security > a`
AUR `div#archnavbarmenu > ul#archnavbarlist > li#anb-aur > a`
Download `div#archnavbarmenu > ul#archnavbarlist > li#anb-download > a`
community-operated package repository `div#content-left > div#intro > p > a`
forums `div#content-left > div#intro > p > a`
mailing lists `div#content-left > div#intro > p > a`
wiki `div#content-left > div#intro > p > a`
Learn more... `div#content-left > div#intro > p.readmore > a`
Latest News `div#content-left > div#news > h3 > a`
kea >= 1:3.0.3-6 update requires manual intervention `div#content-left > div#news > h4 > a`
iptables now defaults to the nft backend `div#content-left > div#news > h4 > a`
NVIDIA 590 driver drops Pascal and lower support; main packages switch to Open … `div#content-left > div#news > h4 > a`
.NET packages may require manual intervention `div#content-left > div#news > h4 > a`
waydroid >= 1.5.4-3 update may require manual intervention `div#content-left > div#news > h4 > a`
Older News `div#content-left > div#news > h3 > a`
dovecot >= 2.4 requires manual intervention `div#news > dl.newslist > dd > a`
Recent service outages `div#news > dl.newslist > dd > a`
zabbix >= 7.4.1-2 may require manual intervention `div#news > dl.newslist > dd > a`
linux-firmware >= 20250613.12fe085f-5 upgrade requires manual intervention `div#news > dl.newslist > dd > a`
Plasma 6.4.0 will need manual intervention if you are on X11 `div#news > dl.newslist > dd > a`
Transition to the new WoW64 wine and wine-staging `div#news > dl.newslist > dd > a`
Valkey to replace Redis in the [extra] Repository `div#news > dl.newslist > dd > a`
Cleaning up old repositories `div#news > dl.newslist > dd > a`
Glibc 2.41 corrupting Discord installation `div#news > dl.newslist > dd > a`
Critical rsync security release 3.4.0 `div#news > dl.newslist > dd > a`
Package Search: `div#pkgsearch > form#pkgsearch-form > fieldset > label`
more `div#pkg-updates > h3 > span.more > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
Wiki `div#nav-sidebar > ul > li > a`
Manual Pages `div#nav-sidebar > ul > li > a`
Installation Guide `div#nav-sidebar > ul > li > a`
Mailing Lists `div#nav-sidebar > ul > li > a`
IRC Channels `div#nav-sidebar > ul > li > a`
Planet Arch `div#nav-sidebar > ul > li > a`
International Communities `div#nav-sidebar > ul > li > a`
Donate `div#nav-sidebar > ul > li > a`
T-shirts via Freewear `div#nav-sidebar > ul > li > a`
T-shirts via HELLOTUX `div#nav-sidebar > ul > li > a`
Mirrorlist Updater `div#nav-sidebar > ul > li > a`
Mirror List `div#nav-sidebar > ul > li > a`
Mirror Status `div#nav-sidebar > ul > li > a`
Getting involved `div#nav-sidebar > ul > li > a`
Dev Blog `div#nav-sidebar > ul > li > a`
Projects in Git `div#nav-sidebar > ul > li > a`
Developer Wiki `div#nav-sidebar > ul > li > a`
Package Groups `div#nav-sidebar > ul > li > a`
Todo Lists `div#nav-sidebar > ul > li > a`
ISO Release List `div#nav-sidebar > ul > li > a`
Visualizations `div#nav-sidebar > ul > li > a`
Differences Reports `div#nav-sidebar > ul > li > a`
Developers `div#nav-sidebar > ul > li > a`
Package Maintainers `div#nav-sidebar > ul > li > a`
Support Staff `div#nav-sidebar > ul > li > a`
Developer Fellows `div#nav-sidebar > ul > li > a`
Package Maintainer Fellows `div#nav-sidebar > ul > li > a`
Support Staff Fellows `div#nav-sidebar > ul > li > a`
Signing Master Keys `div#nav-sidebar > ul > li > a`
Press Coverage `div#nav-sidebar > ul > li > a`
Logos & Artwork `div#nav-sidebar > ul > li > a`
News Archives `div#nav-sidebar > ul > li > a`
RSS Feeds `div#nav-sidebar > ul > li > a`
Judd Vinet `div#content > div#footer > p > a`
Aaron Griffin `div#content > div#footer > p > a`
Levente Polyák `div#content > div#footer > p > a`
trademarks `div#content > div#footer > p > 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
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
x86_64 `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
any `tbody > tr > td.pkg-arch > a`
Wiki `div#nav-sidebar > ul > li > a`
Manual Pages `div#nav-sidebar > ul > li > a`
Installation Guide `div#nav-sidebar > ul > li > a`
Mailing Lists `div#nav-sidebar > ul > li > a`
IRC Channels `div#nav-sidebar > ul > li > a`
Planet Arch `div#nav-sidebar > ul > li > a`
Donate `div#nav-sidebar > ul > li > a`
T-shirts via Freewear `div#nav-sidebar > ul > li > a`
T-shirts via HELLOTUX `div#nav-sidebar > ul > li > a`
Mirrorlist Updater `div#nav-sidebar > ul > li > a`
Mirror List `div#nav-sidebar > ul > li > a`
Mirror Status `div#nav-sidebar > ul > li > a`
Getting involved `div#nav-sidebar > ul > li > a`
Dev Blog `div#nav-sidebar > ul > li > a`
Projects in Git `div#nav-sidebar > ul > li > a`
Developer Wiki `div#nav-sidebar > ul > li > a`
Package Groups `div#nav-sidebar > ul > li > a`
Todo Lists `div#nav-sidebar > ul > li > a`
ISO Release List `div#nav-sidebar > ul > li > a`
Visualizations `div#nav-sidebar > ul > li > a`
Differences Reports `div#nav-sidebar > ul > li > a`
Developers `div#nav-sidebar > ul > li > a`
Package Maintainers `div#nav-sidebar > ul > li > a`
Support Staff `div#nav-sidebar > ul > li > a`
Developer Fellows `div#nav-sidebar > ul > li > a`
Package Maintainer Fellows `div#nav-sidebar > ul > li > a`
Support Staff Fellows `div#nav-sidebar > ul > li > a`
Signing Master Keys `div#nav-sidebar > ul > li > a`
Press Coverage `div#nav-sidebar > ul > li > a`
Logos & Artwork `div#nav-sidebar > ul > li > a`
News Archives `div#nav-sidebar > ul > li > a`
RSS Feeds `div#nav-sidebar > 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>`

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○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

○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

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

○Elements with visible text labels have matching accessible names.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

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
#pkgsearch-field	text	Package Search:	for/id

A+

Link & Button Quality

1 issue(s) across 89 links and 0 buttons

PASS

1 issue(s) across 89 links and 0 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /packages/?sort=-last_update ("more")

88 link(s) with descriptive text

89 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/packages/?sort=-last_update	more	generic text	Replace with descriptive text
Before: more Suggested: ?Sort= Last Update

88 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/packages/?sort=-last_update ("more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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