Skip to content
https://libreoffice.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 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 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
5 landmarks
REVIEW
5 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
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) ASIDE 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

C
Form Accessibility
Action
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="languages-site-header-fallback-nav">; <input type="search" id="searchInput">; <select id="languages-site-footer-fallback-nav">
Info::
2 control(s) properly labeled
5 controls
2 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#languages-site-header-inputtextLanguage:for/id
#languages-site-footer-inputtextLanguage:for/id
#searchInputsearch(none)none
#languages-site-footer-fallback-navselect(none)none
#languages-site-header-fallback-navselect(none)none

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

<select id="languages-site-header-fallback-nav">; <input type="search" id="searchInput">; <select id="languages-site-footer-fallback-nav">

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
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 passed
REVIEW
88

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
DONATE nav.nav-main > ul > li > a.button
JOIN OUR COMMUNITY section#dl-join > div#dl-join-buttons > p > a.button
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Ilmari Lauhakangas section#join_our_community > div.opportunities > p > a
DESIGN div.opportunities > ul > li > a
LOCALISATION div.opportunities > ul > li > a
MARKETING div.opportunities > ul > li > a
DOCUMENTATION div.opportunities > ul > li > a
DEVELOPMENT div.opportunities > ul > li > a
INFRASTRUCTURE div.opportunities > ul > li > a
QUALITY ASSURANCE div.opportunities > ul > li > a
Join TDF section#join_our_community > div.opportunities > p > a
ZDNET section#what_people_are_saying > ul.fullWidth-center > li > a
TechRadar section#what_people_are_saying > ul.fullWidth-center > li > a
DONATE div.fullWidth-center > div.ft-donate-lang-social > p > a.button

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download About Us Get Help Community Blog DONATE body.html-ltr > div#nav-wrapper > nav.nav-main > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon

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.x64 html.x64

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-*]` 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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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
○Buttons have an accessible name
○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
○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.
○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
20 headings
PASS
20 headings
Info::
Single H1 present
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)
  • H1 LibreOffice is an open source office suite created by you, for you.
  • H2 One suite. Six tools.
  • H3 Writer
  • H3 Calc
  • H3 Impress
  • H3 Draw
  • H3 Base
  • H3 Math
  • H2 Why Choose LibreOffice?
  • H2 Join Our Community
  • H2 What People Are Saying
  • H2 Meet Our Community
  • H2 (empty)
  • H3 Download
  • H3 About Us
  • H3 Get Help
  • H3 Community
  • H3 Blog
  • H3 Follow us!

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 190 images OK
PASS
All 190 images OK
Info::
88 decorative image(s) correctly marked
Info::
102 image(s) with good alt text
190 images 102 good alt text 88 decorative
All images have appropriate alt text.
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 LibreOffice is an op…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 One suite. Six tools…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Choose LibreOffi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join Our Community21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What People Are Sayi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet Our Community21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Writer21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Calc21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Impress21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Draw21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Base21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Math21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Download21.00:13.0:1
#000000
#FFFFFF
Pass
h3 About Us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get Help21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Community21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Follow us!21.00:13.0:1
#000000
#FFFFFF
Pass
title LibreOffice16.36:14.5:1
#000000
#E3E3E3
Pass
label Language:21.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.

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

Send Feedback