Skip to content
https://shopaccino.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
84
GRADE
B
FIX
4
REVIEW
4
PASS
16
INFO
0
Checks
24
16 PASS 4 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name App Icons 6 icon(s)
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: #ffffff
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::
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 1 <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
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 Shopaccino: Create ecommerce store with 30 days free trail ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
21 icon(s) detected
REVIEW
21 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
PWA Depth
3 PWA signal(s) surfaced
REVIEW
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
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).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A
Landmark Structure
4 landmarks
PASS
4 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
39 headings
PASS
39 headings
Info::
Single H1 present
  • H1 Build, Manage & Scale Your eCommerce Business with an Enterprise-Grade Commerce Platform
  • H2 Trusted by growing brands across industries
  • H2 Everything You Need to Run & Scale Modern Commerce
  • H3 Enterprise Commerce Engine
  • H3 Scale Without Boundaries
  • H3 Automation That Drives Efficiency
  • H2 Built for Your Industry, Not Just Generic Commerce
  • H3 Fashion & Apparel
  • H3 Grocery
  • H3 Furniture & Home Décor
  • H3 Jewellery
  • H3 B2B Wholesale
  • H3 Handicrafts Online
  • H3 Shoe Store
  • H3 Food Delivery
  • H3 Sell Bags Online
  • H3 Sell Electronics Online
  • H3 Books & Stationery
  • H3 Sell Cosmetics Online
  • H3 Health & Wellness
  • H3 Handicrafts Online
  • H2 A Complete Commerce Ecosystem, Not Just a Platform
  • H3 Launch your own iOS & Android app
  • H3 Optimize last-mile delivery
  • H3 Drive repeat purchases
  • H3 Wholesale & retail, one platform
  • H2 Why Businesses Choose Shopaccino
  • H3 Transaction Fee
  • H3 Built for Growth
  • H3 All-in-One Commerce Platform
  • H3 Enterprise Capabilities Without Complexity
  • H3 Faster Time to Market
  • H3 Scalable Support System
  • H2 Take Your Business Global.
  • H2 Support That Helps You Grow
  • H3 Onboarding assistance
  • H3 Dedicated account support
  • H3 Continuous improvements
  • H2 Start Scaling YoureCommerce Business Today.
A+
Heading Text Quality
All 39 heading(s) have substantive, well-formed text
PASS
All 39 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 71 images OK
PASS
All 71 images OK
Info::
9 decorative image(s) correctly marked
Info::
62 image(s) with good alt text
71 images 62 good alt text 9 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
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
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 105 visible text node(s) render at >= 12 CSS pixels
PASS
All 105 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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+
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)
ElementRatioRequiredFGBGResult
h1 Build, Manage & Scal…19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Trusted by growing b…19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Everything You Need …19.35:13.0:1
#000000
#F9F5F0
Pass
h2 & Scale19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Built for Your Indus…19.35:13.0:1
#000000
#F9F5F0
Pass
h2 A Complete Commerce19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Ecosystem,19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Why Businesses Choos…19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Take Your Business19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Support That Helps Y…19.35:13.0:1
#000000
#F9F5F0
Pass
h2 Start Scaling Your19.35:13.0:1
#000000
#F9F5F0
Pass
h2 eCommerce Business T…19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Enterprise Commerce …19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Scale Without Bounda…19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Automation That Driv…19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Fashion & Apparel19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Grocery19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Furniture & Home Dé…19.35:13.0:1
#000000
#F9F5F0
Pass
h3 Jewellery19.35:13.0:1
#000000
#F9F5F0
Pass
h3 B2B Wholesale19.35:13.0:1
#000000
#F9F5F0
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 100/100 — 0 failing, 23 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 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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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.
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback