Skip to content
https://openoffice.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 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: <select id="selectlanguage">; <input type="text" name="q" id="query">; <input type="submit" name="Button">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#selectlanguageselect(none)none
#querytext(none)none
Buttonsubmit(none)none

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

<select id="selectlanguage">; <input type="text" name="q" id="query">; <input type="submit" name="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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 4 failing, 12 passed
REVIEW
76

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
Language Asturianu (ast) Català (ca) Čeština (cs) Dansk (da) Deutsch (de) Engl… body > div#bannera > div#languagesdiv
The Free and Open Productivity Suite body > div#bannera > div#bannercenter
Product div#topnava > ul > li > a
Download div#topnava > ul > li > a
Support div#topnava > ul > li > a
Blog div#topnava > ul > li > a
Extensions & Templates div#topnava > ul > li > a
Get Involved div#topnava > ul > li > a
Focus Areas div#topnava > ul > li > a
Native Languages div#topnava > ul > li > a
home body > div#topbara > div#breadcrumbsa > a
All Posts div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.16 div#news > div.first > p > a
Development Update - April 2024 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.15 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.14 div#news > div.first > p > a
333,333,333+ Downloads of Apache OpenOffice div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.13 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.12 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.11 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.10 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.9 div#news > div.first > p > a
New release for Apple's macOS 11 (Big Sur) - Also with fixes for Linux and Wind… div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.8 div#news > div.first > p > a
300 Million Downloads of Apache OpenOffice div#news > div.first > p > a
The Apache Software Foundation Celebrates 20 Years of OpenOffice® div#news > div.first > p > a
Apache OpenOffice needs your help div#news > div.first > p > a
1.6 million downloads of Apache OpenOffice 4.1.7 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.7 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.6 div#news > div.first > p > a
Over 3.2 million downloads of Apache OpenOffice 4.1.5 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.5 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.4 div#news > div.first > p > a
Over 200 million downloads of Apache OpenOffice div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.3 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.2 div#news > div.first > p > a
Coming soon... Apache OpenOffice 4.1.2 div#news > div.first > p > a
Authoring e-Books in Apache OpenOffice div#news > div.first > p > a
Collaboration is in our DNA div#news > div.first > p > a
Copyright & License div#footera > div#copyrighta > p > a
Privacy div#footera > div#copyrighta > p > a
Contact Us div#footera > div#copyrighta > p > a
Donate div#footera > div#copyrighta > p > a
Thanks div#footera > div#copyrighta > p > a

These are opportunities to improve the legibility of your content.

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.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Asturianu (ast) Català (ca) Čeština (cs) Dansk (da) Deutsch (de) English [US] (… body > div#bannera > div#languagesdiv > select#selectlanguage

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>`
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●Document has a `<title>` element
●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
●Identical links have the same purpose.
○`[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
○`<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 a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○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.
○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
31 headings
PASS
31 headings
Info::
Single H1 present
  • H1 Apache OpenOffice
  • H2 I want to learn more about OpenOffice
  • H2 I want to download Apache OpenOffice
  • H2 I need help with my OpenOffice
  • H2 I want to do more with my OpenOffice
  • H2 I want to participate in OpenOffice
  • H2 I want to stay in touch with OpenOffice
  • H2 Recent Blog Posts
  • H2 Recent News
  • H2 Apache OpenOffice 4.1.16 released
  • H2 Apache OpenOffice 4.1.15 released
  • H2 Apache OpenOffice 4.1.14 released
  • H2 More than 333,333,333 downloads
  • H2 Apache OpenOffice 4.1.13 released
  • H2 Apache OpenOffice 4.1.12 released
  • H2 Apache OpenOffice 4.1.11 released
  • H2 Apache OpenOffice 4.1.10 released
  • H2 Apache OpenOffice 4.1.9 released
  • H2 Apache OpenOffice 4.1.8 released
  • H2 Apache OpenOffice 4.1.7 released
  • H2 Apache OpenOffice 4.1.6 released
  • H2 Apache OpenOffice 4.1.5 released
  • H2 Apache OpenOffice 4.1.4 released
  • H2 Apache OpenOffice 4.1.3 released
  • H2 Apache OpenOffice 4.1.2 released
  • H2 Udine moves to OpenOffice, will save 360,000 Euro
  • H2 Apache OpenOffice 4.1.1 released
  • H2 Apache OpenOffice 4.1.0 released
  • H2 100 Million downloads
  • H2 Italian region adopts OpenOffice, saves 2 Million Euro
  • H2 Volunteers, not Amateurs
A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
7 image(s) with good alt text
7 images 7 good alt text
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 Apache OpenOffice21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I want to learn more…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I want to download A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I need help with my …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I want to do more wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I want to participat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I want to stay in to…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recent Blog Posts21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recent News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More than 333,333,33…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Apache OpenOffice 4.…21.00:13.0: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