Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 2 REVIEW 4 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-kupjop

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.

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: #0a0a08

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

8 landmarks

REVIEW

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

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

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

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

Favicon & Branding

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H1 Toute l'Amérique latine, une seule adresse
H2 Le meilleur de l'Amérique latine
H3 Plats
H4 Lomo Saltado 🇵🇪
H4 Pique Macho 🇧🇴
H4 Chicharrón de Chancho 🇧🇴
H3 Boissons
H4 Singani Sour 🇧🇴
H4 Mocochinchi 🇧🇴
H4 Batido Tamarindo
H2 Commandez à emporter
H2 Willy's · Genève
H2 Au cœur de Genève, à 5 minutes de Cornavin
H3 Quartiers desservis
H3 Comment venir
H3 Ouvert 7j/7
H3 Spécialités boliviennes

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

2 decorative image(s) correctly marked

4 image(s) with good alt text

6 images 4 good alt text 2 decorative

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.

Link & Button Quality

29 links, 5 buttons — all OK

PASS

29 links, 5 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://maps.google.com/?q=Rue+de+la+Servette+21+1201+Genève; https://instagram.com/willys_restaurant_bolivien; https://maps.google.com/?q=Rue+de+la+Servette+21+1201+Genève; https://instagram.com/willys_restaurant_bolivien

25 link(s) with descriptive text

29 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.google.com/?q=Rue+de+la+Ser…	Rue de la Servette 21, 1201 Ge…	new tab	Add '(opens in new tab)' to text
https://instagram.com/willys_restaurant_…	@willys_restaurant_bolivien	new tab	Add '(opens in new tab)' to text
https://maps.google.com/?q=Rue+de+la+Ser…	Rue de la Servette 21, 1201 Ge…	new tab	Add '(opens in new tab)' to text
https://instagram.com/willys_restaurant_…	@willys_restaurant_bolivien	new tab	Add '(opens in new tab)' to text

30 links and buttons have descriptive text

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

https://maps.google.com/?q=Rue+de+la+Servette+21+1201+Genève; https://instagram.com/willys_restaurant_bolivien; https://maps.google.com/?q=Rue+de+la+Servette+21+1201+Genève; https://instagram.com/willys_restaurant_bolivien

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

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+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Willy's — Cuisine Latino

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Willy's — Cuisine Latino ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Willy's — Cuisine Latino Display Mode standalone Theme Color #0A0A08 Background Color #FBF6E9 Icons 3 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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 Toute l'Amérique la…	18.24:1	3.0:1	#000000	#F9EED7	Pass
h2 Le meilleur de l'Am�…	18.24:1	3.0:1	#000000	#F9EED7	Pass
h2 Commandez à emporte…	18.24:1	3.0:1	#000000	#F9EED7	Pass
h2 Willy's · Genève	18.24:1	3.0:1	#000000	#F9EED7	Pass
h2 Au cœur de Genève,…	18.24:1	3.0:1	#000000	#F9EED7	Pass
h3 Plats	18.24:1	3.0:1	#000000	#F9EED7	Pass
h3 Boissons	18.24:1	3.0:1	#000000	#F9EED7	Pass
h3 Quartiers desservis	18.24:1	3.0:1	#000000	#F9EED7	Pass
h3 Comment venir	18.24:1	3.0:1	#000000	#F9EED7	Pass
h3 Ouvert 7j/7	18.24:1	3.0:1	#000000	#F9EED7	Pass
h3 Spécialités bolivi…	18.24:1	3.0:1	#000000	#F9EED7	Pass
title Willy's Food — Emp…	18.24:1	4.5:1	#000000	#F9EED7	Pass
a À emporter	18.24:1	4.5:1	#000000	#F9EED7	Pass
a Carte	18.24:1	4.5:1	#000000	#F9EED7	Pass
a À propos	18.24:1	4.5:1	#000000	#F9EED7	Pass
a Contact	18.24:1	4.5:1	#000000	#F9EED7	Pass
a Traiteur	18.24:1	4.5:1	#000000	#F9EED7	Pass
p Une cuisine latino a…	18.24:1	4.5:1	#000000	#F9EED7	Pass
p Ouvert tous les jour…	18.24:1	4.5:1	#000000	#F9EED7	Pass
a Commander à emporte…	18.24:1	4.5:1	#000000	#F9EED7	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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 23 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
Commander à emporter `section.bg-zone-cream > div.container > div.mt-8 > a.inline-flex`
33.– `div.grid > div.rounded-xl > div.flex > span.font-bold`
33.– `div.grid > div.rounded-xl > div.flex > span.font-bold`
23.– `div.grid > div.rounded-xl > div.flex > span.font-bold`
15.– `div.grid > div.rounded-xl > div.flex > span.font-bold`
5.– `div.grid > div.rounded-xl > div.flex > span.font-bold`
8.– `div.grid > div.rounded-xl > div.flex > span.font-bold`
Voir la carte → `section.bg-zone-cream > div.container > div.mt-10 > a.block`
Découvrir la Salteña bolivienne — une spécialité unique à Genève → `section.bg-zone-cream > div.container > div.mt-10 > a.block`
Découvrir l'Amérique Latine à Genève → `section.bg-zone-cream > div.container > div.mt-10 > a.block`
À EMPORTER `main.flex-1 > section.bg-zone-terra > div.container > p.label-eyebrow`
Commander à emporter `section.bg-zone-cream > div.container > div > a.mt-8`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rue de la Servette 21, 1201 Genève Cliquer pour afficher la carte `div.container > div.rounded-xl > div > button.w-full`

○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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

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