Skip to content
https://caddy.community

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
3
REVIEW
3
PASS
7
INFO
0
Checks
13
7 PASS 3 REVIEW 3 FIX
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 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
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Missing
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="username" id="signin_username">; <input type="password" name="password" id="signin_password">; <input type="submit" id="signin-button">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#signin_usernametext(none)none
#signin_passwordpassword(none)none
#signin-buttonsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="username" id="signin_username">; <input type="password" name="password" id="signin_password">; <input type="submit" id="signin-button">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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 Caddy Community Custom Styling Navigation Homepage Link Search Form
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Caddy Community
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Caddy Community 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name Caddy Community Display Mode standalone Theme Color #fff Background Color #fff Icons 2 icon(s)
A+
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 All latest topics
A+
Alt Text Quality
All 80 images OK
PASS
All 80 images OK
Info::
79 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
80 images 1 good alt text 79 decorative
All images have appropriate alt text.
A+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 light dark Dark theme-color #fff CSS indicators Detected

Detection limited to meta tags and inline styles.

A+
Color Contrast (Screenshot)
20 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.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 All latest topics21.00:13.0:1
#000000
#FFFFFF
Pass
title Caddy Community21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a Wiki21.00:14.5:1
#000000
#FFFFFF
Pass
a Docs21.00:14.5:1
#000000
#FFFFFF
Pass
a GitHub21.00:14.5:1
#000000
#FFFFFF
Pass
a Rules21.00:14.5:1
#000000
#FFFFFF
Pass
span Sign Up21.00:14.5:1
#000000
#FFFFFF
Pass
span Log In21.00:14.5:1
#000000
#FFFFFF
Pass
span 21.00:14.5:1
#000000
#FFFFFF
Pass
span Topics21.00:14.5:1
#000000
#FFFFFF
Pass
span More21.00:14.5:1
#000000
#FFFFFF
Pass
span Categories21.00:14.5:1
#000000
#FFFFFF
Pass
span Announcements21.00:14.5:1
#000000
#FFFFFF
Pass
span Help21.00:14.5:1
#000000
#FFFFFF
Pass
span Showcase21.00:14.5:1
#000000
#FFFFFF
Pass
span Wiki21.00:14.5:1
#000000
#FFFFFF
Pass
span All categories21.00:14.5:1
#000000
#FFFFFF
Pass
span 21.00:14.5:1
#000000
#FFFFFF
Pass
span categories21.00:14.5:1
#000000
#FFFFFF
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 96/100 — 1 failing, 30 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
read more div.topic-item-metadata > div.main-link > a.topic-excerpt > span.topic-excerpt-more
May 2016 div.num > span.age > a > span.relative-date
1h div.num > span.age > a > span.relative-date
7h div.num > span.age > a > span.relative-date
9h div.num > span.age > a > span.relative-date
13h div.num > span.age > a > span.relative-date
1d div.num > span.age > a > span.relative-date
1d div.num > span.age > a > span.relative-date
1d div.num > span.age > a > span.relative-date
2d div.num > span.age > a > span.relative-date
5d div.num > span.age > a > span.relative-date
6d div.num > span.age > a > span.relative-date
9d div.num > span.age > a > span.relative-date
9d div.num > span.age > a > span.relative-date
10d div.num > span.age > a > span.relative-date
12d div.num > span.age > a > span.relative-date
16d div.num > span.age > a > span.relative-date
20d div.num > span.age > a > span.relative-date
21d div.num > span.age > a > span.relative-date
23d div.num > span.age > a > span.relative-date
24d div.num > span.age > a > span.relative-date
24d div.num > span.age > a > span.relative-date
24d div.num > span.age > a > span.relative-date
25d div.num > span.age > a > span.relative-date
25d div.num > span.age > a > span.relative-date
25d div.num > span.age > a > span.relative-date
26d div.num > span.age > a > span.relative-date
26d div.num > span.age > a > span.relative-date
27d div.num > span.age > a > span.relative-date
28d div.num > span.age > a > span.relative-date
28d div.num > span.age > a > span.relative-date

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>`
`[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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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.
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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Uses ARIA roles only on compatible elements
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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.
No element has a `[tabindex]` value greater than 0
`[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.
Image elements do not have `[alt]` attributes that are redundant text.
`<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