Skip to content
https://asiftraders.shop

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
84
GRADE
B
FIX
4
REVIEW
3
PASS
17
INFO
0
Checks
24
17 PASS 3 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
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Mobile-Readable Font Sizes
Action
82% of visible text renders at >= 12 CSS px (54 below threshold)
REVIEW
82% of visible text renders at >= 12 CSS px (54 below threshold)
Warning::
54 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: <small> 11.5px ("Get Best Price on WhatsApp"); <small> 11.5px ("Speak to Our Expert"); <span> 10.5px ("Binders"); <span> 11.0px ("27 products"); <span> 10.5px ("Reinforcement").
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Every material,
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cement
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Quotes the way
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 One consolidated quote for your entire p…
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tiles, blocks & roofing
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Steel & TMT — bulk supply
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why contractors
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to start your project?
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Common questions
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
24px · bottom of viewport
h3 UltraTech Cement - OPC 43 Grade
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 UltraTech Cement - OPC 53 Grade
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 UltraTech Cement - PPC
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ACC Cement - PPC
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Build your list
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get one consolidated quote
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Scheduled delivery
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Vitrified Floor Tiles
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ceramic Wall Tiles
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Wall Tiles
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
h3 GVT Floor Tiles
1.44:1
#000000
on
#292929
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Every material,1.44:13.0:1
#000000
#292929
Fail
h2 Cement1.44:13.0:1
#000000
#292929
Fail
h2 Quotes the way1.44:13.0:1
#000000
#292929
Fail
h2 One consolidated quo…1.44:13.0:1
#000000
#292929
Fail
h2 Tiles, blocks & roof…1.44:13.0:1
#000000
#292929
Fail
h2 Steel & TMT — bulk…1.44:13.0:1
#000000
#292929
Fail
h2 Why contractors1.44:13.0:1
#000000
#292929
Fail
h2 Ready to start your …1.44:13.0:1
#000000
#292929
Fail
h2 Common questions1.44:13.0:1
#000000
#292929
Fail
h3 UltraTech Cement - O…1.44:13.0:1
#000000
#292929
Fail
h3 UltraTech Cement - O…1.44:13.0:1
#000000
#292929
Fail
h3 UltraTech Cement - P…1.44:13.0:1
#000000
#292929
Fail
h3 ACC Cement - PPC1.44:13.0:1
#000000
#292929
Fail
h3 Build your list1.44:13.0:1
#000000
#292929
Fail
h3 Get one consolidated…1.44:13.0:1
#000000
#292929
Fail
h3 Scheduled delivery1.44:13.0:1
#000000
#292929
Fail
h3 Vitrified Floor Tile…1.44:13.0:1
#000000
#292929
Fail
h3 Ceramic Wall Tiles1.44:13.0:1
#000000
#292929
Fail
h3 Wall Tiles1.44:13.0:1
#000000
#292929
Fail
h3 GVT Floor Tiles1.44:13.0:1
#000000
#292929
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Primary" MAIN ASIDE "Navigation menu" CONTENTINFO footer

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

A
Heading Hierarchy
43 headings, 1 skip(s)
PASS
43 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 BuildingStrongerFutures.
  • H2 Every material, one index
  • H2 Cement & binders
  • H3 UltraTech Cement - OPC 43 Grade
  • H3 UltraTech Cement - OPC 53 Grade
  • H3 UltraTech Cement - PPC
  • H3 ACC Cement - PPC
  • H2 Quotes the way sites work
  • H3 Build your list
  • H3 Get one consolidated quote
  • H3 Scheduled delivery
  • H2 One consolidated quote for your entire project
  • H2 Tiles, blocks & roofing
  • H3 Vitrified Floor Tiles
  • H3 Ceramic Wall Tiles
  • H3 Wall Tiles
  • H3 GVT Floor Tiles
  • H3 AAC Block 600×200×200
  • H3 Galvanized Roofing Sheets
  • H3 Polycarbonate Roofing Sheets
  • H2 Steel & TMT — bulk supply
  • H3 TMT Bar – 12mm
  • H3 TMT Bar – 16mm
  • H3 TMT Bar – 20mm
  • H3 MS Angle
  • H3 MS Channel
  • H3 H-Beams
  • H3 River Sand
  • H2 Why contractors choose us
  • H3 Trusted brands
  • H3 Quality materials
  • H3 Reliable supply
  • H3 Bulk orders
  • H3 Contractor-friendly service
  • H3 Quote-based ordering
  • H3 Build your list
  • H3 Get your quotation
  • H3 We deliver on time
  • H2 Ready to start your project?
  • H2 Common questions
  • H4 Categories skipped
  • H4 Quick Links
  • H4 Contact Info

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

Why this matters

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

Learn more

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Heading Text Quality
All 43 heading(s) have substantive, well-formed text
PASS
All 43 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
29 image(s) with good alt text
29 images 29 good alt text
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
qsearchSearch productsaria-label
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
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"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
404 Error Page
HTTP 404, custom page
PASS
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 Page Not Found | ASIF TRADERS Custom Styling Navigation Homepage Link Search Form
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
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 22 passed
PASS
90

Accessibility

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

ARIA

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
ASIF TRADERS BUILDING MATERIALS Login Sign Up Home Products Brands About Us Quo… body > aside.drawer

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Request a Quote Get Best Price on WhatsApp div.hero6-copy > div.hero6-ctas > a.hero6-cta > span
Get Best Price on WhatsApp div.hero6-ctas > a.hero6-cta > span > small
Call Now Speak to Our Expert div.hero6-copy > div.hero6-ctas > a.hero6-cta > span
Speak to Our Expert div.hero6-ctas > a.hero6-cta > span > small
ACC main#main > div.marquee > div.marquee-track > span.mq-b
DALMIA main#main > div.marquee > div.marquee-track > span.mq-b
SCROLL THE CATALOGUE div.container > div.look > div.look-head > span.look-hint
Sign Up aside.drawer > div.drawer-user > div.du-guest > a.du-btn

These are opportunities to improve the legibility of your content.

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
CATEGORIES div.container > div.footer-grid > div > h4

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ASIF TRADERS BUILDING MATERIALS main#main > section.hero6 > div#siteHeader > a.hero6-logo
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback