Skip to content
https://ttmb-coffee.surge.sh

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 (missing!) CONTENTINFO footer

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

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

D
Heading Hierarchy
Action
89 headings, 3 skip(s)
FIX
89 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Melbourne Specialty Coffee Meets Jumeirah's Tranquility
  • H5 Mariam Al-Maktoum skipped
  • H5 Alexandre Dupont
  • H5 Noura Al-Khaja
  • H5 Sarah Jenkins
  • H5 Rashid Al-Nuaimi
  • H5 Elena Rostova
  • H5 Mariam Al-Maktoum
  • H5 Alexandre Dupont
  • H5 Noura Al-Khaja
  • H5 Sarah Jenkins
  • H5 Rashid Al-Nuaimi
  • H5 Elena Rostova
  • H2 A Secluded Courtyard at La Plage
  • H3 Shaded Courtyard Garden
  • H3 Terrazzo Espresso & Brew Bar
  • H3 Sun-Dappled Terrace Dining
  • H3 Grazia Middle East Feature
  • H3 Minimalist Oak & Clay Banquettes
  • H3 Night Atmosphere & Neon Facade
  • H2 Precision Pour-Overs & Micro-Lot Roasts
  • H4 Salma Bermudez Colombia Anaerobic skipped
  • H2 Dine-In Menu & Creations
  • H3 Hot Ricotta Pancakes
  • H3 Herby Smashed Avo
  • H3 Dates & Cocoa Nib Granola
  • H3 For The Love Of Bread
  • H3 Very Green Breakfast
  • H3 Mediterranean Mushroom Toast
  • H3 Bacon & Cheese Melt Toast
  • H3 Artisan Cheese & Jam Toast
  • H3 TTMB Classic Cheeseburger with Fries
  • H3 Breakfast Roll Bagel
  • H3 Smoked Turkey & Avocado Bagel
  • H3 Middle Eastern-Ish Bagel
  • H3 Smoked Salmon & Caperberry Bagel
  • H3 Artisan Smoked Pastrami Sandwich
  • H3 Classic Beef Lasagna Bolognese
  • H3 Roasted Salmon & Cracked Wheat Salad
  • H3 Who Doesn't Like Falafel
  • H3 Crispy Spiced Pakora Fritters
  • H3 Wheat Pearls & Chicken Salad
  • H3 Quinoa Shrimp & Roasted Pumpkin Salad
  • H3 French Lentil & Flaked Salmon Salad
  • H3 Tropical Acai Bowl
  • H3 Protein Acai Energy Bowl
  • H3 Outer Space Signature Cheesecake
  • H3 Half Moon Valrhona Chocolate Cake
  • H3 Seriously Good Banana Pudding
  • H3 Torta Di Nocciole (Italian Hazelnut Cake)
  • H3 Giant Dark Choc Chip Sea Salt Cookie
  • H3 18-Hour Slow Steeped Cold Brew
  • H3 Iced Spanish Latte
  • H3 Iced Vanilla Flat White
  • H3 Iced Specialty Latte
  • H3 Iced Dark Chocolate Mocha
  • H3 Iced Long Black
  • H3 Iced Hibiscus Blossom Tea
  • H3 Iced Lemon Earl Grey Tea
  • H3 Iced Spiced Chai Latte
  • H3 Artisan Iced Chocolate
  • H3 Iced Chai Chocolate Fusion
  • H3 Fresh Cold-Pressed Orange Juice
  • H3 TTMB Anniversary Chocolate Box
  • H3 Anniversary Collector's Bundle
  • H3 Colombia Micro-Lot Drip Bags (Box of 8)
  • H3 Ethiopia Yirgacheffe Drip Bags (Box of 8)
  • H3 Kenya Kainamui Drip Bags (Box of 8)
  • H3 Colombia Finca Julia Drip Bags (Box of 8)
  • H3 Brazil Santa Ines Drip Bags (Box of 8)
  • H3 Salma Bermudez Colombia Filter (250g)
  • H3 Letty Bermudez Colombia Filter (250g)
  • H3 Diego Bermudez Colombia Filter (250g)
  • H3 Samuel Junior Bermudez Colombia (250g)
  • H3 Sweet Valley Colombia Filter (250g)
  • H3 Felipe Contreras Guatemala Filter (250g)
  • H3 Janson X 819 Panama Geisha Filter (250g)
  • H3 Viani Colombia Filter (250g)
  • H3 No dishes found
  • H2 Visit To The Moon & Back
  • H4 Physical Address skipped
  • H4 Operating Hours
  • H4 Valet & Street Parking
  • H5 To The Moon & Back Coffee
  • H3 Moments Under The Moon
  • H3 (empty)
  • H3 Courtyard Table Reservation
  • H4 Reservation Request Logged!
  • H4 (empty)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

F
Form Accessibility
Action
7 of 9 controls have issues
FIX
7 of 9 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="bookGuests">; <input type="date" id="bookDate">; <select id="bookTime">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="menuSearchInput">; <input type="text" id="bookName">; <input type="tel" id="bookPhone">; <textarea id="bookNotes">
Info::
2 control(s) properly labeled
9 controls
2 labeled
4 placeholder only
3 unlabeled
ControlTypeLabelMethod
seatingradionone
seatingradionone
#bookPhonetel(+971 50 XXX XXXX)placeholder only
#menuSearchInputtext(Search dishes, coffee, sweets...)placeholder only
#bookNametext(e.g. Sarah Al-Maktoum)placeholder only
#bookNotestextarea(Dietary restrictions, celebration, high chair...)placeholder only
#bookGuestsselect(none)none
#bookDatedate(none)none
#bookTimeselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select id="bookGuests">; <input type="date" id="bookDate">; <select id="bookTime">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" id="menuSearchInput">; <input type="text" id="bookName">; <input type="tel" id="bookPhone">; <textarea id="bookNotes">

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

D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel.
Got: <input type="tel" id="bookPhone">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel.
Got: <input type="tel" id="bookPhone">
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #080b11
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile-Readable Font Sizes
Action
80% of visible text renders at >= 12 CSS px (34 below threshold)
REVIEW
80% of visible text renders at >= 12 CSS px (34 below threshold)
Warning::
34 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> 9.0px ("JUMEIRAH 2"); <span> 10.0px ("4.4 ★"); <span> 10.0px ("(450+ Google Reviews)"); <span> 10.0px ("Hot Ricotta Pancakes"); <span> 10.0px ("Google Review").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 A Secluded Courtyard at La Plage
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Precision Pour-Overs & Micro-Lot Roasts
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dine-In Menu & Creations
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Visit To The Moon & Back
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Shaded Courtyard Garden
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Terrazzo Espresso & Brew Bar
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sun-Dappled Terrace Dining
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Grazia Middle East Feature
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Minimalist Oak & Clay Banquettes
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Night Atmosphere & Neon Facade
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Hot Ricotta Pancakes
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Herby Smashed Avo
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Dates & Cocoa Nib Granola
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 For The Love Of Bread
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Very Green Breakfast
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mediterranean Mushroom Toast
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bacon & Cheese Melt Toast
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Artisan Cheese & Jam Toast
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TTMB Classic Cheeseburger with Fries
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Breakfast Roll Bagel
1.05:1
#000000
on
#06090F
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 A Secluded Courtyard…1.05:13.0:1
#000000
#06090F
Fail
h2 Precision Pour-Overs…1.05:13.0:1
#000000
#06090F
Fail
h2 Dine-In Menu & Creat…1.05:13.0:1
#000000
#06090F
Fail
h2 Visit To The Moon & …1.05:13.0:1
#000000
#06090F
Fail
h3 Shaded Courtyard Gar…1.05:13.0:1
#000000
#06090F
Fail
h3 Terrazzo Espresso & …1.05:13.0:1
#000000
#06090F
Fail
h3 Sun-Dappled Terrace …1.05:13.0:1
#000000
#06090F
Fail
h3 Grazia Middle East F…1.05:13.0:1
#000000
#06090F
Fail
h3 Minimalist Oak & Cla…1.05:13.0:1
#000000
#06090F
Fail
h3 Night Atmosphere & N…1.05:13.0:1
#000000
#06090F
Fail
h3 Hot Ricotta Pancakes1.05:13.0:1
#000000
#06090F
Fail
h3 Herby Smashed Avo1.05:13.0:1
#000000
#06090F
Fail
h3 Dates & Cocoa Nib Gr…1.05:13.0:1
#000000
#06090F
Fail
h3 For The Love Of Brea…1.05:13.0:1
#000000
#06090F
Fail
h3 Very Green Breakfast1.05:13.0:1
#000000
#06090F
Fail
h3 Mediterranean Mushro…1.05:13.0:1
#000000
#06090F
Fail
h3 Bacon & Cheese Melt …1.05:13.0:1
#000000
#06090F
Fail
h3 Artisan Cheese & Jam…1.05:13.0:1
#000000
#06090F
Fail
h3 TTMB Classic Cheeseb…1.05:13.0:1
#000000
#06090F
Fail
h3 Breakfast Roll Bagel1.05:13.0:1
#000000
#06090F
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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 4 failing, 11 passed
REVIEW
79

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#mainHeaderWrapper > header.max-w-7xl > div.flex > button#mobileMenuBtn div#mainHeaderWrapper > header.max-w-7xl > div.flex > button#mobileMenuBtn

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.

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
Independent Melbourne-standard specialty coffee & courtyard cafe at La Plage Re… footer.bg-space-950 > div.max-w-7xl > div.space-y-2.5 > p.text-slate-500
© 2026 To The Moon & Back Coffee. All rights reserved. body.celestial-bg > footer.bg-space-950 > div.max-w-7xl > div.text-slate-600

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mariam Al-Maktoum div.flex > div.flex > div.leading-tight > h5.text-sm
Salma Bermudez Colombia Anaerobic div.absolute > div.flex > div > h4.text-white
Physical Address div.p-6 > div.flex > div > h4.text-white

These are opportunities to improve keyboard navigation in your application.

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.scroll-smooth html.scroll-smooth

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-hidden="true"]` is not present on the document `<body>`
●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-hidden="true"]` elements do not contain focusable descendents
●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
●Links have a discernible name
●Touch targets have sufficient size and spacing.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
A+
Heading Text Quality
All 89 heading(s) have substantive, well-formed text
PASS
All 89 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::
65 image(s) with good alt text
65 images 65 good alt text
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "menuSearchInput" should use type="search" (currently type="text")
Field name "menuSearchInput" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
9 form control(s) checked, no input-semantic issues
PASS
9 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: To The Moon & Back (TTMB)
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name To The Moon & Back (TTMB) ✓192×192 icon ✓512×512 icon ✓Start URL ./index.html ✓Display Mode standalone ✓
Name To The Moon & Back (TTMB) Display Mode standalone Theme Color #0A0E17 Background Color #06080E Icons 2 icon(s)
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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback