Skip to content
https://dearammi.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
D
Form Accessibility
Action
5 of 16 controls have issues
FIX
5 of 16 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <input type="search" name="q">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="contact[email]">; <input type="text" id="CartDiscountcode">; <input type="text">
Info::
11 control(s) properly labeled
16 controls
11 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#CartSpecialInstructionstextareaAdd Order NoteEdit Order Notefor/id
#ShippingCountry_mini_cartselectCountryfor/id
#ShippingProvince_mini_cartselectProvincefor/id
#ShippingZip_mini_carttextZip codefor/id
#RecoverEmailemailEmail addressfor/id
#CustomerEmailemailEmail *for/id
#CustomerPasswordpasswordPassword *for/id
#RegisterForm-FirstNametextFirst Namefor/id
#RegisterForm-LastNametextLast Namefor/id
#RegisterForm-emailemailEmail *for/id
#RegisterForm-passwordpasswordPassword *for/id
#CartDiscountcodetext(Coupon code)placeholder only
contact[email]email(Your email address)placeholder only
inputtext(Search)placeholder only
selectselect(none)none
qsearch(none)none

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

<select>; <input type="search" name="q">

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="email" name="contact[email]">; <input type="text" id="CartDiscountcode">; <input type="text">

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
7/8 eligible field(s) missing autocomplete or inputmode
FIX
7/8 eligible field(s) missing autocomplete or inputmode
Warning::
2 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: country-name, postal-code.
Got: <select name="country" id="ShippingCountry_mini_cart">, <input type="text" name="zip" id="ShippingZip_mini_cart">
Warning::
5 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: email, search.
Got: <input type="email" name="contact[email]">, <input type="email" name="email" id="RecoverEmail">, <input type="email" name="customer[email]" id="CustomerEmail">, <input type="email" name="customer[email]" id="RegisterForm-email">, <input type="search" name="q">
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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: #fff
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Form Input Quality
2 input-semantic issue(s) across 16 form control(s)
REVIEW
2 input-semantic issue(s) across 16 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">.
Info::
1 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="contact[email]">.
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 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.
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 – Dear Ammi ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title Dear Ammi
1.71:1
#000000
on
#413225
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Dear Ammi5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Customers are saying5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Freshly Packed5.24:13.0:1
#000000
#7F7F7F
Pass
h3 100% Natural5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Fast Delivery5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Healthy Ingredients5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Why Choose Dear Ammi5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Benefits5.24:13.0:1
#000000
#7F7F7F
Pass
h3 FREE SHIPPING5.24:13.0:1
#000000
#7F7F7F
Pass
h3 SUPPORT 24/75.24:13.0:1
#000000
#7F7F7F
Pass
h3 7 DAYS FREE RETURN5.24:13.0:1
#000000
#7F7F7F
Pass
h3 100% PAYMENT SECURE5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Get in Touch5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Information5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Information5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Useful links5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Useful links5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Newsletter Signup5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Newsletter Signup5.24:13.0:1
#000000
#7F7F7F
Pass
title Dear Ammi1.71:14.5:1
#000000
#413225
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 75/100 — 6 failing, 21 passed
REVIEW
75

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div.t4s-slideshow > div.flickityt4s-viewport > div.flickityt4s-slider > div#b_image_parent_LnwnkG div.t4s-slideshow > div.flickityt4s-viewport > div.flickityt4s-slider > div#b_image_parent_LnwnkG
div.t4s-slideshow > div.flickityt4s-viewport > div.flickityt4s-slider > div#b_164602873867eb3815-0 div.t4s-slideshow > div.flickityt4s-viewport > div.flickityt4s-slider > div#b_164602873867eb3815-0
Sale All 3 Bundles Rs.9,349.00Rs.7,500.00 div.t4s-flicky-slider > div.flickityt4s-viewport > div.flickityt4s-slider > div.t4s-product
Sale Brain Boost & PowerHouse Superfood Rs.5,899.00Rs.5,450.00 div.t4s-flicky-slider > div.flickityt4s-viewport > div.flickityt4s-slider > div.t4s-product
Organic Superfoods That Actually Work: Nuts, Seeds & Adaptogenic Herbs Backed b… div.t4s-flicky-slider > div.flickityt4s-viewport > div.flickityt4s-slider > article.t4s-col-item
Three Super Herbs: Thousands of Benefits on January 19, 2026 Ashwagandha, Ginkg… div.t4s-flicky-slider > div.flickityt4s-viewport > div.flickityt4s-slider > article.t4s-col-item

These are opportunities to improve the usage of ARIA in your application which 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
TOP SELLING PRODUCTS div.t4s-top-heading > div.heading-testimonials-star > h3.t4s-section-title > span
Sale div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-badge > span.t4s-badge-item
EyeMax Superfood div.t4s-product-info > div.t4s-product-info__inner > h3.t4s-product-title > a.is--href-replaced
Rs.2,800.00 div.t4s-product-info > div.t4s-product-info__inner > div.t4s-product-price > ins
Sale div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-badge > span.t4s-badge-item
Power House Superfood div.t4s-product-info > div.t4s-product-info__inner > h3.t4s-product-title > a.is--href-replaced
Rs.2,800.00 div.t4s-product-info > div.t4s-product-info__inner > div.t4s-product-price > ins
Sale div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-badge > span.t4s-badge-item
Brain Boost Superfood div.t4s-product-info > div.t4s-product-info__inner > h3.t4s-product-title > a.is--href-replaced
Rs.2,600.00 div.t4s-product-info > div.t4s-product-info__inner > div.t4s-product-price > ins
Sale div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-badge > span.t4s-badge-item
All 3 Bundles div.t4s-product-info > div.t4s-product-info__inner > h3.t4s-product-title > a.is--href-replaced
Rs.7,500.00 div.t4s-product-info > div.t4s-product-info__inner > div.t4s-product-price > ins
Why Choose Dear Ammi div.t4s-image-text > div.t4s-col-text > div.t4s-image-text-content > h3.t4s-image-text-heading
100% Pure & Premium: We use only organic nuts, seeds, and powerful herbs (Ginkg… div.t4s-col-text > div.t4s-image-text-content > div.t4s-image-text-des > p
100% Pure & Premium: div.t4s-image-text-content > div.t4s-image-text-des > p > strong
Targeted & Proven Benefits: Each blend is specifically formulated to deliver ac… div.t4s-col-text > div.t4s-image-text-content > div.t4s-image-text-des > p
Targeted & Proven Benefits: div.t4s-image-text-content > div.t4s-image-text-des > p > strong
Nutrient-Rich Formulations: Our products are nutritional powerhouses, packed wi… div.t4s-col-text > div.t4s-image-text-content > div.t4s-image-text-des > p
Nutrient-Rich Formulations: div.t4s-image-text-content > div.t4s-image-text-des > p > strong
Adaptogenic Stress Support: We incorporate powerful adaptogens like Ashwagandha… div.t4s-col-text > div.t4s-image-text-content > div.t4s-image-text-des > p
Adaptogenic Stress Support: div.t4s-image-text-content > div.t4s-image-text-des > p > strong
Near-Zero Sugar Formula: We avoid refined sugars to prevent sugar spikes and br… div.t4s-col-text > div.t4s-image-text-content > div.t4s-image-text-des > p
Near-Zero Sugar Formula: div.t4s-image-text-content > div.t4s-image-text-des > p > strong
Trusted, Small-Batch Craftsmanship: Customers rely on Dear Ammi because our sma… div.t4s-col-text > div.t4s-image-text-content > div.t4s-image-text-des > p
Trusted, Small-Batch Craftsmanship: div.t4s-image-text-content > div.t4s-image-text-des > p > strong
About Us div.t4s-image-text > div.t4s-col-text > div.t4s-image-text-content > a.t4s-btn
Best Selling div.t4s-top-heading > div.heading-testimonials-star > h3.t4s-section-title > span
EYEMAX Superfood: Your Natural Vision Support Blend div.t4s-top-heading > div.heading-testimonials-star > h3.t4s-section-title > span
Benefits div.t4s-image-text > div.t4s-col-text > div.t4s-image-text-content > h3.t4s-image-text-heading
All 3 Bundles div.jdgm-card > div.jdgm-rating-section > div.jdgm-product-name > a
Frequently Asked Questions div.t4s-top-heading > div.heading-testimonials-star > h3.t4s-section-title > span
Blog post div.t4s-top-heading > div.heading-testimonials-star > h3.t4s-section-title > span
FREE SHIPPING div.t4s-shipping > div.t4s-shipping-inner > div.t4s-col > h3.t4s-shipping-title
SUPPORT 24/7 div.t4s-shipping > div.t4s-shipping-inner > div.t4s-col > h3.t4s-shipping-title
7 DAYS FREE RETURN div.t4s-shipping > div.t4s-shipping-inner > div.t4s-col > h3.t4s-shipping-title
100% PAYMENT SECURE div.t4s-shipping > div.t4s-shipping-inner > div.t4s-col > h3.t4s-shipping-title
Get in Touch div.t4s-custom-col > div.t4s-col-inner > div.t4s-footer-heading > h3.t4s-col-heading
Information div.t4s-custom-col > div.t4s-col-inner > div.t4s-footer-heading > h3.t4s-col-heading
Useful links div.t4s-custom-col > div.t4s-col-inner > div.t4s-footer-heading > h3.t4s-col-heading
Newsletter Signup div.t4s-custom-col > div.t4s-col-inner > div.t4s-footer-heading > h3.t4s-col-heading

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.t4s-hero-inner > div.t4s_ratio > video > img div.t4s-hero-inner > div.t4s_ratio > video > img

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
div.t4s-container > div.t4s-row > div.t4s-col-md-4 > a.t4s-push-menu-btn div.t4s-container > div.t4s-row > div.t4s-col-md-4 > a.t4s-push-menu-btn
div.t4s-col-lg-auto > div.t4s-site-nav__icons > div.t4s-site-nav__icon > a.t4s-pr div.t4s-col-lg-auto > div.t4s-site-nav__icons > div.t4s-site-nav__icon > a.t4s-pr
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns > a.t4s-pr-item-btn
div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn div.t4s-product-wrapper > div.t4s-product-inner > div.t4s-product-btns2 > a.t4s-pr-item-btn
div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link div.t4s-product > div.t4s-product-wrapper > div.t4s-product-inner > a.t4s-full-width-link
div#block-5 > div.block-content > div.block > a.social-network-block-wrapper div#block-5 > div.block-content > div.block > a.social-network-block-wrapper
div#block-5 > div.block-content > div.block > a.social-network-block-wrapper div#block-5 > div.block-content > div.block > a.social-network-block-wrapper
div#block-5 > div.block-content > div.block > a.social-network-block-wrapper div#block-5 > div.block-content > div.block > a.social-network-block-wrapper

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Dear Ammi div.t4s-product-info > div.t4s-product-info__inner > div.t4s-product-vendor > a
All 3 Bundles div.t4s-product-info > div.t4s-product-info__inner > h3.t4s-product-title > a.is--href-replaced

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
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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.
○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
○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.
○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+
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A
Heading Hierarchy
35 headings, 1 skip(s)
PASS
35 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 Dear Ammi
  • H3 Freshly Packed skipped
  • H3 100% Natural
  • H3 Fast Delivery
  • H3 Healthy Ingredients
  • H3 TOP SELLING PRODUCTS
  • H3 EyeMax Superfood
  • H3 Power House Superfood
  • H3 Brain Boost Superfood
  • H3 All 3 Bundles
  • H3 Why Choose Dear Ammi
  • H3 Best Selling
  • H3 EyeMax & PowerHouse Superfood
  • H3 Brain Boost & EyeMax Superfood
  • H3 All 3 Bundles
  • H3 Brain Boost & PowerHouse Superfood
  • H3 EYEMAX Superfood: Your Natural Vision Support Blend
  • H3 Benefits
  • H2 Customers are saying
  • H3 Frequently Asked Questions
  • H3 Blog post
  • H3 Organic Superfoods That Actually Work: Nuts, Seeds & Adaptogenic Herbs Backed by Science
  • H3 Three Super Herbs: Thousands of Benefits
  • H3 10 Healthy Superfoods for a Balanced Life & Strong Health
  • H3 FREE SHIPPING
  • H3 SUPPORT 24/7
  • H3 7 DAYS FREE RETURN
  • H3 100% PAYMENT SECURE
  • H3 Get in Touch
  • H3 Information
  • H3 Information
  • H3 Useful links
  • H3 Useful links
  • H3 Newsletter Signup
  • H3 Newsletter Signup

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::
5 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: 5 all-caps heading(s)
A
Alt Text Quality
1 of 59 images have issues
PASS
1 of 59 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 decorative image(s) correctly marked
Info::
51 image(s) with good alt text
59 images 51 good alt text 7 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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 "Search" should use type="search" (currently type="text")
Field name "Search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
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
11 explicit tabindex attribute(s) checked, no anti-patterns
PASS
11 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://dearammi.com/web-pixels@9f5e2762wb720532ap19708c42m93b2bec3/custom/web-…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Mobile-Readable Font Sizes
All 217 visible text node(s) render at >= 12 CSS pixels
PASS
All 217 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback