https://wee-san-flavors-website.lovable.app

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

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

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

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

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

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No banner (header) landmark

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Link & Button Quality

2 issue(s) across 22 links and 6 buttons

REVIEW

2 issue(s) across 22 links and 6 buttons

2 link(s) with no accessible text

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

Got: /cart; /cart

3 link(s) open in new tab without warning

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

Got: https://wa.me/41000000000; https://instagram.com; https://wa.me/41000000000

17 link(s) with descriptive text

22 links

2 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/41000000000	Chat on WhatsApp	new tab	Add '(opens in new tab)' to text
/cart	(empty)	empty	Add link text or aria-label
/cart	(empty)	empty	Add link text or aria-label
https://instagram.com	Instagram	new tab	Add '(opens in new tab)' to text
https://wa.me/41000000000	WhatsApp	new tab	Add '(opens in new tab)' to text

23 links and buttons have descriptive text

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

/cart; /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

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

https://wa.me/41000000000; https://instagram.com; https://wa.me/41000000000

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

Mobile-Readable Font Sizes

Action

75% of visible text renders at >= 12 CSS px (25 below threshold)

REVIEW

75% of visible text renders at >= 12 CSS px (25 below threshold)

25 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 ("08:00"); <span> 11.0px ("13:30"); <span> 11.0px ("08:00"); <span> 11.0px ("13:00"); <span> 11.0px ("08:00").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA 2 pass AA only

h2 Nos Spécialités

1.12:1

#000000

#1E0E07

needs 3.0:1 (large text)

24px · bottom of viewport

a À Propos

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Menu

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

a Horaires

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

a Traiteur

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

a Commander

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

a Commander

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

p Cuisine de Rue Asiatique — Genève

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

p Cuisine de Rue Asiatique Authentique —…

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · above the fold

a Commander

3.77:1

#000000

#CD0E4E

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Wee San	3.77:1	3.0:1	#000000	#CD0E4E	Pass
h2 Notre Histoire	3.77:1	3.0:1	#000000	#CD0E4E	Pass
h2 Nos Spécialités	1.12:1	3.0:1	#000000	#1E0E07	Fail
h2 Cette Semaine	11.40:1	3.0:1	#000000	#F3B26C	Pass
h2 Services Traiteur	11.40:1	3.0:1	#000000	#F3B26C	Pass
h3 Menu Sur Mesure	11.40:1	3.0:1	#000000	#F3B26C	Pass
h3 Tout Événement	11.40:1	3.0:1	#000000	#F3B26C	Pass
h3 Expérience Unique	11.40:1	3.0:1	#000000	#F3B26C	Pass
title Wee San — Cuisine …	19.22:1	4.5:1	#000000	#FBF4E9	Pass
span Wee	19.22:1	4.5:1	#000000	#FBF4E9	Pass
span San	19.22:1	4.5:1	#000000	#FBF4E9	Pass
a À Propos	3.77:1	4.5:1	#000000	#CD0E4E	Fail
a Menu	3.77:1	4.5:1	#000000	#CD0E4E	Fail
a Horaires	3.77:1	4.5:1	#000000	#CD0E4E	Fail
a Traiteur	3.77:1	4.5:1	#000000	#CD0E4E	Fail
a Commander	3.77:1	4.5:1	#000000	#CD0E4E	Fail
a Commander	3.77:1	4.5:1	#000000	#CD0E4E	Fail
p Cuisine de Rue Asiat…	3.77:1	4.5:1	#000000	#CD0E4E	Fail
p Cuisine de Rue Asiat…	3.77:1	4.5:1	#000000	#CD0E4E	Fail
a Commander	3.77:1	4.5:1	#000000	#CD0E4E	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+

Heading Hierarchy

8 headings

PASS

8 headings

Single H1 present

H1 Wee San
H2 Notre Histoire
H2 Nos Spécialités
H2 Cette Semaine
H2 Services Traiteur
H3 Menu Sur Mesure
H3 Tout Événement
H3 Expérience Unique

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

4 images 4 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "fr"

PASS

Lang attribute set to "fr"

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

Got: fr

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+

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

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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 21 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
CUISINE DE RUE ASIATIQUE — GENÈVE `div.relative > div.max-w-md > div.hero-fade-up > p.font-label`
Cuisine de Rue Asiatique Authentique — Fraîche, Rapide & Savoureuse `section.relative > div.relative > div.max-w-md > p.hero-fade-up`
Cuisine de rue thaïlandaise & vietnamienne, fraîche et savoureuse — Genève. `div.container > div.grid > div.md:pr-10 > p.text-white/70`
LIENS RAPIDES `div.container > div.grid > div.md:px-10 > p.font-label`
OÙ NOUS TROUVER `div.container > div.grid > div.md:pl-10 > p.font-label`
LUN `div.md:pl-10 > ul.space-y-1.5 > li.text-white/90 > span.font-label`
MAR `div.md:pl-10 > ul.space-y-1.5 > li.text-white/90 > span.font-label`
JEU `div.md:pl-10 > ul.space-y-1.5 > li.text-white/90 > span.font-label`
VEN `div.md:pl-10 > ul.space-y-1.5 > li.text-white/90 > span.font-label`
SAM `div.md:pl-10 > ul.space-y-1.5 > li.text-white/90 > span.font-label`
© 2026 Wee San. Tous droits réservés. `footer.bg-primary > div.container > div.border-t > p.text-white/60`
Dashboard `footer.bg-primary > div.container > div.border-t > a.inline-flex`

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#root > nav.fixed > div.flex > a.relative `div#root > nav.fixed > div.flex > a.relative`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●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

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

●Deprecated ARIA roles were not used

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

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

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

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

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