Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

Link & Button Quality

Action

4 issue(s) across 46 links and 10 buttons

FIX

4 issue(s) across 46 links and 10 buttons

2 link(s) with no accessible text

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

Got: https://sevano.com/customer_authentication/redirect?locale=en&region_country=ES; /cart

1 link(s) with generic text

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

Got: /pages/our-philosophy ("Learn More")

12 link(s) open in new tab without warning

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

Got: https://www.instagram.com/sevano; https://www.tiktok.com/@sevano; https://www.youtube.com/@sevanoswiss; https://x.com/sevanoswiss; https://www.pinterest.com/sevanoswiss; https://www.linkedin.com/company/sevanoswiss; https://www.instagram.com/sevano; https://www.tiktok.com/@sevano; https://www.youtube.com/@sevanoswiss; https://x.com/sevanoswiss (+2 more)

1 button(s) with no accessible text

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

Got: button.menu-drawer__close (#326 on page)

31 link(s) with descriptive text

46 links

2 empty

1 generic text

12 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://sevano.com/customer_authenticati…	(empty)	empty	Add link text or aria-label
/cart	(empty)	empty	Add link text or aria-label
/pages/our-philosophy	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Our Philosophy
https://www.instagram.com/sevano	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sevano	TikTok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@sevanoswiss	YouTube	new tab	Add '(opens in new tab)' to text
https://x.com/sevanoswiss	X	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/sevanoswiss	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/sevanos…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/sevano	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sevano	TikTok	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@sevanoswiss	YouTube	new tab	Add '(opens in new tab)' to text
https://x.com/sevanoswiss	X	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/sevanoswiss	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/sevanos…	LinkedIn	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

40 links and buttons have descriptive text

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

https://sevano.com/customer_authentication/redirect?locale=en&region_country=ES; /cart

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/our-philosophy ("Learn 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://www.instagram.com/sevano; https://www.tiktok.com/@sevano; https://www.youtube.com/@sevanoswiss; https://x.com/sevanoswiss; https://www.pinterest.com/sevanoswiss; https://www.linkedin.com/company/sevanoswiss; https://www.instagram.com/sevano; https://www.tiktok.com/@sevano; https://www.youtube.com/@sevanoswiss; https://x.com/sevanoswiss (+2 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.menu-drawer__close (#326 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.

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 ✗

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="email" name="contact[email]">; <input type="email" name="contact[email]">

1 control(s) properly labeled

3 controls

1 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#Search-In-Drawer	search	Search	aria-label
contact[email]	email	(Your email address)	placeholder only
contact[email]	email	(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

Mobile-Readable Font Sizes

Action

81% of visible text renders at >= 12 CSS px (11 below threshold)

REVIEW

81% of visible text renders at >= 12 CSS px (11 below threshold)

11 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.2px ("Menu"); <a> 11.2px ("Fragrances"); <a> 11.2px ("Sample Kit"); <a> 11.2px ("Our Philosophy"); <a> 11.2px ("Craftmanship").

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H2 Your cart is empty
H3 Fragrance
H3 Fragrance
H2 Your cart
H2 Estimated total
H1 The Essence of Swiss Refinement
H2 Explore Our Fragrances
H3 Verca
H3 Roya
H3 Omega
H2 Begin your fragrance journey
H2 Our Philosophy
H2 Join the SEVANO Circle
H3 SEVANO
H3 Support
H3 Join our World
H3 Follow us
H3 Follow us

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

Alt Text Quality

2 of 19 images have issues

PASS

2 of 19 images have issues

2 image(s) with generic alt text

1 decorative image(s) correctly marked

16 image(s) with good alt text

19 images 16 good alt text 1 decorative 2 generic

Issue	Count
generic	2 image(s)

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

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

PASS

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

No tabindex anti-patterns detected

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

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+

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 The Essence of Swiss…	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h2 Your cart is empty	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h2 Your cart	17.51:1	3.0:1	#000000	#FAE8CF	Pass
h2 Estimated total	17.55:1	3.0:1	#000000	#FBE8CF	Pass
h2 Explore Our Fragranc…	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h2 Begin your fragrance…	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h2 Our Philosophy	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h2 Join the SEVANO Circ…	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Verca	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Roya	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Omega	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 SEVANO	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Support	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Join our World	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Follow us	16.89:1	3.0:1	#000000	#F6E4CC	Pass
h3 Follow us	16.89:1	3.0:1	#000000	#F6E4CC	Pass
title Sevano – Swiss Nic…	16.89:1	4.5:1	#000000	#F6E4CC	Pass
a Skip to content	16.89:1	4.5:1	#000000	#F6E4CC	Pass
a Continue shopping	17.56:1	4.5:1	#000000	#FBE8D0	Pass
p Have an account?	17.56:1	4.5:1	#000000	#FBE8D0	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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 passed

PASS

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.

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
YOUR SCENT STORY `section > div > div > p`
© 2026 SEVANO – All rights reserved `div#shopify-section-sections--29779419857244__footer > footer.footer > div.footer__bottom > p.section-subtext`
Imprint · Privacy · Terms `div#shopify-section-sections--29779419857244__footer > footer.footer > div.footer__bottom > p.section-subtext`
Imprint `footer.footer > div.footer__bottom > p.section-subtext > a`
Privacy `footer.footer > div.footer__bottom > p.section-subtext > a`
Terms `footer.footer > div.footer__bottom > p.section-subtext > a`

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
sticky-header.header-wrapper > header.header > div.header__icons > a.header__icon `sticky-header.header-wrapper > header.header > div.header__icons > a.header__icon`
sticky-header.header-wrapper > header.header > div.header__icons > a#cart-icon-bubble `sticky-header.header-wrapper > header.header > div.header__icons > a#cart-icon-bubble`

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

●Form elements have associated labels

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

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

●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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○Links are distinguishable without relying on color.

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

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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