Skip to content
https://gitea.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
1 navigation landmark(s) detected
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 "Global" MAIN (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
17 headings, 1 skip(s)
REVIEW
17 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Private, Fast, Reliable DevOps Platform
  • H3 Gitea Cloud skipped
  • H3 Gitea Enterprise
  • H2 Dev/Deploy faster
  • H2 Trusted by the world’s most innovative teams
  • H1 Run Gitea Anywhere duplicate H1
  • H2 Test, Deploy Faster
  • H1 Integrated with Your Favorite Tools duplicate H1
  • H2 Testimonials
  • H3 Open Source
  • H3 Enterprise
  • H2 Want product news and updates?
  • H2 Footer
  • H3 Products
  • H3 Support
  • H3 About Us
  • H3 Legal

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Gitea Official Website
2.30:1
#000000
on
#14532D
needs 4.5:1 (normal text)
16px · top of page (header area)
strong Try   Gitea Cloud   ☁️   free for…
2.30:1
#000000
on
#14532D
needs 3.0:1 (large text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Private, Fast, Relia…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Run Gitea Anywhere21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Integrated with Your…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dev/Deploy faster21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by the world…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Test, Deploy Faster21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Testimonials21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Want product news an…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Footer21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Open Source21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Enterprise21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Products21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Support21.00:13.0:1
#000000
#FFFFFF
Pass
h3 About Us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Legal21.00:13.0:1
#000000
#FFFFFF
Pass
title Gitea Official Websi…2.30:14.5:1
#000000
#14532D
Fail
strong Try   Gitea Cloud …2.30:13.0:1
#000000
#14532D
Fail
span →21.00:14.5:1
#000000
#FFFFFF
Pass
span Accelerate your Dev …21.00:14.5:1
#000000
#FFFFFF
Pass
span Gitea21.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.

B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 26 passed
REVIEW
89

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
Docker Pulls div.mx-auto > dl.grid > div.mx-auto > dt.text-base
Github Stars div.mx-auto > dl.grid > div.mx-auto > dt.text-base
Installations div.mx-auto > dl.grid > div.mx-auto > dt.text-base
Contributors div.mx-auto > dl.grid > div.mx-auto > dt.text-base
Dev/Deploy faster div.bg-white > div.mx-auto > div.mx-auto > h2.text-base
GitHub Actions div.relative > dd.mt-2 > span > a.text-main-600
Cargo div.relative > dd.mt-2 > span > a.text-main-600
Chef div.relative > dd.mt-2 > span > a.text-main-600
Composer div.relative > dd.mt-2 > span > a.text-main-600
Conan div.relative > dd.mt-2 > span > a.text-main-600
Conda div.relative > dd.mt-2 > span > a.text-main-600
Container div.relative > dd.mt-2 > span > a.text-main-600
Helm div.relative > dd.mt-2 > span > a.text-main-600
Maven div.relative > dd.mt-2 > span > a.text-main-600
NPM div.relative > dd.mt-2 > span > a.text-main-600
NuGet div.relative > dd.mt-2 > span > a.text-main-600
Pub div.relative > dd.mt-2 > span > a.text-main-600
PyPI div.relative > dd.mt-2 > span > a.text-main-600
RubyGems div.relative > dd.mt-2 > span > a.text-main-600
Vagrant div.relative > dd.mt-2 > span > a.text-main-600
Test, Deploy Faster div.mx-auto > div.lg:ml-auto > div.lg:max-w-lg > h2.text-base
Testimonials div.relative > div.mx-auto > div.mx-auto > h2.text-lg
$19 div > div.ring-gray-200 > p.mt-6 > span.text-xl
[1] ul.text-gray-600 > li.flex > div > a.text-main-600
privacy policy div.mx-auto > div.w-full > p.mt-4 > a.font-semibold
© 2026 CommitGo, Inc. All rights reserved. div.xl:grid > div.space-y-8 > div.mt-16 > p.text-xs

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cargo div.relative > dd.mt-2 > span > a.text-main-600
Chef div.relative > dd.mt-2 > span > a.text-main-600
Composer div.relative > dd.mt-2 > span > a.text-main-600
Conan div.relative > dd.mt-2 > span > a.text-main-600
Conda div.relative > dd.mt-2 > span > a.text-main-600
Container div.relative > dd.mt-2 > span > a.text-main-600
Helm div.relative > dd.mt-2 > span > a.text-main-600
Maven div.relative > dd.mt-2 > span > a.text-main-600
NPM div.relative > dd.mt-2 > span > a.text-main-600
NuGet div.relative > dd.mt-2 > span > a.text-main-600
Pub div.relative > dd.mt-2 > span > a.text-main-600
PyPI div.relative > dd.mt-2 > span > a.text-main-600
RubyGems div.relative > dd.mt-2 > span > a.text-main-600
Vagrant div.relative > dd.mt-2 > span > a.text-main-600
[1] ul.text-gray-600 > li.flex > div > a.text-main-600

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Gitea Cloud div.mt-8 > div.w-80 > div.p-4 > h3.text-center

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●Form elements have associated labels
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●`<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
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○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 a valid value for its `[lang]` attribute
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
9 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
19 images 10 good alt text 9 decorative
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
#email-addressemailEmail addressfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback