Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Alt Text Quality

Action

6 of 11 images have issues

FIX

6 of 11 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 image-in-link without alt text

An image inside a link with no alt creates an empty link.

5 image(s) with good alt text

11 images 5 good alt text 6 missing

Issue	Count
missing	6 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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: #144d3f

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Link & Button Quality

1 issue(s) across 195 links and 0 buttons

REVIEW

1 issue(s) across 195 links and 0 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /en/user/

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://hosted.weblate.org/; https://hosted.weblate.org/

192 link(s) with descriptive text

195 links

1 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en/user/	(empty)	empty	Add link text or aria-label
https://hosted.weblate.org/	Go Weblate!	new tab	Add '(opens in new tab)' to text
https://docs.weblate.org/en/latest/admin…	Continuous Localization Au…	img no alt	Add alt attribute to the image
https://docs.weblate.org/en/latest/user/…	Quality Checks Customizabl…	img no alt	Add alt attribute to the image
https://docs.weblate.org/en/latest/faq.h…	Attribution All translator…	img no alt	Add alt attribute to the image
/en/hosting/	Hosting Plans Use Weblate …	img no alt	Add alt attribute to the image
/en/download/	Cloud Ready Comes with app…	img no alt	Add alt attribute to the image
https://github.com/WeblateOrg/weblate	Libre Software Copylefted;…	img no alt	Add alt attribute to the image
https://hosted.weblate.org/	Go Weblate!	new tab	Add '(opens in new tab)' to text

192 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/en/user/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://hosted.weblate.org/; https://hosted.weblate.org/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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

5 icon(s) detected

REVIEW

5 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 Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Weblate

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Weblate ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Weblate Display Mode standalone Theme Color #144d3f Background Color #144d3f Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

h1 Web-based

2.09:1

#000000

#0F4A46

needs 3.0:1 (large text)

32px · above the fold

h1 localization

2.06:1

#000000

#0F4946

needs 3.0:1 (large text)

32px · mid-page

title Weblate - web-based localization

2.16:1

#000000

#114C4A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Weblate

2.19:1

#000000

#124D4B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Go Weblate!

2.19:1

#000000

#124D4C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Features

2.41:1

#000000

#14544D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Download

2.40:1

#000000

#12544E

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Web-based	2.09:1	3.0:1	#000000	#0F4A46	Fail
h1 localization	2.06:1	3.0:1	#000000	#0F4946	Fail
h2 Weblate localizes th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Robust feature set	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Users and Supporters	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 —it’s up to you	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Continuous Localizat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Quality Checks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Attribution	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hosting Plans	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cloud Ready	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Libre Software	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Premium Cloud	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Self-hosted	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Gratis Weblate	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Weblate - web-based …	2.16:1	4.5:1	#000000	#114C4A	Fail
a Weblate	2.19:1	4.5:1	#000000	#124D4B	Fail
a Go Weblate!	2.19:1	4.5:1	#000000	#124D4C	Fail
a Features	2.41:1	4.5:1	#000000	#14544D	Fail
a Download	2.40:1	4.5:1	#000000	#12544E	Fail

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 85/100 — 2 failing, 10 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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.f-box > a > div.icon > img `div.f-box > a > div.icon > img`
div.f-box > a > div.icon > img `div.f-box > a > div.icon > img`
div.f-box > a > div.icon > img `div.f-box > a > div.icon > img`
div.f-box > a > div.icon > img `div.f-box > a > div.icon > img`
div.f-box > a > div.icon > img `div.f-box > a > div.icon > img`
div.f-box > a > div.icon > img `div.f-box > a > div.icon > img`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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

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

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

●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

○Background and foreground colors have a sufficient contrast ratio

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

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

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 Web-based continuous localization
H2 Weblate localizes the world
H2 Robust feature set
H3 Continuous Localization
H3 Quality Checks
H3 Attribution
H3 Hosting Plans
H3 Cloud Ready
H3 Libre Software
H2 Users and Supporters
H2 Gratis or Premium—it’s up to you
H3 Premium Cloud
H3 Self-hosted
H3 Gratis Weblate

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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