Skip to content
https://bolbala.in

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
4
REVIEW
7
PASS
13
INFO
0
Checks
24
13 PASS 7 REVIEW 4 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
9 landmarks
REVIEW
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #main
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

C
Heading Hierarchy
Action
40 headings, 2 skip(s)
REVIEW
40 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Bol Bala
  • H1 Bol Bala duplicate H1
  • H2 Search
  • H5 Latest skipped
  • H5 Popular
  • H5 Update
  • H6 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H6 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H6 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H6 Chhabra 555 | Chandni Chowk
  • H6 KAKE DI HATTI | Chandni Chowk
  • H6 Pratishta Siksha Vikas Kendra Trust | NGO
  • H6 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H6 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H6 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H4 Main
  • H3 Men’s Wedding Dress in Karol Bagh – Complete Guide to Choosing the Perfect Outfit
  • H3 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H3 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H3 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H3 Lajpat Nagar Street Food Guide: Top Street Food You Can’t Miss
  • H3 Men’s Wedding Dress in Karol Bagh – Complete Guide to Choosing the Perfect Outfit
  • H3 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H4 Trending
  • H6 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar skipped
  • H6 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H6 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H6 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H6 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H6 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H6 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H6 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H6 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H4 Featured Categories
  • H2 Featured Post
  • H2 Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar
  • H2 Vintage Cottage Cafe Noida Review: Aesthetic Vibes, Menu, Prices & Free Dessert Offer
  • H2 Uttarakhand Traditional Dress: A Visit to Uttranchali Ethnic Collection
  • H2 Lajpat Nagar Street Food Guide: Top Street Food You Can’t Miss
  • H2 GALLERY

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Mobile-Readable Font Sizes
Action
89% of visible text renders at >= 12 CSS px (10 below threshold)
REVIEW
89% of visible text renders at >= 12 CSS px (10 below threshold)
Warning::
10 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: <span> 11.9px ("October 11, 2026"); <span> 11.9px ("April 24, 2026"); <span> 11.9px ("April 23, 2026"); <span> 11.0px ("Lifestyle"); <span> 11.9px ("By").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 21 passed
REVIEW
83

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Previous slide div.blogsy-posts-wrapper > div#blogsy-hero-nexo-slider > div.carousel-nav-wrapper > a.carousel-nav-prev
Next slide div.blogsy-posts-wrapper > div#blogsy-hero-nexo-slider > div.carousel-nav-wrapper > a.carousel-nav-next
Previous slide div.blogsy-posts-wrapper > div#blogsy-hero-elastic-carousel > div.carousel-nav-wrapper > a.carousel-nav-prev
Next slide div.blogsy-posts-wrapper > div#blogsy-hero-elastic-carousel > div.carousel-nav-wrapper > a.carousel-nav-next

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.pt-row > div.pt-col-12 > div.blogsy-card-items > div.blogsy-news-ticker-btn div.pt-row > div.pt-col-12 > div.blogsy-card-items > div.blogsy-news-ticker-btn

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest div.blogsy-post-elastic-widget > div.hero-tabs-inner > button.tab-btn > h5
Diwali Wholesale Lights in Delhi: LED Diyas, Lamps and Candles at Sadar Bazaar div.post-inner > div.content-wrapper > div.content-inner > h6.title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a
div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a
div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a
div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a div.blogsy-news-ticker-items > div.blogsy-news-ticker-item > div.item-thumbnail > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content body.home > div#site > div#site-inner > a.skip-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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 are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 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: 1 all-caps heading(s)
A+
Alt Text Quality
All 86 images OK
PASS
All 86 images OK
Info::
8 decorative image(s) correctly marked
Info::
78 image(s) with good alt text
86 images 78 good alt text 8 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
stextSearcharia-label
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
11 explicit tabindex attribute(s) checked, no anti-patterns
PASS
11 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
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 Search19.94:13.0:1
#000000
#FAF8FF
Pass
h2 Featured Post19.94:13.0:1
#000000
#FAF8FF
Pass
h2 GALLERY19.94:13.0:1
#000000
#FAF8FF
Pass
title BolBala - Explore Le…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Facebook19.94:14.5:1
#000000
#FAF8FF
Pass
span Youtube19.94:14.5:1
#000000
#FAF8FF
Pass
span Twitter19.94:14.5:1
#000000
#FAF8FF
Pass
span Instagram19.94:14.5:1
#000000
#FAF8FF
Pass
span Pinterest19.94:14.5:1
#000000
#FAF8FF
Pass
a Bol Bala19.94:14.5:1
#000000
#FAF8FF
Pass
p what you need is her…19.94:14.5:1
#000000
#FAF8FF
Pass
a Bol Bala19.94:14.5:1
#000000
#FAF8FF
Pass
p what you need is her…19.94:14.5:1
#000000
#FAF8FF
Pass
span Home19.94:14.5:1
#000000
#FAF8FF
Pass
span food19.94:14.5:1
#000000
#FAF8FF
Pass
span Travel19.94:14.5:1
#000000
#FAF8FF
Pass
span Lifestyle19.94:14.5:1
#000000
#FAF8FF
Pass
span Trending19.94:14.5:1
#000000
#FAF8FF
Pass
span Deals19.94:14.5:1
#000000
#FAF8FF
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