Skip to content
https://owncloud.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 (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

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

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
Theme color only
FIX
Theme color only
Info::
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: #ffffff
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 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.

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::
2 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 2 <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.
B
Heading Hierarchy
38 headings, 2 skip(s)
REVIEW
38 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 products
  • H4 solutions
  • H4 community
  • H4 resources
  • H4 partners
  • H4 about us
  • H1 ownCloud Infinite Scale
  • H2 Filesharing, trusted by 200 million users worldwide
  • H2 Spaces
  • H2 Web office
  • H3 Seeking to Unify, Track, Control, and Secure All Your Sensitive Content on One Platform?
  • H2 Secure by design
  • H2 For organizations with high data governance requirements
  • H3 Do you prefer SaaS? Check out ownCloud.online!
  • H2 For smaller organizations and private users
  • H2 Control who can access your data
  • H4 GDPR-ready skipped
  • H4 LGPD-ready
  • H4 CCRF-ready
  • H4 HIPAA-ready
  • H4 CCPA-ready
  • H2 Increase productivity
  • H3 Convenient collaboration with internal and external parties without storing data in the public cloud. Open APIs and modularity let you integrate almost everything to your ownCloud – Data sovereignty
  • H2 Users love ownCloud
  • H3 4.2
  • H3 4.1
  • H3 4.7
  • H2 Our latest news
  • H2 What happens when you fork twice, get acquired, and keep shipping anyway
  • H2 Understanding Web Applications in oCIS
  • H2 A (re-)introduction to the ownCloud Community
  • H4 Get started skipped
  • H4 Product
  • H4 Company
  • H4 Community
  • H4 Help
  • H4 Legal
  • H4 Follow Us

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

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
Form Accessibility
Action
5 of 11 controls have issues
REVIEW
5 of 11 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" id="searchsubmit">
Info::
6 control(s) properly labeled
11 controls
6 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#stextSearch for:for/id
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#searchsubmitsubmit(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" id="searchsubmit">

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
Favicon & Branding
5 icon(s) detected
REVIEW
5 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 Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 2 pass AA only
a Details
4.49:1
#000000
on
#4576B2
needs 4.5:1 (normal text)
16px · top of page (header area)
a [#IABV2SETTINGS#]
1.21:1
#000000
on
#031A39
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.21:1
#000000
on
#031A39
needs 4.5:1 (normal text)
16px · above the fold
div This website uses cookies
1.21:1
#000000
on
#031A39
needs 4.5:1 (normal text)
16px · above the fold
div We use cookies to personalise content an…
1.21:1
#000000
on
#031A39
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_BANNER_ICON#]
1.21:1
#000000
on
#031A39
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 ownCloud16.98:13.0:1
#000000
#E7E7E7
Pass
h1 Infinite Scale16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Spaces16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Web office16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Secure by design16.98:13.0:1
#000000
#E7E7E7
Pass
h2 For organizations wi…16.98:13.0:1
#000000
#E7E7E7
Pass
h2 For smaller organiza…16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Control who can acce…16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Increase productivit…16.98:13.0:1
#000000
#E7E7E7
Pass
h2 Users love ownCloud16.98:13.0:1
#000000
#E7E7E7
Pass
h3 Seeking to Unify, Tr…16.98:13.0:1
#000000
#E7E7E7
Pass
h3 Do you prefer SaaS? …16.98:13.0:1
#000000
#E7E7E7
Pass
title ownCloud - share fil…5.23:14.5:1
#000000
#4C81C2
Pass
a Consent4.82:14.5:1
#000000
#487BBA
Pass
a Details4.49:14.5:1
#000000
#4576B2
Fail
a [#IABV2SETTINGS#]1.21:14.5:1
#000000
#031A39
Fail
a About1.21:14.5:1
#000000
#031A39
Fail
div This website uses co…1.21:14.5:1
#000000
#031A39
Fail
div We use cookies to pe…1.21:14.5:1
#000000
#031A39
Fail
div [#GPC_BANNER_ICON#]1.21:14.5:1
#000000
#031A39
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 23 passed
REVIEW
82

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.topbar > div.topbar__wrapper > div.topbar__settings > button.hamburger div.topbar > div.topbar__wrapper > div.topbar__settings > button.hamburger

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_row > div.et_pb_column > div.et_pb_module > a div.et_pb_row > div.et_pb_column > div.et_pb_module > a
div.et_pb_row > div.et_pb_column > div.et_pb_module > a div.et_pb_row > div.et_pb_column > div.et_pb_module > a

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.

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
Security Alert – Attention ownCloud Customers – Security Notice div.infobanner__content > div.infobanner__text-wrapper > span.infobanner__text > a
Security Alert div.infobanner__text-wrapper > span.infobanner__text > a > strong
Read More div.infobanner > div.infobanner__content > div.infobanner__buttons > a.infobanner__button
Filesharing, trusted by 200 million users worldwide div.et_pb_module > div.et_pb_text_inner > h2 > span
Learn more div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Contact us div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Start now div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Share flexibly div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Collaborate efficiently div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Apr 22, 2026 div.column > article#post-79464 > p.post-meta > span.published
read more div.column > article#post-79464 > div.post-content > a.more-link
Apr 21, 2026 div.column > article#post-79440 > p.post-meta > span.published
read more div.column > article#post-79440 > div.post-content > a.more-link
Aug 1, 2024 div.column > article#post-78926 > p.post-meta > span.published
read more div.column > article#post-78926 > div.post-content > a.more-link
Search div.et_pb_blurb_container > div.et_pb_blurb_description > p > a
English ul > li.wpml-ls-slot-shortcode_actions > a.js-wpml-ls-item-toggle > span.wpml-ls-native

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
GDPR-ready div.et_pb_module > div.et_pb_blurb_content > div.et_pb_blurb_container > h4.et_pb_module_header
GET STARTED div.et_pb_column > div.et_pb_module > div.et_pb_code_inner > h4.footer-menu-title

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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
English div.wpml-ls-statics-shortcode_actions > ul > li.wpml-ls-slot-shortcode_actions > a.js-wpml-ls-item-toggle
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
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
`[lang]` attributes have a valid value
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
`<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
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.
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.
`<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.
A+
Alt Text Quality
1 of 32 images have issues
PASS
1 of 32 images have issues
Warning::
1 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
32 images 26 good alt text 5 decorative 1 generic
IssueCount
generic1 image(s)
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 Page not found - ownCloud Custom Styling Navigation Homepage Link Search Form
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback