Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

Link & Button Quality

Action

7 issue(s) across 41 links and 20 buttons

FIX

7 issue(s) across 41 links and 20 buttons

5 link(s) with no accessible text

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

Got: /; /collections/organic-seamless; /pages/sustainability; /blogs/artist-collabs-blog; /

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /pages/sustainability ("read more")

6 link(s) open in new tab without warning

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

Got: https://moi-basics.com/policies/privacy-policy; https://instagram.com/moibasics; https://www.facebook.com/sustainableunderwear; https://moi-basics.com/; https://instagram.com/moibasics; https://www.facebook.com/sustainableunderwear

1 button(s) with no accessible text

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

Got: button.collapsible-trigger (#162 on page)

29 link(s) with descriptive text

41 links

5 empty

1 generic text

6 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://moi-basics.com/policies/privacy-…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://instagram.com/moibasics	instagram Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sustainableunde…	Facebook	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://moi-basics.com/	moi-basics	new tab	Add '(opens in new tab)' to text
/collections/organic-seamless	(empty)	empty	Add link text or aria-label
/pages/sustainability	read more	generic text	Replace with descriptive text
Before: read more Suggested: Sustainability
/pages/sustainability	(empty)	empty	Add link text or aria-label
/blogs/artist-collabs-blog	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://instagram.com/moibasics	instagram Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sustainableunde…	Facebook	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

48 links and buttons have descriptive text

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

/; /collections/organic-seamless; /pages/sustainability; /blogs/artist-collabs-blog; /

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

Generic link text like 'click here' doesn't describe the destination.

/pages/sustainability ("read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://moi-basics.com/policies/privacy-policy; https://instagram.com/moibasics; https://www.facebook.com/sustainableunderwear; https://moi-basics.com/; https://instagram.com/moibasics; https://www.facebook.com/sustainableunderwear

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.collapsible-trigger (#162 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

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

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

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.

Got: #1c1d1d

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.

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 ✗

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title icon-X ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

title moi-basics / sustainable ethically made …

1.24:1

#000000

#1C1D1D

needs 4.5:1 (normal text)

16px · top of page (header area)

a world of

3.96:1

#000000

#886355

needs 4.5:1 (normal text)

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

a artist collabs

4.18:1

#000000

#926456

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

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

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Sign up and save	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Press	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ultralight, organic,…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 back to shop	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 infos / services / c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title moi-basics / sustain…	1.24:1	4.5:1	#000000	#1C1D1D	Fail
p We use cookies and o…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Manage preferences	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button no, thanks	17.77:1	4.5:1	#000000	#F2EAED	Pass
a Skip to content	12.10:1	4.5:1	#000000	#DCBEB8	Pass
span Free shipping within…	10.67:1	4.5:1	#000000	#D3B2A4	Pass
span Close menu	10.23:1	4.5:1	#000000	#CFAEA2	Pass
a women	10.76:1	4.5:1	#000000	#D6B2A3	Pass
a men	9.92:1	4.5:1	#000000	#CEAB9B	Pass
a world of	3.96:1	4.5:1	#000000	#886355	Fail
a the story	5.53:1	4.5:1	#000000	#A9776A	Pass
a sustainability	4.83:1	4.5:1	#000000	#9D6E5F	Pass
a artist collabs	4.18:1	4.5:1	#000000	#926456	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 86/100 — 4 failing, 27 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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
We use cookies and other technologies to personalize your experience and enhanc… `body.template-index > section#shopify-pc__banner`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Wer Wäsche mit Schnickschnack nichts abgewinnen kann, der sollte moi-basics ins… `div#Testimonials-template--17778706546904__bc36148c-d1ed-4374-b659-310d3092dc52 > div.flickity-viewport > div.flickity-slider > div.testimonials-slide`

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.

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
back to shop `div.page-width > div.grid > div.grid__item > button.footer__title`
infos / services / contact `div.page-width > div.grid > div.grid__item > button.footer__title`
newsletter `div.page-width > div.grid > div.grid__item > button.footer__title`
© 2026 moi-basics , Hohlstrasse 420, CH-8048 Zürich `div.page-width > div.site-footer__bottom > div.footer__copyright > span.footer__copyright`

These are opportunities to improve the legibility of your content.

Names and labels

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.header-layout > div.header-item > h1#LogoContainer > a.site-header__logo-link `div.header-layout > div.header-item > h1#LogoContainer > a.site-header__logo-link`
div.feature-row > div.feature-row__item > div.feature-row__first-image > a `div.feature-row > div.feature-row__item > div.feature-row__first-image > a`
div.feature-row > div.feature-row__item > div.feature-row__first-image > a `div.feature-row > div.feature-row__item > div.feature-row__first-image > a`
div.feature-row > div.feature-row__item > div.feature-row__first-image > a `div.feature-row > div.feature-row__item > div.feature-row__first-image > a`
div.grid__item > div.footer__logo-social > div.footer__logo > a `div.grid__item > div.footer__logo-social > div.footer__logo > 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.

○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

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

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

○`[accesskey]` values are unique

○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

○Tables have different content in the summary attribute and `<caption>`.

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

A+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

9 headings

PASS

9 headings

Single H1 present

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 moi-basics
H2 Sign up and save
H2 (empty)
H2 Press
H2 ultralight, organic, breathable
H2 (empty)
H2 back to shop
H2 infos / services / contact
H2 newsletter

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Heading Text Quality

All 9 heading(s) have substantive, well-formed text

PASS

All 9 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

1 of 17 images have issues

PASS

1 of 17 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

14 decorative image(s) correctly marked

2 image(s) with good alt text

17 images 2 good alt text 14 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 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#CartTermsDrawer	checkbox	I agree with the terms and conditions	for/id
#Search	search	Search	for/id
#Email-footer-2	email	Enter your email	for/id

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

Mobile-Readable Font Sizes

All 48 visible text node(s) render at >= 12 CSS pixels

PASS

All 48 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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.

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