Skip to content
https://tp-link.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Alt Text Quality
Action
6 of 44 images have issues
FIX
6 of 44 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
5 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
44 images 33 good alt text 5 decorative 6 missing
IssueCount
missing6 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

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::
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
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 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 CONTENTINFO footer

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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#tp-follow-subscribe-inputtextE-mailfor/id
qtext(Rechercher)placeholder only
qtext(Rechercher)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q">; <input type="text" name="q">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title TP-Link ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 TP-Link France – Le meilleur du WiFi p…
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Optez pour la 5G
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Optez pour la 5G
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nouveautés WiFi TP-Link
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recommandés
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nouveautés
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trouvez le système Deco qui vous convie…
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dernières News
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newsletter TP-Link
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Suivez-nous
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Tapo C665G KIT
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deco BE68
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tapo RV50 Pro Omni
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 M8550
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tapo C660 KIT
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Archer NX200
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deco BE25-Outdoor
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tapo C230
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Archer NX500-Outdoor
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Archer NX505
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 TP-Link France – L…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Optez pour la 5G2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Optez pour la 5G2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Nouveautés WiFi TP-…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Recommandés2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Nouveautés2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Trouvez le système …2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Dernières News2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Newsletter TP-Link2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Suivez-nous2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Tapo C665G KIT2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Deco BE682.45:13.0:1
#000000
#4C4C4C
Fail
h3 Tapo RV50 Pro Omni2.45:13.0:1
#000000
#4C4C4C
Fail
h3 M85502.45:13.0:1
#000000
#4C4C4C
Fail
h3 Tapo C660 KIT2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Archer NX2002.45:13.0:1
#000000
#4C4C4C
Fail
h3 Deco BE25-Outdoor2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Tapo C2302.45:13.0:1
#000000
#4C4C4C
Fail
h3 Archer NX500-Outdoor2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Archer NX5052.45:13.0:1
#000000
#4C4C4C
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.

A+
Heading Hierarchy
31 headings
PASS
31 headings
Info::
Single H1 present
  • H1 TP-Link France – Le meilleur du WiFi partout. La maison 100% connectée Tapo
  • H2 Optez pour la 5G
  • H2 Optez pour la 5G
  • H2 Nouveautés WiFi TP-Link
  • H2 Recommandés
  • H2 Nouveautés
  • H3 Tapo C665G KIT
  • H3 Deco BE68
  • H3 Tapo RV50 Pro Omni
  • H3 M8550
  • H3 Tapo C660 KIT
  • H3 Archer NX200
  • H3 Deco BE25-Outdoor
  • H3 Tapo C230
  • H3 Archer NX500-Outdoor
  • H3 Archer NX505
  • H3 OC220
  • H3 SX3032F
  • H3 SG2452LP
  • H3 EAP787
  • H3 ES206XPP-M2
  • H3 ES206X-M2
  • H2 Trouvez le système Deco qui vous convient
  • H2 Dernières News
  • H3 Caméra extérieure chez soi : quelle réglementation en France ?
  • H3 Pourquoi utiliser un MiFi 5G plutôt que le WiFi public de son université ?
  • H3 Les dangers des hotspots WiFi publics : ce qu’il faut savoir pour naviguer en sécurité
  • H3 Observation de la faune avec une caméra 4G solaire
  • H3 Détection IA dans les caméras de surveillance : moins de fausses alertes, plus de sécurité
  • H2 Newsletter TP-Link>TP-Link prend votre vie privée au sérieux. Pour plus de détails sur la politique de confidentialité de TP-Link, veuillez consultez la page suivante Politique de confidentialit�
  • H2 Suivez-nous
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 25 passed
PASS
100

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.

○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
●Buttons have an accessible name
●`[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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[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
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Heading elements appear in a sequentially-descending order
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback