Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Link & Button Quality

Action

8 issue(s) across 121 links and 26 buttons

FIX

8 issue(s) across 121 links and 26 buttons

4 link(s) with no accessible text

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

Got: a.cta-conversion--pattern (#130 on page); /blog/success-stories-en/clothing-brand-molly-bracken-accelerates-with-presta…; /blog/news/prestashop-monthly-march-2026; /blog/success-stories-en/store-lashes-a-new-look-at-bnpl-in-b2b

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/prestashop-offers/"]

18 link(s) open in new tab without warning

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

Got: https://addons.prestashop.com/en/; https://experts.prestashop.com/english/experts/; https://www.prestashop.com/forums/; https://events.prestashop.com/; https://care-center.prestashop.com/gb/; https://addons.prestashop.com/en/; https://experts.prestashop.com/english/experts/; https://www.prestashop.com/forums/; https://events.prestashop.com/; https://care-center.prestashop.com/gb/ (+8 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.close (#343 on page); button (#360 on page); button (#397 on page); button (#426 on page)

98 link(s) with descriptive text

121 links

4 empty

0 generic text

18 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/prestashop-offers/	GET STARTED	img no alt	Add alt attribute to the image
	(empty)	empty	Add link text or aria-label
https://addons.prestashop.com/en/	PrestaShop Marketplace Explore…	new tab	Add '(opens in new tab)' to text
https://experts.prestashop.com/english/e…	PrestaShop Experts Hire a prof…	new tab	Add '(opens in new tab)' to text
https://www.prestashop.com/forums/	Forum Engage in discussions an…	new tab	Add '(opens in new tab)' to text
https://events.prestashop.com/	Events Browse our calendar to …	new tab	Add '(opens in new tab)' to text
https://care-center.prestashop.com/gb/	Care Center Learn how to use P…	new tab	Add '(opens in new tab)' to text
https://addons.prestashop.com/en/	PrestaShop Marketplace Explore…	new tab	Add '(opens in new tab)' to text
https://experts.prestashop.com/english/e…	PrestaShop Experts Hire a prof…	new tab	Add '(opens in new tab)' to text
https://www.prestashop.com/forums/	Forum Engage in discussions an…	new tab	Add '(opens in new tab)' to text
https://events.prestashop.com/	Events Browse our calendar to …	new tab	Add '(opens in new tab)' to text
https://care-center.prestashop.com/gb/	Care Center Learn how to use P…	new tab	Add '(opens in new tab)' to text
https://experts.prestashop.com/english/e…	Find a PrestaShop Expert	new tab	Add '(opens in new tab)' to text
/blog/success-stories-en/clothing-brand-…	(empty)	empty	Add link text or aria-label
/blog/news/prestashop-monthly-march-2026	(empty)	empty	Add link text or aria-label
/blog/success-stories-en/store-lashes-a-…	(empty)	empty	Add link text or aria-label
https://facebook.com/prestashop	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/prestashop/	Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/prestashop	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/prestas…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/prestashop	Youtube	new tab	Add '(opens in new tab)' to text
https://github.com/PrestaShop/	Github	new tab	Add '(opens in new tab)' to text
https://join.slack.com/t/prestashop/shar…	Slack	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

120 links and buttons have descriptive text

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

a.cta-conversion--pattern (#130 on page); /blog/success-stories-en/clothing-brand-molly-bracken-accelerates-with-presta…; /blog/news/prestashop-monthly-march-2026; /blog/success-stories-en/store-lashes-a-new-look-at-bnpl-in-b2b

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/prestashop-offers/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://addons.prestashop.com/en/; https://experts.prestashop.com/english/experts/; https://www.prestashop.com/forums/; https://events.prestashop.com/; https://care-center.prestashop.com/gb/; https://addons.prestashop.com/en/; https://experts.prestashop.com/english/experts/; https://www.prestashop.com/forums/; https://events.prestashop.com/; https://care-center.prestashop.com/gb/ (+8 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.close (#343 on page); button (#360 on page); button (#397 on page); button (#426 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

title Create an online shop easily - Ecommerce…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Aller au menu

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Aller au contenu

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Aller au footer

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Unlock your commerce	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More than 250,000 me…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Made for commerce.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Built for success.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Feel empowered by th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 To ensure your succe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 we work with the bes…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 You need extra help	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 to build the ecommer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 you've always wanted…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ecommerce trends, be…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 You're in control.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your store, your way…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 We're in this for th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 We're here to help.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Clothing brand Molly…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Create an online sho…	1.00:1	4.5:1	#000000	#000000	Fail
a Aller au menu	1.00:1	4.5:1	#000000	#000000	Fail
a Aller au contenu	1.00:1	4.5:1	#000000	#000000	Fail
a Aller au footer	1.00:1	4.5:1	#000000	#000000	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.

Lighthouse Accessibility Audits

Score 81/100 — 6 failing, 25 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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Control `div.col-md-1--1 > div.tabs > div.tablist > button#tab-0`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.nav > div.mobile > nav.main > button.close `div.nav > div.mobile > nav.main > button.close`

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.theHeader__container > div.actions > div > a.cta-login--pattern `div.theHeader__container > div.actions > div > a.cta-login--pattern`
div.grid > div.col-lg-8 > div.card-article > a `div.grid > div.col-lg-8 > div.card-article > a`
div.grid > aside.col-lg-4 > div.card-article > a `div.grid > aside.col-lg-4 > div.card-article > a`
div.grid > aside.col-lg-4 > div.card-article > a `div.grid > aside.col-lg-4 > div.card-article > 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.

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.

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
I refuse `div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss`
Fine for me `div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll`

○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 are valid and not misspelled

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●Links are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○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">`

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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

15 headings

PASS

15 headings

Single H1 present

H1 Unlock your commerce
H2 More than 250,000 merchants are already on PrestaShop
H2 Made for commerce.Built for success.
H3 You're in control.
H3 Your store, your way.
H3 We're in this for the long run.
H3 We're here to help.
H2 Feel empowered by the strength of our community
H2 To ensure your success,we work with the best
H2 You need extra helpto build the ecommerceyou've always wanted?
H2 Ecommerce trends, best practices, and business tips
H3 Clothing brand Molly Bracken accelerates with PrestaShop
H4 PrestaShop Monthly, March 2026
H4 Store Lashes: A New Look at BNPL in B2B
H4 The latest ecommerce trends

A+

Alt Text Quality

All 135 images OK

PASS

All 135 images OK

83 decorative image(s) correctly marked

52 image(s) with good alt text

135 images 52 good alt text 83 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#accessibility-font	checkbox	Change text display	for/id

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