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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-56v3ar

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://synology.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://synology.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

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

2 of 6 images have issues

REVIEW

2 of 6 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 decorative image(s) correctly marked

6 images 4 decorative 2 missing

Issue	Count
missing	2 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

Link & Button Quality

Action

2 issue(s) across 38 links and 13 buttons

REVIEW

2 issue(s) across 38 links and 13 buttons

2 link(s) with no accessible text

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

Got: a.btn-close (#116 on page); a.btn-close (#565 on page)

13 link(s) open in new tab without warning

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

Got: /en-global/company/legal/privacy; /en-global/company/legal/cookie_policy; https://www.synology.com/company/legal/privacy; https://www.synology.com/company/legal/Services_Data_Collection_Disclosure; https://blog.synology.com/; https://community.synology.com/enu; https://event.synology.com/en-global; https://www.facebook.com/synology?ref=nf; https://twitter.com/synology; https://www.youtube.com/user/synologyinc (+3 more)

23 link(s) with descriptive text

38 links

2 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en-global/company/legal/privacy	Privacy Statement	new tab	Add '(opens in new tab)' to text
/en-global/company/legal/cookie_policy	Cookie Policy	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.synology.com/company/legal/p…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.synology.com/company/legal/S…	Data Collection Disclosure	new tab	Add '(opens in new tab)' to text
https://blog.synology.com/	Blog	new tab	Add '(opens in new tab)' to text
https://community.synology.com/enu	Community	new tab	Add '(opens in new tab)' to text
https://event.synology.com/en-global	Events	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/synology?ref=nf	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/synology	Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/synologyinc	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/synology.offic…	Instagram	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.synology.com/company/legal/p…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.synology.com/company/legal/S…	Data Collection Disclosure	new tab	Add '(opens in new tab)' to text

36 links and buttons have descriptive text

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

a.btn-close (#116 on page); a.btn-close (#565 on page)

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.

/en-global/company/legal/privacy; /en-global/company/legal/cookie_policy; https://www.synology.com/company/legal/privacy; https://www.synology.com/company/legal/Services_Data_Collection_Disclosure; https://blog.synology.com/; https://community.synology.com/enu; https://event.synology.com/en-global; https://www.facebook.com/synology?ref=nf; https://twitter.com/synology; https://www.youtube.com/user/synologyinc (+3 more)

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

Favicon & Branding

11 icon(s) detected

REVIEW

11 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 1 pass AA only

a Cookie Policy

1.39:1

#000000

#372200

needs 4.5:1 (normal text)

16px · above the fold

p for more information on how we collect a…

2.64:1

#000000

#6F490E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Reject All

1.85:1

#000000

#6E1E03

needs 4.5:1 (normal text)

16px · above the fold

div Agree

2.34:1

#000000

#892604

needs 4.5:1 (normal text)

16px · above the fold

span Il semble qu'une page avec des données …

2.98:1

#000000

#A23109

needs 4.5:1 (normal text)

16px · above the fold

div Česká republika - Čeština

3.15:1

#000000

#A5370F

needs 4.5:1 (normal text)

16px · above the fold

s-btn Continuer

3.79:1

#000000

#935A44

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Always clear — day…	6.52:1	3.0:1	#000000	#938E91	Pass
h1 DSM 7.3	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Collaboration in ful…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Secure your data, sc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Synology Inc.	19.26:1	4.5:1	#000000	#F5F5F5	Pass
div We value your privac…	19.26:1	4.5:1	#000000	#F5F5F5	Pass
p We use cookies to pe…	19.26:1	4.5:1	#000000	#F5F5F5	Pass
a Privacy Statement	19.26:1	4.5:1	#000000	#F5F5F5	Pass
p and	19.26:1	4.5:1	#000000	#F5F5F5	Pass
a Cookie Policy	1.39:1	4.5:1	#000000	#372200	Fail
p for more information…	2.64:1	4.5:1	#000000	#6F490E	Fail
div Cookie Options	7.58:1	4.5:1	#000000	#C7922E	Pass
div Reject All	1.85:1	4.5:1	#000000	#6E1E03	Fail
div Agree	2.34:1	4.5:1	#000000	#892604	Fail
span Il semble qu'une pag…	2.98:1	4.5:1	#000000	#A23109	Fail
div Česká republika - …	3.15:1	4.5:1	#000000	#A5370F	Fail
span France - Français	5.45:1	4.5:1	#000000	#B37254	Pass
s-btn Continuer	3.79:1	4.5:1	#000000	#935A44	Fail
p AI-powered camera wi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
s-btn Learn more	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 29 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

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
France - Français `div.s-ddv2__container > div.s-ddv2__combobox > div.s-ddv2__control > button.s-ddv2__control-content`
button#home-hero-video-link `button#home-hero-video-link`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
s-section#home-ai-advisor > s-container.home-ai-advisor__input-wrapper > div.home-ai-advisor__input > textarea#home-ai-advisor-textarea `s-section#home-ai-advisor > s-container.home-ai-advisor__input-wrapper > div.home-ai-advisor__input > textarea#home-ai-advisor-textarea`

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

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
Continuer `div.ip-banner > div.s-containerless > div.ip-banner__btn-box > a.ip-banner__btn-box__btn-continue-wrapper`

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
Storage and Data Management `a.s-link`
Data Protection `a.s-link`
Video Surveillance `a.s-link`
Business Productivity `a.s-link`
Open language picker `div.m-lp > button.m-lp-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

●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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

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

●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

●Background and foreground colors have a sufficient contrast ratio

●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

●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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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

Heading Hierarchy

4 headings

PASS

4 headings

Multiple H1 headings (4 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Always clear — day, night, near, far.
H1 DSM 7.3 duplicate H1
H1 Collaboration in full flight duplicate H1
H1 Secure your data, scale your success duplicate H1

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

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="home-ai-advisor-textarea" id="home-ai-advisor-textarea">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	checkbox		none
input	radio		none
textarea	textarea	Ask a question	aria-label
#home-ai-advisor-textarea	textarea	(none)	none

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

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

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