Skip to content
https://bestreviews.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
7
REVIEW
8
PASS
9
INFO
0
Checks
24
9 PASS 8 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 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: email.
Got: <input type="email" name="email">, <input type="email" name="email">
Warning::
2 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.
Got: <input type="email" name="email">, <input type="email" name="email">
D
Tabindex Anti-Patterns
Action
0 positive, 20 -1-on-focusable
FIX
0 positive, 20 -1-on-focusable
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.)
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
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
38 headings
REVIEW
38 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Adidas and New Balance are up to 66% off at Nordstrom Rack
  • H2 IKEA just launched affordable fall decor for this economy
  • H2 Mattel unveils Whitney Houston Barbie in look from her most iconic video
  • H2 Epic Discounts: Elevate your home with these cleaning, kitchen and wellness must-haves
  • H2 Epic Discounts: Elevate your home with these cleaning, kitchen and wellness must-haves
  • H2 Self-cleaning litter boxes that are definitely worth the money
  • H2 OUR TOP PICKS Some of our must-have essentials for this season, hand picked by our experts just for you.
  • H2 Rare discounts on Apple products are happening this week
  • H2 LEGO unveils new sets with Gen X’ers and millennials in mind
  • H2 IKEA’s budget-friendly Halloween collection is available for delivery
  • H2 Summer skin care essentials to hydrate and protect your skin
  • H2 Drawstring jeans are everywhere this summer
  • H2 9 countertop appliances for when it’s too hot to use your conventional oven
  • H2 These camping accessories will make your campsite feel like home
  • H2 What to plant in August: best vegetables and flowers to grow
  • H2 Best hose reels
  • H2 Best Callaway irons
  • H2 Best pool pumps
  • H2 Solawave's viral LED face mask is, unfortunately, worth the price
  • H2 Best persimmon soap
  • H2 Pregnancy skin care recs from an also pregnant beauty editor
  • H2 Our Korean hair care picks for thick, moisturized locks
  • H2 Studies suggest PDRN skin care has anti-aging benefits
  • H2 Best Turntables
  • H2 Best printers
  • H2 Best laptops under $500
  • H2 Best Apple Watch
  • H2 Best drones
  • H2 Best travel mugs
  • H2 Shoppers are loving Dolly Parton’s new Walmart home line
  • H2 10 produce-saving products that'll help your grocery budget
  • H2 Best soda makers
  • H2 Should you wash chicken before you cook it?
  • H2 The best bathroom cleaning supplies for everyone’s least favorite chore
  • H2 Will a smart thermostat save me money?
  • H2 The best pillows for people who love to read in bed
  • H2 Best air purifiers
  • H2 Best air mattresses

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

B
Form Accessibility
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Warning::
5 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="text" name="q">; <input type="email" name="email">; <input type="email" name="email">; <textarea name="user_message">
5 controls
0 labeled
5 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtext(What are you looking for today?)placeholder only
qtext(What are you looking for today?)placeholder only
emailemail(Email address)placeholder only
emailemail(Email...)placeholder only
user_messagetextarea(Type your message here...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q">; <input type="text" name="q">; <input type="email" name="email">; <input type="email" name="email">; <textarea name="user_message">

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

B
Iframe Accessibility
3/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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="")
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="")
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.
C
Tap Target Adequacy
Action
4 tap target(s) too small or too close together
REVIEW
4 tap target(s) too small or too close together
Warning::
4 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 Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 25 passed
REVIEW
78

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.bestie-chat-window > header > div.bestie-chat-controls > button.bestie-chat-close div.bestie-chat-window > header > div.bestie-chat-controls > button.bestie-chat-close
div.bestie-chat-window > footer > form.bestie-chat-form > button.send-btn div.bestie-chat-window > footer > form.bestie-chat-form > button.send-btn

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.block--whoisbestreviews--our-mission > div.block--whoisbestreviews--our-mission--image > div.prgrsv > img.blr div.block--whoisbestreviews--our-mission > div.block--whoisbestreviews--our-mission--image > div.prgrsv > img.blr

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.blocksv4-bestreviews-landing-components-videothumbnail > div.br-youtube-frame-wrapper > div.br-youtube-frame-inner > iframe.thumbnail div.blocksv4-bestreviews-landing-components-videothumbnail > div.br-youtube-frame-wrapper > div.br-youtube-frame-inner > iframe.thumbnail

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
body.is-landing > div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > a body.is-landing > div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > a
div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a
div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a
div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a
div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a div.featured-articles-holder > article.editorial-article-featured > div.editorial-article-featured--image-holder > a
div.left-section > article > div.category-layout--layout1--article--image-holder > a div.left-section > article > div.category-layout--layout1--article--image-holder > a
div.blocksv4-bestreviews-landing-components-articleslist > article.article > div.article-image-wrapper > a div.blocksv4-bestreviews-landing-components-articleslist > article.article > div.article-image-wrapper > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.left-section > article > div.category-layout--layout3--article--image-holder > a div.left-section > article > div.category-layout--layout3--article--image-holder > a
div.left-section > article > div.category-layout--layout3--article--image-holder > a div.left-section > article > div.category-layout--layout3--article--image-holder > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.left-section > article > div.category-layout--layout1--article--image-holder > a div.left-section > article > div.category-layout--layout1--article--image-holder > a
div.blocksv4-bestreviews-landing-components-articleslist > article.article > div.article-image-wrapper > a div.blocksv4-bestreviews-landing-components-articleslist > article.article > div.article-image-wrapper > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.left-section > article > div.category-layout--layout3--article--image-holder > a div.left-section > article > div.category-layout--layout3--article--image-holder > a
div.left-section > article > div.category-layout--layout3--article--image-holder > a div.left-section > article > div.category-layout--layout3--article--image-holder > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.left-section > article > div.category-layout--layout3--article--image-holder > a div.left-section > article > div.category-layout--layout3--article--image-holder > a
div.left-section > article > div.category-layout--layout3--article--image-holder > a div.left-section > article > div.category-layout--layout3--article--image-holder > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a div.right-section > div.blocksv4-bestreviews-landing-components-articleslist > article.article > a
div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-fb div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-fb
div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-twitter div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-twitter
div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-insta div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-insta
div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-in div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-in
div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-youtube div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-youtube
div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-pinterest div.footer-content-inner > div.footer-content-row-2 > div.social-buttons > a.social-pinterest

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
Aug. 13, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
FASHION article.article > div.article-description > div.components-metadata > a.components-metadata--category
Aug. 11, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
HOME article.article > div.article-description > div.components-metadata > a.components-metadata--category
Aug. 10, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
TOYS & GAMES article.article > div.article-description > div.components-metadata > a.components-metadata--category
Aug. 13, 2026 div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > div.components-metadata > time.components-metadata--date
PETS div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > div.components-metadata > a.components-metadata--category
Best Cat Litter div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > div.related-articles > a.related-articles--article
The self-cleaning litter box that changed my cat-loving life div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > div.related-articles > a.related-articles--article
Catios are trending — here’s how to give your feline friend an outdoor oasis div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > div.related-articles > a.related-articles--article
$59.99 div.details > a > div.price > span.current-price
$149.00 div.details > a > div.price > span.current-price
$189.99 div.details > a > div.price > span.current-price
$149.99 div.details > a > div.price > span.current-price
ELECTRONICS div.featured-articles-holder > article.editorial-article-featured > div.components-metadata > a.components-metadata--category
TOYS & GAMES div.featured-articles-holder > article.editorial-article-featured > div.components-metadata > a.components-metadata--category
BEAUTY & PERSONAL CARE div.featured-articles-holder > article.editorial-article-featured > div.components-metadata > a.components-metadata--category
APPAREL div.featured-articles-holder > article.editorial-article-featured > div.components-metadata > a.components-metadata--category
Aug. 4, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Aug. 6, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 11, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 10, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 12, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Jul. 28, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Jul. 16, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Jul. 24, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Jul. 27, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Jul. 30, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Aug. 6, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 7, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 6, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 13, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Aug. 5, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Aug. 11, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 10, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 10, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 10, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Aug. 11, 2026 div.left-section > article > div.components-metadata > time.components-metadata--date
Aug. 5, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Aug. 13, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
Jul. 30, 2026 article.article > div.article-description > div.components-metadata > time.components-metadata--date
READ MORE div.block--whoisbestreviews--container > div.block--whoisbestreviews--our-mission > a.block--whoisbestreviews--about--us--button > button.block--whoisbestreviews--our-mission--button
Accept div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FASHION article.article > div.article-description > div.components-metadata > a.components-metadata--category
HOME article.article > div.article-description > div.components-metadata > a.components-metadata--category
TOYS & GAMES article.article > div.article-description > div.components-metadata > a.components-metadata--category
PETS div.blocksv4-bestreviews-landing-landingtopsection > article.blocksv4-bestreviews-landing-components-featuredarticle > div.components-metadata > a.components-metadata--category

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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●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
○`button`, `link`, and `menuitem` elements 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
○`<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.
○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 Quality
All 38 heading(s) have substantive, well-formed text
PASS
All 38 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
1 of 80 images have issues
PASS
1 of 80 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
42 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
80 images 37 good alt text 42 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
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
Mobile-Readable Font Sizes
All 170 visible text node(s) render at >= 12 CSS pixels
PASS
All 170 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::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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
h2 Epic Discounts: Elev…18.93:13.0:1
#000000
#F3F3F3
Pass
h2 OUR TOP PICKS18.93:13.0:1
#000000
#F3F3F3
Pass
title BestReviews - Never …21.00:14.5:1
#000000
#FFFFFF
Pass
a Menu12.77:14.5:1
#000000
#CAC9CF
Pass
button Ask Bestie18.14:14.5:1
#000000
#FEEEB9
Pass
a Electronics18.33:14.5:1
#000000
#FEEFC1
Pass
a Computer18.82:14.5:1
#000000
#FEF2CF
Pass
a Beauty & Personal Ca…18.99:14.5:1
#000000
#FEF3D4
Pass
a Bed & Bath19.01:14.5:1
#000000
#FEF3D6
Pass
a Automotive19.36:14.5:1
#000000
#FEF5E1
Pass
a All Categories20.36:14.5:1
#000000
#FFFBF4
Pass
a Trending21.00:14.5:1
#000000
#FFFFFF
Pass
a Deals21.00:14.5:1
#000000
#FFFFFF
Pass
a Gifts21.00:14.5:1
#000000
#FFFFFF
Pass
a About Us21.00:14.5:1
#000000
#FFFFFF
Pass
a Trending21.00:14.5:1
#000000
#FFFFFF
Pass
a Deals20.65:14.5:1
#000000
#FDFDFD
Pass
a Gifts21.00:14.5:1
#000000
#FFFFFF
Pass
button Ask Bestie21.00:14.5:1
#000000
#FFFFFF
Pass
div The Latest21.00:14.5: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.

Send Feedback