Skip to content
https://www.menuella.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
83
GRADE
B
FIX
4
REVIEW
5
PASS
15
INFO
0
Checks
24
15 PASS 5 REVIEW 4 FIX
D
Mobile-Readable Font Sizes
Action
68% of visible text renders at >= 12 CSS px (103 below threshold)
FIX
68% of visible text renders at >= 12 CSS px (103 below threshold)
Warning::
103 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> 10.0px ("your-restaurant.co.uk"); <h2> 9.0px ("The Royal Oak Gastropub Menu"); <span> 7.0px ("42 High Street, SW1A 1AA London"); <span> 7.0px ("Mon–Sat 12:00–23:00"); <span> 7.0px ("Pickup").
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Menuella
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Menuella ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Menuella Display Mode standalone Theme Color #ffe11a Background Color #ffe11a Icons 1 icon(s)
D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
No navigation patterns
FIX
No navigation patterns
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 7 <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
Landmark Structure
26 landmarks
REVIEW
26 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
5 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV "Main navigation" MAIN ASIDE "Main menu" CONTENTINFO footer

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

B
Tabindex Anti-Patterns
0 positive, 4 -1-on-focusable
REVIEW
0 positive, 4 -1-on-focusable
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color white ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 The AI platform for your restaurant.
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Menuella Platform Explorer
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Royal Oak Gastropub Menu
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Royal Oak Gastropub Menu
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Royal Oak Gastropub Menu
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Royal Oak Gastropub Menu
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Royal Oak Gastropub Menu
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stop Losing Revenue to Commission Fees
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Three beliefs that guide Menuella
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Menuella
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Loved by Restaurants Worldwide
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently asked questions
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ideas for growing your restaurant
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get everything your restaurant needs to …
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We value your privacy
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Restaurant website
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Online ordering
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Loyalty & Rewards
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Marketing Automation
2.64:1
#000000
on
#674B3A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The AI platform for …2.64:13.0:1
#000000
#674B3A
Fail
h2 Menuella Platform Ex…2.64:13.0:1
#000000
#674B3A
Fail
h2 The Royal Oak Gastro…2.64:13.0:1
#000000
#674B3A
Fail
h2 The Royal Oak Gastro…2.64:13.0:1
#000000
#674B3A
Fail
h2 The Royal Oak Gastro…2.64:13.0:1
#000000
#674B3A
Fail
h2 The Royal Oak Gastro…2.64:13.0:1
#000000
#674B3A
Fail
h2 The Royal Oak Gastro…2.64:13.0:1
#000000
#674B3A
Fail
h2 Welcome to The Royal…7.94:13.0:1
#FFFFFF
#674B3A
Pass
h2 Stop Losing Revenue …2.64:13.0:1
#000000
#674B3A
Fail
h2 Three beliefs that g…2.64:13.0:1
#000000
#674B3A
Fail
h2 Why Menuella2.64:13.0:1
#000000
#674B3A
Fail
h2 Loved by Restaurants…2.64:13.0:1
#000000
#674B3A
Fail
h2 Frequently asked que…2.64:13.0:1
#000000
#674B3A
Fail
h2 Ideas for growing yo…2.64:13.0:1
#000000
#674B3A
Fail
h2 Get everything your …2.64:13.0:1
#000000
#674B3A
Fail
h2 We value your privac…2.64:13.0:1
#000000
#674B3A
Fail
h3 Restaurant website2.64:13.0:1
#000000
#674B3A
Fail
h3 Online ordering2.64:13.0:1
#000000
#674B3A
Fail
h3 Loyalty & Rewards2.64:13.0:1
#000000
#674B3A
Fail
h3 Marketing Automation2.64:13.0:1
#000000
#674B3A
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
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 The AI platform for your restaurant.
  • H2 Menuella Platform Explorer
  • H3 Restaurant website
  • H2 The Royal Oak Gastropub Menu
  • H2 The Royal Oak Gastropub Menu
  • H2 The Royal Oak Gastropub Menu
  • H2 The Royal Oak Gastropub Menu
  • H2 The Royal Oak Gastropub Menu
  • H3 Online ordering
  • H3 Loyalty & Rewards
  • H3 Marketing Automation
  • H3 Link Pages
  • H2 Welcome to The Royal Oak Gastropub
  • H3 Short Links
  • H3 Media Gallery
  • H2 Stop Losing Revenue to Commission Fees
  • H2 Three beliefs that guide Menuella
  • H3 Restaurants don't need more tools — they need one connected system.
  • H3 Every feature should create compounding value.
  • H3 Restaurants should stay in control — always.
  • H2 Why Menuella
  • H2 Loved by Restaurants Worldwide
  • H2 Frequently asked questions
  • H2 Ideas for growing your restaurant
  • H2 Get everything your restaurant needs to grow online—with Menuella on one platform.
  • H3 Digital presence & visibility
  • H3 Guest experience & loyalty
  • H3 Direct ordering & revenue
  • H3 Operations & in-venue tools
  • H3 Resources
  • H3 Company
  • H3 Free Tools
  • H3 Get Started
  • H2 We value your privacy
A+
Heading Text Quality
All 34 heading(s) have substantive, well-formed text
PASS
All 34 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
All 65 images OK
PASS
All 65 images OK
Info::
12 image(s) with alt text over 125 characters
Info::
28 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
65 images 25 good alt text 28 decorative
IssueCount
too long12 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#consent-analyticscheckboxAnalyticsfor/id
#consent-marketingcheckboxMarketingfor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
Favicon & Branding
5 icon(s) detected
PASS
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 100/100 — 0 failing, 27 passed
PASS
100

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.

○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
●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
●Background and foreground colors have a sufficient contrast ratio
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○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.

Send Feedback