Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 6 REVIEW 7 FIX

Link & Button Quality

Action

28 issue(s) across 201 links and 56 buttons

FIX

28 issue(s) across 201 links and 56 buttons

2 link(s) with no accessible text

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

Got: javascript:void(0);; a#contentarea

5 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="https://www.facebook.com/magicmotorsport"]; a[href="https://twitter.com/MAGICMOTORSPORT"]; a[href="https://www.linkedin.com/company/magicmotorsport/"]; a[href="https://www.youtube.com/user/magicmotorsport"]; a[href="https://www.instagram.com/mms.center/"]

11 link(s) open in new tab without warning

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

Got: https://magicmotorsport.shop/en//terms-services-warranty; https://www.iubenda.com/privacy-policy/25141031; https://www.facebook.com/magicmotorsport; https://twitter.com/MAGICMOTORSPORT; https://www.linkedin.com/company/magicmotorsport/; https://www.youtube.com/user/magicmotorsport; https://www.instagram.com/mms.center/; https://www.magicmotorsport.com/; https://www.magicmotorsport.com/en/compliance-and-funding/; https://www.magicmotorsport.com/ (+1 more)

26 button(s) with no accessible text

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

Got: button.owl-dot (#950 on page); button.owl-dot (#952 on page); button.owl-dot (#954 on page); button.owl-dot (#956 on page); button.owl-dot (#958 on page); button.action (#998 on page); button.action (#1028 on page); button.action (#1058 on page); button.action (#1088 on page); button.action (#1119 on page) (+16 more)

183 link(s) with descriptive text

201 links

2 empty

0 generic text

11 new tab

26 empty buttons

Element	Text	Issue	Suggested Fix
#	Espanol	img no alt	Add alt attribute to the image
#	German	img no alt	Add alt attribute to the image
#	Italiano	img no alt	Add alt attribute to the image
javascript:void(0);	(empty)	empty	Add link text or aria-label
#	Espanol	img no alt	Add alt attribute to the image
#	German	img no alt	Add alt attribute to the image
#	Italiano	img no alt	Add alt attribute to the image
	(empty)	empty	Add link text or aria-label
https://magicmotorsport.shop/en//terms-s…	terms of service	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/2…	privacy policy	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/magicmotorsport	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/MAGICMOTORSPORT	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/magicmo…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/magicmotors…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mms.center/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.magicmotorsport.com/	Official site	new tab	Add '(opens in new tab)' to text
https://www.magicmotorsport.com/en/compl…	Compliance	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/magicmotorsport	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/MAGICMOTORSPORT	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/magicmo…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/magicmotors…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mms.center/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.magicmotorsport.com/	Official site	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/2…	cookie policy	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
<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
<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
<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
<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
<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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

213 links and buttons have descriptive text

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

javascript:void(0);; a#contentarea

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="https://www.facebook.com/magicmotorsport"]; a[href="https://twitter.com/MAGICMOTORSPORT"]; a[href="https://www.linkedin.com/company/magicmotorsport/"]; a[href="https://www.youtube.com/user/magicmotorsport"]; a[href="https://www.instagram.com/mms.center/"]

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://magicmotorsport.shop/en//terms-services-warranty; https://www.iubenda.com/privacy-policy/25141031; https://www.facebook.com/magicmotorsport; https://twitter.com/MAGICMOTORSPORT; https://www.linkedin.com/company/magicmotorsport/; https://www.youtube.com/user/magicmotorsport; https://www.instagram.com/mms.center/; https://www.magicmotorsport.com/; https://www.magicmotorsport.com/en/compliance-and-funding/; https://www.magicmotorsport.com/ (+1 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.owl-dot (#950 on page); button.owl-dot (#952 on page); button.owl-dot (#954 on page); button.owl-dot (#956 on page); button.owl-dot (#958 on page); button.action (#998 on page); button.action (#1028 on page); button.action (#1058 on page); button.action (#1088 on page); button.action (#1119 on page) (+16 more)

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

Mobile Keyboard & Autofill

Action

6/8 eligible field(s) missing autocomplete or inputmode

FIX

6/8 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="newsletter">

5 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="username" id="customer-email">, <input type="email" name="email" id="newsletter">, <input type="email" name="sender_email">, <input type="email" name="sender_email">, <input type="email" name="sender_email">

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-9jykeq

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

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

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Heading Hierarchy

26 headings, 1 skip(s)

REVIEW

26 headings, 1 skip(s)

Multiple H1 headings (12 found)

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

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Mechatronic solutions for automotive workshops
H1 430€ OFF duplicate H1
H1 IXI duplicate H1
H1 DYNOMAG duplicate H1
H1 FLEX duplicate H1
H1 Automatic A/C Machine duplicate H1
H1 430€ OFF duplicate H1
H1 IXI duplicate H1
H1 DYNOMAG duplicate H1
H1 FLEX duplicate H1
H1 Automatic A/C Machine duplicate H1
H1 430€ OFF duplicate H1
H2 Recommended products
H2 Top categories
H2 Latest arrived
H2 Reviews
H2 Our brands
H2 Subscribe to the newsletter
H6 Contact skipped
H6 Social media
H6 Support
H6 Disclaimers and rules
H6 Support
H6 Disclaimers and rules
H6 Contact
H2 Notice

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

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

Form Accessibility

8 of 13 controls have issues

REVIEW

8 of 13 controls have issues

8 control(s) rely on placeholder only

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

Got: <input type="text" name="q" id="search">; <input type="email" name="email" id="newsletter">; <input type="text" name="sender_name">; <input type="email" name="sender_email">; <input type="text" name="sender_name">; <input type="email" name="sender_email">; <input type="text" name="sender_name">; <input type="email" name="sender_email">

5 control(s) properly labeled

13 controls

5 labeled

8 placeholder only

0 unlabeled

Control	Type	Label	Method
#customer-email	email	Email Address	for/id
#pass	password	Password	for/id
#is_acepted	checkbox	I agree and understand Magicmotorsport terms of service and privacy policy. I agree and consent to receive communications from the company. You can unsubscribe at any time by clicking the link in the footer of our emails *	for/id
#recipient_email	textarea	Recipient Email(s)	for/id
#message	textarea	Message (optional)	for/id
#newsletter	email	(Email Address...)	placeholder only
sender_name	text	(Enter Your Name)	placeholder only
sender_email	email	(Enter Your Email)	placeholder only
#search	text	(Search...)	placeholder only
sender_name	text	(Enter Your Name)	placeholder only
sender_email	email	(Enter Your Email)	placeholder only
sender_name	text	(Enter Your Name)	placeholder only
sender_email	email	(Enter Your Email)	placeholder only

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

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

Form Input Quality

2 input-semantic issue(s) across 13 form control(s)

REVIEW

2 input-semantic issue(s) across 13 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="password">.

6 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="username">, <input type="email" name="email">, <textarea name="recipient_email"> (+3 more).

Tap Target Adequacy

2 tap target(s) too small or too close together

REVIEW

2 tap target(s) too small or too close together

2 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

96% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

96% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Language"); <span> 11.0px ("English"); <span> 10.0px ("items").

Lighthouse Accessibility Audits

Score 80/100 — 6 failing, 26 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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu Categories Account Settings `ul.bottom-menu > li.nav-item > div.sections > div.section-items`

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.banner-slider > div#home-slider > div.owl-nav > button.owl-next`
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot `div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot`
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot `div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot`
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot `div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot`
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot `div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot`
div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot `div.banner-slider > div#home-slider > div.owl-dots > button.owl-dot`
‹ `div.row > div#product-slider > div.owl-nav > button.owl-prev`
› `div.row > div#product-slider > div.owl-nav > button.owl-next`
‹ `div.row > div#latest-slider > div.owl-nav > button.owl-prev`
› `div.row > div#latest-slider > div.owl-nav > button.owl-next`

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
form#search_mini_form > div.field > div.control > input#search `form#search_mini_form > div.field > div.control > input#search`
Shop `div.product-item-info > div.product-item-details > div.product-item-subtext > p`
Last arrived `div.product-item-info > div.product-item-details > div.product-item-subtext > p`
div.newsletter > div.control > span.input-text > input#newsletter `div.newsletter > div.control > span.input-text > input#newsletter`
Support `div.row > div.col-lg > div.block-content > h6`
Disclaimers and rules `div.row > div.col-lg-6 > div.block-content > h6`
Contact `div.row > div.col-lg > div.block-content > h6`
Cookie Policy `div.policy-links > div > a.iubenda-nostyle > span`
Privacy Policy `div.policy-links > div > a.iubenda-nostyle > span`

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
Support `div.row > div.col-lg > div.block-content > h6`

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`

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
+39 (0)91 74877 22 `ul.site-links > li > p > a`
+39 (0)91 74877 23 `ul.site-links > li > p > a`

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

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

●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

●`<frame>` or `<iframe>` elements have a title

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

●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

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

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

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

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

7 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 7 all-caps heading(s)

Alt Text Quality

2 of 116 images have issues

PASS

2 of 116 images have issues

2 image(s) with generic alt text

44 decorative image(s) correctly marked

70 image(s) with good alt text

116 images 70 good alt text 44 decorative 2 generic

Issue	Count
generic	2 image(s)

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

11 explicit tabindex attribute(s) checked, no anti-patterns

PASS

11 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

Iframe Accessibility

1/5 iframe(s) missing title; 0 placeholder(s)

PASS

1/5 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/css/print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet https://magicmotorsport.shop/static/version1786090959/frontend/Smartwave/porto_child/en_GB/css/print.css ✓Inline @media print Not detected ✗

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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)

Element	Ratio	Required	FG	BG	Result
h1 Mechatronic solution…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 for automotive works…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 430€ OFF	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 IXI	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 DYNOMAG	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 FLEX	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 Automatic A/C Machin…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 430€ OFF	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 IXI	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 DYNOMAG	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 FLEX	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 Automatic A/C Machin…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h1 430€ OFF	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Notice	19.77:1	3.0:1	#000000	#F8F8F8	Pass
title Magicmotorsport Shop…	13.75:1	4.5:1	#000000	#FFC2C2	Pass
div The store will not w…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Links	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Compare (	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Login	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Language	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.

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