Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 13 -1-on-focusable

FIX

0 positive, 13 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

D

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.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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.

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

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

10 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 10 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Heading Hierarchy

17 headings, 2 skip(s)

REVIEW

17 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H1 → H3 (missing H2)

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

H2 Cookie consent
H2 New collection
H2 We believe we must always stay one step ahead to continuously develop the best headwear.
H2 FEMALE HATS
H2 FLAT CAPS
H3 FREE DELIVERY
H3 EASY TO RETURN
H3 100% SECURE PAYMENTS
H3 SUPPORT
H2 NO WIND
H2 BEANIES
H2 Protect yourself from any kind of weather
H4 Wind skipped
H4 Cold
H4 Rain
H1 Hats and Caps Specialist in the Netherlands
H3 Hatland, your headwear specialist skipped

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

B

Link & Button Quality

1 issue(s) across 362 links and 69 buttons

REVIEW

1 issue(s) across 362 links and 69 buttons

5 link(s) open in new tab without warning

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

Got: https://www.hatland.nl/en/policies/privacy-policy; https://www.instagram.com/hatland.nl/; https://www.youtube.com/@hatlandheadwear; https://www.instagram.com/hatland.nl/; https://www.youtube.com/@hatlandheadwear

1 button(s) with no accessible text

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

Got: button.button (#2784 on page)

357 link(s) with descriptive text

362 links

0 empty

0 generic text

5 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.hatland.nl/en/policies/priva…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/hatland.nl/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@hatlandheadwear	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/hatland.nl/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@hatlandheadwear	YouTube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

425 links and buttons have descriptive text

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

https://www.hatland.nl/en/policies/privacy-policy; https://www.instagram.com/hatland.nl/; https://www.youtube.com/@hatlandheadwear; https://www.instagram.com/hatland.nl/; https://www.youtube.com/@hatlandheadwear

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.button (#2784 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

B

Mobile-Readable Font Sizes

93% of visible text renders at >= 12 CSS px (10 below threshold)

REVIEW

93% of visible text renders at >= 12 CSS px (10 below threshold)

10 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: <button> 10.0px ("Accept"); <button> 10.0px ("Decline"); <a> 10.0px ("Skip to content"); <p> 10.0px ("30-day return policy"); <p> 10.0px ("More than 25,000 satisfied customers").

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 6 pass AA only

p We and our partners, including Shopify, …

4.22:1

#000000

on

#6A707C

needs 4.5:1 (normal text)

16px · top of page (header area)

p More than 25,000 satisfied customers

1.93:1

#000000

on

#423C34

needs 4.5:1 (normal text)

16px · mid-page

button Men

1.91:1

#000000

on

#403C33

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Hats and Caps Specia…	3.03:1	3.0:1	#000000	#615949	Pass
h2 Cookie consent	11.18:1	3.0:1	#000000	#BCBDC0	Pass
h2 New collection	3.03:1	3.0:1	#000000	#615949	Pass
h2 We believe we must a…	3.03:1	3.0:1	#000000	#615949	Pass
h2 Protect yourself fro…	3.03:1	3.0:1	#000000	#615949	Pass
h3 Hatland, your headwe…	3.03:1	3.0:1	#000000	#615949	Pass
title The most beautiful h…	19.77:1	4.5:1	#000000	#F8F8F8	Pass
p We and our partners,…	4.22:1	4.5:1	#000000	#6A707C	Fail
a Privacy Policy	7.64:1	4.5:1	#000000	#9A9CA1	Pass
span Manage preferences	7.17:1	4.5:1	#000000	#9197A5	Pass
button Accept	10.10:1	4.5:1	#000000	#AEB4C1	Pass
button Decline	8.55:1	4.5:1	#000000	#9AA6BB	Pass
a Skip to content	9.29:1	4.5:1	#000000	#A3ADBF	Pass
span E-GIFTCARD	10.43:1	4.5:1	#000000	#B1B7C3	Pass
p Official Hatland web…	9.93:1	4.5:1	#000000	#ABB3BF	Pass
p Order by 3:00 PM on …	9.42:1	4.5:1	#000000	#A7AEBB	Pass
p Sign up for our news…	7.55:1	4.5:1	#000000	#A1999B	Pass
p 30-day return policy	5.62:1	4.5:1	#000000	#938171	Pass
p More than 25,000 sat…	1.93:1	4.5:1	#000000	#423C34	Fail
button Men	1.91:1	4.5:1	#000000	#403C33	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

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

10 <nav> landmark(s) found

10 of 10 <nav> elements are unlabeled

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

Skip navigation link present

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

8 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: 8 all-caps heading(s)

A

Alt Text Quality

1 of 84 images have issues

PASS

1 of 84 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

26 decorative image(s) correctly marked

57 image(s) with good alt text

84 images 57 good alt text 26 decorative 1 missing

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

A+

Form Accessibility

All 37 controls labeled

PASS

All 37 controls labeled

37 control(s) properly labeled

37 controls

37 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#country-drawer-selector-header-drawer-	select	Change currency	for/id
#country-drawer-language-header-drawer-	select	Change language	for/id
#country-drawer-selector-header-sections--25914267140420__header	select	Change currency	for/id
#country-drawer-language-header-sections--25914267140420__header	select	Change language	for/id
#search-desktop	search	Search	for/id
#template--25914267631940__featured_products_BVPWUA-15456191643972-variant-option-1-1-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191643972-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191643972-variant-option-1-3-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191643972-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190824772-variant-option-1-1-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190824772-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190824772-variant-option-1-3-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190824772-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188072260-variant-option-1-1-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188072260-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188072260-variant-option-1-3-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188072260-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15452475228484-variant-option-1-1-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15452475228484-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15452475228484-variant-option-1-3-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15452475228484-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191709508-variant-option-1-1-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191709508-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191709508-variant-option-1-3-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15456191709508-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190464324-variant-option-1-1-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190464324-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190464324-variant-option-1-3-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15456190464324-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188662084-variant-option-1-1-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188662084-variant-option-1-2-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188662084-variant-option-1-3-block	radio	L	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188662084-variant-option-1-4-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188039492-variant-option-1-1-block	radio	XL	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188039492-variant-option-1-2-block	radio	S	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188039492-variant-option-1-3-block	radio	M	aria-label
#template--25914267631940__featured_products_BVPWUA-15456188039492-variant-option-1-4-block	radio	L	aria-label

A+

Form Input Types

37 form control(s) checked, no type mismatches

PASS

37 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

37 form control(s) checked, no input-semantic issues

PASS

37 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A

Iframe Accessibility

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

PASS

1/2 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+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 25 passed

PASS

90

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.

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
ACCEPT `section#shopify-pc__banner > div.shopify-pc__banner__wrapper > div.shopify-pc__banner__btns > button#shopify-pc__banner__btn-accept`
DECLINE `section#shopify-pc__banner > div.shopify-pc__banner__wrapper > div.shopify-pc__banner__btns > button#shopify-pc__banner__btn-decline`
New collection `div.container > div.section__head > div.section__head-title > h2.section__heading`
NEW `div.product-card__content > div.product-card__info > div.product-labels__wrapper > span.product-label`
ELISEO - WOOL HAT - BROWN `div.product-card__info > span.product-card__title > a.product-card__link > span`
€84,99 `div.price > div.price__container > div.price__regular > span`
NEW `div.product-card__content > div.product-card__info > div.product-labels__wrapper > span.product-label`
DURBAN - FELT HAT - BROWN `div.product-card__info > span.product-card__title > a.product-card__link > span`
€99,99 `div.price > div.price__container > div.price__regular > span`
VIEW ALL `div.container > div.section__foot > div.section__head--buttons > a.button`
SHOP NOW `div.grid > div.section-dual-tiles__block > div.section-dual-tiles__content > button.button`
EXPLORE NOW `div.grid > div.section-dual-tiles__block > div.section-dual-tiles__content > button.button`
Protect yourself from any kind of weather `div.container > div.section__head > div.section__head-title > h2.section__heading`
Wind `a.card-collection__content-wrapper > div.card-collection__content > h4.card-collection__heading > span`
Cold `a.card-collection__content-wrapper > div.card-collection__content > h4.card-collection__heading > span`
Hats and Caps Specialist in the Netherlands `div.section-multitile__content > div > div.section-multitile__text > h1`
Hatland, your headwear specialist `div.section-multitile__content > div > div.section-multitile__text > h3`
Collections `accordion-default.accordion > nav.footer__nav-mobile > details#Footer-accordion-section-1 > summary#Accordion-button-1`
Hatland `accordion-default.accordion > nav.footer__nav-mobile > details#Footer-accordion-section-2 > summary#Accordion-button-2`
Information `accordion-default.accordion > nav.footer__nav-mobile > details#Footer-accordion-section-3 > summary#Accordion-button-3`
Support `accordion-default.accordion > nav.footer__nav-mobile > details#Footer-accordion-section-4 > summary#Accordion-button-4`
Policy `accordion-default.accordion > nav.footer__nav-mobile > details#Footer-accordion-section-5 > summary#Accordion-button-5`
Telephone 038-4226843 `div.grid > div.section-footer__block > div.section-footer__content > p`
Telephone `div.section-footer__block > div.section-footer__content > p > strong`
E-mail support@hatland.eu `div.grid > div.section-footer__block > div.section-footer__content > p`
E-mail `div.section-footer__block > div.section-footer__content > p > strong`
Need help? `div.section-footer__block > div.section-footer__content > p > strong`
Mo - Fr 09:00 hour - 15:00 hour `div.grid > div.section-footer__block > div.section-footer__content > p`
© HATLAND HEADWEAR. ALL RIGHTS RESERVED. `div.grid > div.section-footer__block > div.section-footer__content > p`

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
Wind `div.card-collection > a.card-collection__content-wrapper > div.card-collection__content > h4.card-collection__heading`
Hatland, your headwear specialist `div.section-multitile__content > div > div.section-multitile__text > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#swiper-wrapper-3ea9e322d74f47a9 > div.swiper-slide > div.announcement-bar__text-content > img `div#swiper-wrapper-3ea9e322d74f47a9 > div.swiper-slide > div.announcement-bar__text-content > img`

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.

○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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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

○Form elements have associated labels

○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

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