Skip to content
https://menu-cactus.ir

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
84
GRADE
B
FIX
3
REVIEW
4
PASS
17
INFO
0
Checks
24
17 PASS 4 REVIEW 3 FIX
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: #090c09
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::
1 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 1 <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
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 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: کاکتوس
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name کاکتوس ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name کاکتوس Display Mode standalone Theme Color #090c09 Background Color #090c09 Icons 2 icon(s)
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
h1 طعمی تازه و هیجان‌انگ…
1.35:1
#000000
on
#28231A
needs 3.0:1 (large text)
32px · top of page (header area)
h2 موردی پیدا نشد
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 جوسی برگر
1.35:1
#000000
on
#28231B
needs 3.0:1 (large text)
19px · mid-page
h3 ماشروم برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 مگابرگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 اسموکی برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 هالوپینو برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 زینگر برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 اسپین برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 دوبل برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 کینگ‌برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 مگا زینگر برگر
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پاستا مرغ آلفردو
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پاستا مرغ پستو
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پاستا گوشت آلفردو
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پیتزا مخصوص کاکتوس
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پیتزا چیکن
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پیتزا سیر استیک
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پیتزا پپرونی
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پیتزا چهار فصل
1.34:1
#000000
on
#26231A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 طعمی تازه و…1.35:13.0:1
#000000
#28231A
Fail
h2 موردی پیدا …1.34:13.0:1
#000000
#26231A
Fail
h3 جوسی برگر1.35:13.0:1
#000000
#28231B
Fail
h3 ماشروم برگØ…1.34:13.0:1
#000000
#26231A
Fail
h3 مگابرگر1.34:13.0:1
#000000
#26231A
Fail
h3 اسموکی برگØ…1.34:13.0:1
#000000
#26231A
Fail
h3 هالوپینو بØ…1.34:13.0:1
#000000
#26231A
Fail
h3 زینگر برگر1.34:13.0:1
#000000
#26231A
Fail
h3 اسپین برگر1.34:13.0:1
#000000
#26231A
Fail
h3 دوبل برگر1.34:13.0:1
#000000
#26231A
Fail
h3 کینگ‌برگر1.34:13.0:1
#000000
#26231A
Fail
h3 مگا زینگر ب…1.34:13.0:1
#000000
#26231A
Fail
h3 پاستا مرغ آ…1.34:13.0:1
#000000
#26231A
Fail
h3 پاستا مرغ پ…1.34:13.0:1
#000000
#26231A
Fail
h3 پاستا گوشت …1.34:13.0:1
#000000
#26231A
Fail
h3 پیتزا مخصوØ…1.34:13.0:1
#000000
#26231A
Fail
h3 پیتزا چیکن1.34:13.0:1
#000000
#26231A
Fail
h3 پیتزا سیر ا…1.34:13.0:1
#000000
#26231A
Fail
h3 پیتزا پپروÙ…1.34:13.0:1
#000000
#26231A
Fail
h3 پیتزا چهار …1.34:13.0:1
#000000
#26231A
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
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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
44 headings, 1 skip(s)
PASS
44 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 طعمی تازه و هیجان‌انگیز، برای عاشقان طعم‌های خاص
  • H3 جوسی برگر skipped
  • H3 ماشروم برگر
  • H3 مگابرگر
  • H3 اسموکی برگر
  • H3 هالوپینو برگر
  • H3 زینگر برگر
  • H3 اسپین برگر
  • H3 دوبل برگر
  • H3 کینگ‌برگر
  • H3 مگا زینگر برگر
  • H3 پاستا مرغ آلفردو
  • H3 پاستا مرغ پستو
  • H3 پاستا گوشت آلفردو
  • H3 پیتزا مخصوص کاکتوس
  • H3 پیتزا چیکن
  • H3 پیتزا سیر استیک
  • H3 پیتزا پپرونی
  • H3 پیتزا چهار فصل
  • H3 پیتزا یونانی
  • H3 پیتزا رست‌بیف
  • H3 فیله چهارتایی کاکتوس
  • H3 فیله شش‌ تایی کاکتوس
  • H3 سبد دورهمی کاکتوس
  • H3 پیاز سوخاری
  • H3 سیب‌زمینی
  • H3 کرانچ دوتایی
  • H3 کرانچ سه‌تایی
  • H3 سالاد سزار کاکتوس
  • H3 نان سیر
  • H3 سس سیر دست ساز کاکتوس
  • H3 سس کچاپ دست ساز کاکتوس
  • H3 سس تارتار دست ساز کاکتوس
  • H3 نوشیدنی قوطی
  • H3 لیموناد
  • H3 آب گازدار
  • H3 آب معدنی
  • H3 لیموناد خانواده
  • H3 نوشابه خانواده
  • H3 لیموناد شیشه ای
  • H3 آبمیوه
  • H3 دوغ آبعلی
  • H3 دوغ
  • H2 موردی پیدا نشد

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
43 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: 43 all-caps heading(s)
A+
Alt Text Quality
All 42 images OK
PASS
All 42 images OK
Info::
42 image(s) with good alt text
42 images 42 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchInputsearchجستجوی غذاaria-label
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 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 "fa"
PASS
Lang attribute set to "fa"
Info::
<html lang="fa"> is set and valid
Got: fa
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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+
Mobile-Readable Font Sizes
All 232 visible text node(s) render at >= 12 CSS pixels
PASS
All 232 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 24 passed
PASS
98

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.

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
جوسی برگر section#menuGrid > article.menu-card > div.menu-card__body > h3.menu-card__title

These are opportunities to improve keyboard navigation in your application.

○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
●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 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
●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 have a discernible name
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Skip links are focusable.
●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
○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
○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.
○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.
○`<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