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 4 REVIEW 4 FIX

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

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

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Error: Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

h2 Book Your Experience

2.25:1

#000000

#3A4950

needs 3.0:1 (large text)

24px · bottom of viewport

h3 MORNING WELLNESS

2.25:1

#000000

#3A4950

needs 3.0:1 (large text)

19px · bottom of viewport

h3 PRIVATE CELEBRATIONS

2.25:1

#000000

#3A4950

needs 3.0:1 (large text)

19px · bottom of viewport

h3 CORPORATE & COMMUNITY EVENTS

2.25:1

#000000

#3A4950

needs 3.0:1 (large text)

19px · bottom of viewport

h3 COLLABORATIONS

2.25:1

#000000

#3A4950

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Premium mobile bever…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 The Art of the	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h2 Beverage Experience	18.59:1	3.0:1	#000000	#F1F1F1	Pass
h2 EXPERIENCES & PARTNE…	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 mobile beverage bar …	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h2 Book Your Experience	2.25:1	3.0:1	#000000	#3A4950	Fail
h3 ART BRUNCHES & CREAT…	17.62:1	3.0:1	#000000	#EBEBEB	Pass
h3 MORNING WELLNESS	2.25:1	3.0:1	#000000	#3A4950	Fail
h3 PRIVATE CELEBRATIONS	2.25:1	3.0:1	#000000	#3A4950	Fail
h3 CORPORATE & COMMUNIT…	2.25:1	3.0:1	#000000	#3A4950	Fail
h3 COLLABORATIONS	2.25:1	3.0:1	#000000	#3A4950	Fail
title Mobile Beverage Bar …	20.65:1	4.5:1	#000000	#FFFDF7	Pass
span top of page	20.65:1	4.5:1	#000000	#FFFDF7	Pass
button Skip to Main Content	20.65:1	4.5:1	#000000	#FFFDF7	Pass
span HOME	20.65:1	4.5:1	#000000	#FFFDF7	Pass
span MENU	20.65:1	4.5:1	#000000	#FFFDF7	Pass
span CONTACT & PRICING	20.65:1	4.5:1	#000000	#FFFDF7	Pass
span PRIVACY POLICY	13.00:1	4.5:1	#000000	#C9CDC3	Pass
span TERMS OF SERVICE	12.26:1	4.5:1	#000000	#BFC9B8	Pass
span ACCESSIBILITY STATEM…	18.43:1	4.5:1	#000000	#F0F0F0	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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H1 Premium mobile beverage bar miami for unforgettable events
H2 The Art of the Beverage Experience
H2 EXPERIENCES & PARTNERSHIPS mobile beverage bar miami
H3 ART BRUNCHES & CREATIVE EVENTS
H3 MORNING WELLNESS
H3 PRIVATE CELEBRATIONS
H3 CORPORATE & COMMUNITY EVENTS
H3 COLLABORATIONS
H4 PARTNERSHIPS
H2 Book Your Experience

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

4 decorative image(s) correctly marked

8 image(s) with good alt text

12 images 8 good alt text 4 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

15 links, 2 buttons — all OK

PASS

15 links, 2 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://www.instagram.com/solandcitrus.miami/; https://www.tiktok.com/@sol.citrus.miami; https://www.facebook.com/share/1b9XhLz2jw/?mibextid=wwXIfr

12 link(s) with descriptive text

15 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/solandcitrus.m…	Camera icon for a mobile bever…	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sol.citrus.miami	TikTok logo for mobile beverag…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1b9XhLz2j…	Facebook icon for our mobile b…	new tab	Add '(opens in new tab)' to text

14 links and buttons have descriptive text

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

https://www.instagram.com/solandcitrus.miami/; https://www.tiktok.com/@sol.citrus.miami; https://www.facebook.com/share/1b9XhLz2jw/?mibextid=wwXIfr

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 "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

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

PASS

11 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+

Mobile-Readable Font Sizes

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

PASS

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

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

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

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Lighthouse Accessibility Audits

Score 92/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.

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
Sol-&-Citrus-logo `div#comp-kbgakxmn_r_comp-mt8660yc > div#comp-kbgakxmn_r_comp-mt8660zr > div#comp-kbgakxmn_r_comp-mt0gh5ct > a._linkLayer_ackza_12`
Camera icon for a mobile beverage bar miami photo gallery `div#comp-kbgakxmn_r_comp-mt8660yc > div#comp-kbgakxmn_r_comp-mt8660zr > div#comp-kbgakxmn_r_comp-mtf6gbct > a._linkLayer_1vtez_44`
TikTok logo for mobile beverage bar Miami `div#comp-kbgakxmn_r_comp-mt8660yc > div#comp-kbgakxmn_r_comp-mt8660zr > div#comp-kbgakxmn_r_comp-mtf6gbio > a._linkLayer_1vtez_44`
Facebook icon for our mobile beverage bar Miami page `div#comp-kbgakxmn_r_comp-mt8660yc > div#comp-kbgakxmn_r_comp-mt8660zr > div#comp-kbgakxmn_r_comp-mtf6gbpe > a._linkLayer_1vtez_44`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Powered by Usercentrics Consent Management `div#main-view > div#mid-container > span.poweredBy > a`

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.

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

●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

●No element has a `[tabindex]` value greater than 0

●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

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

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

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