https://www.91servings.in
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
66
GRADE
D
FIX
10
REVIEW
4
PASS
10
INFO
0
Checks
2410 PASS 4 REVIEW 10 FIX
DHeading HierarchyAction35 headingsFIX
Heading Hierarchy
Action35 headings
35 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
- H4 Shop By Category
- H3 (empty)
- H3 (empty)
- H3 TOP SELLING
- H3 COMBO OF THE WEEK
- H3 NEW ARRIVALS
- H3 TRENDING IN MULTIVITAMINS
- H3 TRENDING IN PRE WORKOUTS
- H3 EXCLUSIVE OFFERS
- H3 Testimonials
- H3 What people say?
- H3 Blogs
- H3 The History Of Calorie Counting
- H3 Fast Delivery
- H3 Safe Payment
- H3 24/7 Help Center
- H3 Shop With Confidence
- H3 Friendly Services
- H3 (empty)
- H2 Authentic Online Sports Nutrition Store in India for Whey Protein, Fitness, Nutrition & Bodybuilding
- H2 Why 91servings?
- H2 Products we offer
- H2 100% Authenticity Guarantee
- H3 Sign Up To Newsletter
- H3 91SERVINGS
- H3 Help & support
- H3 Contact Us
- H3 Follow Us
- H3 Copyright © 91servings. all rights reserved.
- H3 (empty)
- H3 (empty)
- H3 WHAT ARE YOU LOOKING FOR?
- H3 Wishlist
- H2 Wishlist
- H3 Compare
Every page should have one H1 that describes the page content.
Why this matters
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
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
FAlt Text QualityAction4 of 109 images have issuesFIX
Alt Text Quality
Action4 of 109 images have issues
4 of 109 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 image(s) with alt text over 125 characters
Info::
13 decorative image(s) correctly marked
Info::
88 image(s) with good alt text
109 images 88 good alt text 13 decorative 4 missing
| Issue | Count |
|---|---|
| missing | 4 image(s) |
| too long | 4 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
An image inside a link with no alt creates an empty link.
Why this matters
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
Learn more ▾ ▴
An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.
Source: WCAG 2.1 SC 2.4.4
DForm AccessibilityAction5 of 7 controls have issuesFIX
Form Accessibility
Action5 of 7 controls have issues
5 of 7 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 name="product_type">; <select name="product_type">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="email" name="contact[email]">; <input type="text" name="q">
Info::
2 control(s) properly labeled
7 controls
2 labeled
3 placeholder only
2 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| currencies | select | Pick a currency | none |
| currencies | select | Pick a currency | none |
| contact[email] | (Your email address...) | placeholder only | |
| q | text | (Search for products ...) | placeholder only |
| q | text | (Search for products ...) | placeholder only |
| product_type | select | (none) | none |
| product_type | select | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<select name="product_type">; <select name="product_type">
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" name="q">; <input type="email" name="contact[email]">; <input type="text" name="q">
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
DLink & Button QualityAction68 issue(s) across 262 links and 15 buttonsFIX
Link & Button Quality
Action68 issue(s) across 262 links and 15 buttons
68 issue(s) across 262 links and 15 buttons
Critical::
66 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: javascript:void(0); a (#613 on page); a (#620 on page); /collections/gainers; /collections/gainers; /collections/creatine; /collections/creatine; /collections/pre-workouts; /collections/pre-workouts; /collections/liver-support (+56 more)
Warning::
1 link(s) with generic text
Generic link text like 'click here' doesn't describe the destination.
Got: /blogs/news/the-history-of-calorie-counting ("Read more")
Warning::
4 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: ; https://www.facebook.com/profile.php?id=100090671071650; https://www.instagram.com/91servings?igsh=bHhhcXFkcnRsYmY4;
Critical::
1 button(s) with no accessible text
Icon-only buttons need an aria-label so screen readers can announce them.
Got: button.col-lg-auto (#1782 on page)
Info::
191 link(s) with descriptive text
262 links
66 empty
1 generic text
4 new tab
1 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| javascript:void(0) | (empty) | empty | Add link text or aria-label |
| / | <img src="//www.91servings.in/… | img no alt | Add alt attribute to the image |
| Best Sellers | img no alt | Add alt attribute to the image | |
| Offer Zone | img no alt | Add alt attribute to the image | |
| /blogs/news | Blogs | img no alt | Add alt attribute to the image |
| /pages/about-us | About Us | img no alt | Add alt attribute to the image |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| /collections/gainers | (empty) | empty | Add link text or aria-label |
| /collections/gainers | (empty) | empty | Add link text or aria-label |
| /collections/creatine | (empty) | empty | Add link text or aria-label |
| /collections/creatine | (empty) | empty | Add link text or aria-label |
| /collections/pre-workouts | (empty) | empty | Add link text or aria-label |
| /collections/pre-workouts | (empty) | empty | Add link text or aria-label |
| /collections/liver-support | (empty) | empty | Add link text or aria-label |
| /collections/liver-support | (empty) | empty | Add link text or aria-label |
| /collections/aminos-bcaa | (empty) | empty | Add link text or aria-label |
| /collections/aminos-bcaa | (empty) | empty | Add link text or aria-label |
| /collections/multivitamins | (empty) | empty | Add link text or aria-label |
| /collections/multivitamins | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein | (empty) | empty | Add link text or aria-label |
| /collections/fat-burners | (empty) | empty | Add link text or aria-label |
| /collections/fat-burners | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein-isolate | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein-isolate | (empty) | empty | Add link text or aria-label |
| /admin/collections | (empty) | empty | Add link text or aria-label |
| /admin/collections | (empty) | empty | Add link text or aria-label |
| /collections/gainers | (empty) | empty | Add link text or aria-label |
| /collections/gainers | (empty) | empty | Add link text or aria-label |
| /collections/creatine | (empty) | empty | Add link text or aria-label |
| /collections/creatine | (empty) | empty | Add link text or aria-label |
| /collections/pre-workouts | (empty) | empty | Add link text or aria-label |
| /collections/pre-workouts | (empty) | empty | Add link text or aria-label |
| /collections/liver-support | (empty) | empty | Add link text or aria-label |
| /collections/liver-support | (empty) | empty | Add link text or aria-label |
| /collections/aminos-bcaa | (empty) | empty | Add link text or aria-label |
| /collections/aminos-bcaa | (empty) | empty | Add link text or aria-label |
| /collections/multivitamins | (empty) | empty | Add link text or aria-label |
| /collections/multivitamins | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein | (empty) | empty | Add link text or aria-label |
| /collections/fat-burners | (empty) | empty | Add link text or aria-label |
| /collections/fat-burners | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein-isolate | (empty) | empty | Add link text or aria-label |
| /collections/whey-protein-isolate | (empty) | empty | Add link text or aria-label |
| /admin/collections | (empty) | empty | Add link text or aria-label |
| /admin/collections | (empty) | empty | Add link text or aria-label |
| /collections/gainers | (empty) | empty | Add link text or aria-label |
| /collections/gainers | (empty) | empty | Add link text or aria-label |
| /collections/creatine | (empty) | empty | Add link text or aria-label |
| /collections/creatine | (empty) | empty | Add link text or aria-label |
| /collections/pre-workouts | (empty) | empty | Add link text or aria-label |
| /collections/pre-workouts | (empty) | empty | Add link text or aria-label |
| /collections/liver-support | (empty) | empty | Add link text or aria-label |
| /collections/liver-support | (empty) | empty | Add link text or aria-label |
| /collections/aminos-bcaa | (empty) | empty | Add link text or aria-label |
| /collections/aminos-bcaa | (empty) | empty | Add link text or aria-label |
| /collections/multivitamins | (empty) | empty | Add link text or aria-label |
| /collections/multivitamins | (empty) | empty | Add link text or aria-label |
| /blogs/news/the-history-of-calorie-count… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: The History Of Calorie Counting | |||
| new tab | Add '(opens in new tab)' to text | ||
| https://www.facebook.com/profile.php?id=… | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/91servings?igs… | Instargram | new tab | Add '(opens in new tab)' to text |
| Youtube | new tab | Add '(opens in new tab)' to text | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| # | (empty) | empty | Add link text or aria-label |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| / | <img src="//www.91servings.in/… | img no alt | Add alt attribute to the image |
| / | <img src="//www.91servings.in/… | img no alt | Add alt attribute to the image |
| https://api.whatsapp.com/send?phone=9196… | (empty) | empty | Add link text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
205 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
javascript:void(0); a (#613 on page); a (#620 on page); /collections/gainers; /collections/gainers; /collections/creatine; /collections/creatine; /collections/pre-workouts; /collections/pre-workouts; /collections/liver-support (+56 more)
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
/blogs/news/the-history-of-calorie-counting ("Read more")
Why this matters
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
; https://www.facebook.com/profile.php?id=100090671071650; https://www.instagram.com/91servings?igsh=bHhhcXFkcnRsYmY4;
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
Icon-only buttons need an aria-label so screen readers can announce them.
button.col-lg-auto (#1782 on page)
Why this matters
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
DTabindex Anti-PatternsAction0 positive, 63 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 63 -1-on-focusable
0 positive, 63 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="slick-slide-control01">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="slick-slide-control02">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="slick-slide-control21">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
FFavicon & BrandingAction2 icon(s) detectedFIX
Favicon & Branding
Action2 icon(s) detected
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
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.
DDark Mode SupportActionTheme color onlyFIX
Dark Mode Support
ActionTheme color only
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: #aaaaaa
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.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
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 ✗
BLandmark Structure10 landmarksREVIEW
Landmark Structure
10 landmarks
10 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
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
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
BIframe Accessibility2/2 iframe(s) missing title; 0 placeholder(s)REVIEW
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.91servings.in/web-pixels@db2e2262w5773267dpae7c6deam788d1861/custom…")
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.
Warning::
<iframe> missing title attribute (src="https://sr-cdn.shiprocket.in/sr-promise/static/iframe.html")
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.
BMobile-Readable Font Sizes98% of visible text renders at >= 12 CSS px (1 below threshold)REVIEW
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (1 below threshold)
98% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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: <button> 0.0px ("Search").
BLighthouse Accessibility AuditsScore 82/100 — 5 failing, 26 passedREVIEW
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 26 passed
82
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.mini_cart_wrap > form.search_header > div.frm_search_input > button.col-lg-auto div.mini_cart_wrap > form.search_header > div.frm_search_input > button.col-lg-auto |
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.container > div.row > div.header-nav-mobile > a.js-mobile-menu div.container > div.row > div.header-nav-mobile > a.js-mobile-menu |
div.container > div.row > div.header-logo > a.site-header__logo-image div.container > div.row > div.header-logo > a.site-header__logo-image |
div#bk_1640932747e1460cee-0 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link div#bk_1640932747e1460cee-0 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link |
article.post-item > div#bk_1640932747e1460cee-0 > div.cat_grid_item__content > a.cat_grid_item__link article.post-item > div#bk_1640932747e1460cee-0 > div.cat_grid_item__content > a.cat_grid_item__link |
div#bk_1640932747e1460cee-1 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link div#bk_1640932747e1460cee-1 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link |
article.post-item > div#bk_1640932747e1460cee-1 > div.cat_grid_item__content > a.cat_grid_item__link article.post-item > div#bk_1640932747e1460cee-1 > div.cat_grid_item__content > a.cat_grid_item__link |
div#bk_1640932747e1460cee-2 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link div#bk_1640932747e1460cee-2 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link |
article.post-item > div#bk_1640932747e1460cee-2 > div.cat_grid_item__content > a.cat_grid_item__link article.post-item > div#bk_1640932747e1460cee-2 > div.cat_grid_item__content > a.cat_grid_item__link |
div#bk_1640932747e1460cee-3 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link div#bk_1640932747e1460cee-3 > div.cat_grid_item__content > div.cat_grid_item__wrapper > a.collections_link |
article.post-item > div#bk_1640932747e1460cee-3 > div.cat_grid_item__content > a.cat_grid_item__link article.post-item > div#bk_1640932747e1460cee-3 > div.cat_grid_item__content > a.cat_grid_item__link |
div.product-item > div.product-collection > div.product-collection__image > a.d-block div.product-item > div.product-collection > div.product-collection__image > a.d-block |
div.product-image__overlay-bottom > div.group-button > div.inner > a.js_quick_view div.product-image__overlay-bottom > div.group-button > div.inner > a.js_quick_view |
div.product-image__overlay-bottom > div.group-button > div.inner > a.wishlist-button div.product-image__overlay-bottom > div.group-button > div.inner > a.wishlist-button |
div.product-item > div.product-collection > div.product-collection__image > a.d-block div.product-item > div.product-collection > div.product-collection__image > a.d-block |
div.product-image__overlay-bottom > div.group-button > div.inner > a.js_quick_view div.product-image__overlay-bottom > div.group-button > div.inner > a.js_quick_view |
div.product-image__overlay-bottom > div.group-button > div.inner > a.wishlist-button div.product-image__overlay-bottom > div.group-button > div.inner > a.wishlist-button |
div.apus-footer-mobile > ul > li > a div.apus-footer-mobile > ul > li > a |
div.apus-footer-mobile > ul > li > a div.apus-footer-mobile > ul > li > a |
div.apus-footer-mobile > ul > li > a div.apus-footer-mobile > ul > li > a |
div.main > div.footer > div#shopify-section-footer4 > a.back-to-top div.main > div.footer > div#shopify-section-footer4 > a.back-to-top |
div.container > div.laber_mini_cart > div.logo-mobile > a.site-header__logo-image div.container > div.laber_mini_cart > div.logo-mobile > a.site-header__logo-image |
div.js-menu-mobile-content > div#mobile_menu > div.logo-mobile > a.site-header__logo-image div.js-menu-mobile-content > div#mobile_menu > div.logo-mobile > a.site-header__logo-image |
body#91-servings-authentic-protein-amp-supplements-india > div#shopify-block-AU0krZXZzNkZxNXNZZ__5394799768760407377 > div.align-right > a body#91-servings-authentic-protein-amp-supplements-india > div#shopify-block-AU0krZXZzNkZxNXNZZ__5394799768760407377 > div.align-right > a |
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 |
|---|
Rs. 2,799.00 div.frm-price-color > div.product-collection__price > span.price > span.compare |
ADD TO CART div.product-collection__content > div.product-collection-cart > a.add-to-cart > span.text |
Rs. 8,499.00 div.frm-price-color > div.product-collection__price > span.price > span.compare |
ADD TO CART div.product-collection__content > div.product-collection-cart > a.add-to-cart > span.text |
MR. WORLD CHAMPION div#slick-slide21 > div.cms_content_quote > div.quote_info > div.quote_address |
DISCOVER NOW div.row > div.testimonial-blog > div.wrap_title_testi > a#b_ |
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
91servings. div.row > div.coppy-right > h3.content > a |
These are opportunities to improve the legibility of your content.
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 |
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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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
○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.
○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 Quality1 heading-text-quality issue(s) detectedPASS
Heading Text Quality
1 heading-text-quality issue(s) detected
1 heading-text-quality issue(s) detected
Info::
8 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: 8 all-caps heading(s)
AForm Input Types2 input(s) using type=text where a specific type would helpPASS
Form Input Types
2 input(s) using type=text where a specific type would help
2 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+Form Input Quality7 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
7 form control(s) checked, no input-semantic issues
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "en"PASS
Document Language
Lang attribute set to "en"
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A404 Error PageHTTP 404, custom pagePASS
404 Error Page
HTTP 404, custom page
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth2 mobile-depth signal(s) detectedPASS
Mobile UX Depth
2 mobile-depth signal(s) detected
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::
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.
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
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)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Authentic Online Spo… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Why 91servings? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Products we offer | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 100% Authenticity Gu… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Wishlist | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 TOP SELLING | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 COMBO OF THE WEEK | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 NEW ARRIVALS | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 TRENDING IN MULTIVIT… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 TRENDING IN PRE WORK… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 EXCLUSIVE OFFERS | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Testimonials | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 What people say? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Blogs | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Fast Delivery | 15.91:1 | 3.0:1 | #222222 | #FFFFFF | Pass |
| h3 Safe Payment | 15.91:1 | 3.0:1 | #222222 | #FFFFFF | Pass |
| h3 24/7 Help Center | 15.91:1 | 3.0:1 | #222222 | #FFFFFF | Pass |
| h3 Shop With Confidence | 15.91:1 | 3.0:1 | #222222 | #FFFFFF | Pass |
| h3 Friendly Services | 15.91:1 | 3.0:1 | #222222 | #FFFFFF | Pass |
| h3 Copyright © | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.