Skip to content
https://gohugo.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
3
REVIEW
2
PASS
8
INFO
0
Checks
13
8 PASS 2 REVIEW 3 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 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.
B
Favicon & Branding
11 icon(s) detected
REVIEW
11 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
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
title The world's fastest framework for buildi…
1.07:1
#000000
on
#000E14
needs 4.5:1 (normal text)
16px · top of page (header area)
title The world's fastest framework for buildi…
1.07:1
#000000
on
#000E14
needs 4.5:1 (normal text)
16px · top of page (header area)
a HUGO
4.02:1
#000000
on
#656E71
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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)
ElementRatioRequiredFGBGResult
h1 The world’s fastes…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hugo Sponsors21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hugo Sponsors21.00:13.0:1
#000000
#FFFFFF
Pass
h3 QR code linking to h…21.00:13.0:1
#000000
#FFFFFF
Pass
title The world's fastest …1.07:14.5:1
#000000
#000E14
Fail
title The world's fastest …1.07:14.5:1
#000000
#000E14
Fail
a HUGO4.02:14.5:1
#000000
#656E71
Fail
a News21.00:14.5:1
#000000
#FFFFFF
Pass
a Docs21.00:14.5:1
#000000
#FFFFFF
Pass
a Themes21.00:14.5:1
#000000
#FFFFFF
Pass
a Community21.00:14.5:1
#000000
#FFFFFF
Pass
a GitHub21.00:14.5:1
#000000
#FFFFFF
Pass
div Built with Hugo21.00:14.5:1
#000000
#FFFFFF
Pass
a v0.160.121.00:14.5:1
#000000
#FFFFFF
Pass
span Search docs21.00:14.5:1
#000000
#FFFFFF
Pass
span Search by21.00:14.5:1
#000000
#FFFFFF
Pass
span Star21.00:14.5:1
#000000
#FFFFFF
Pass
span 8769621.00:14.5:1
#000000
#FFFFFF
Pass
span 87.7k21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV MAIN 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

A+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 (empty)
  • H3 QR code linking to https://gohugo.io/
  • H1 The world’s fastest framework for building websites
  • H2 Hugo Sponsors
  • H2 Hugo Sponsors

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
1 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
5 images 4 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearch(Search docs)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page not found | Hugo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Hugo
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Hugo ✓192×192 icon ✓512×512 icon ✗Start URL ./?utm_source=web_app_manifest ✓Display Mode standalone ✓
Name Hugo Display Mode standalone Theme Color #0A1922 Background Color #FFF Icons 7 icon(s)
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 27 passed
PASS
97

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
Star button dl.mt-10 > div.relative > dd.inline > a.text-blue-500
Hugo forums dl.mt-10 > div.relative > dd.inline > a.text-blue-500
release dl.mt-10 > div.relative > dd.inline > a.text-blue-500

These are opportunities to improve the legibility of your content.

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
HUGO body.flex > header.print:hidden > div.relative > a.text-white
○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
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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
○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.

Send Feedback