Skip to content
https://www.trenzobd.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
24
10 PASS 6 REVIEW 8 FIX
F
Heading Hierarchy
Action
102 headings, 10 skip(s)
FIX
102 headings, 10 skip(s)
Warning::
Multiple H1 headings (79 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Search
  • H1 Shopping Cart (0 Item) duplicate H1
  • H1 Subtotal duplicate H1
  • H1 ৳0 duplicate H1
  • H1 Wallets that move with you Premium comfort meets everyday style. duplicate H1
  • H1 Wallets that move with you. Premium comfort meets everyday style. duplicate H1
  • H1 Trusted by Thousands ! Loved by 10,000+ Customers duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 10,000+ SATISFIED CUSTOMERS duplicate H1
  • H1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME DELIVERY NATIONWIDE duplicate H1
  • H1 Category by Shop duplicate H1
  • H1 The Flux Series duplicate H1
  • H1 Premium Microfiber Leather duplicate H1
  • H1 Shop Collection duplicate H1
  • H1 The Pulse Series duplicate H1
  • H1 Genuine Full Grain Leather duplicate H1
  • H1 Shop Collection duplicate H1
  • H1 iFinder – Smart Wallet Tracker duplicate H1
  • H1 Never Lose What Matters duplicate H1
  • H1 Shop Collection duplicate H1
  • H1 Latest Arrivals duplicate H1
  • H1 Mint Horizon duplicate H1
  • H3 BDT 1,900 skipped
  • H1 Azure Weave duplicate H1
  • H3 BDT 1,900 skipped
  • H1 Obsidian Flow duplicate H1
  • H3 BDT 1,900 skipped
  • H1 iFinder (Smart Wallet Tracker) duplicate H1
  • H3 BDT 1,600 skipped
  • H4 BDT 2,100
  • H1 Midnight Flow duplicate H1
  • H3 BDT 1,700 skipped
  • H4 BDT 1,850
  • H1 Espresso Weave duplicate H1
  • H3 BDT 1,900 skipped
  • H1 Crimson Barrel duplicate H1
  • H3 BDT 2,100 skipped
  • H4 BDT 2,350
  • H1 Olive Crown duplicate H1
  • H3 BDT 2,100 skipped
  • H4 BDT 2,350
  • H1 The Flux Series duplicate H1
  • H1 Mint Horizon duplicate H1
  • H1 Azure Weave duplicate H1
  • H1 Obsidian Flow duplicate H1
  • H1 Midnight Flow duplicate H1
  • H1 The Pulse Series duplicate H1
  • H1 Crimson Barrel duplicate H1
  • H1 Olive Crown duplicate H1
  • H1 Obsidian Vault duplicate H1
  • H1 Midnight Drift duplicate H1
  • H1 iFinder – Smart Wallet Tracker duplicate H1
  • H1 iFinder (Smart Wallet Tracker) duplicate H1
  • H1 Story of Trenzo duplicate H1
  • H4 View All skipped
  • H1 Nationwide Delivery duplicate H1
  • H1 Effortless Returns duplicate H1
  • H1 Cash on Delivery duplicate H1
  • H1 Customer Reviews duplicate H1
  • H3 Syed Saymun Rahman skipped
  • H3 Farhana Binte Mohiuddin
  • H3 Maruf
  • H3 Ohona Ona
  • H3 Samiul Sami
  • H3 N.K. Antara
  • H3 Tanvir Ahmed
  • H3 Ruhul Amin
  • H3 Nusrat Jahan
  • H1 Frequently Asked Questions duplicate H1
  • H1 What materials are used in Trenzo™ wallets? duplicate H1
  • H1 How many cards can a Trenzo™ wallet hold? duplicate H1
  • H1 What is iFinder? duplicate H1
  • H1 Is iFinder compatible with iPhone and Android? duplicate H1
  • H1 Does iFinder™ require an app or internet connection? duplicate H1
  • H1 Does Trenzo™ offer engraving? duplicate H1
  • H1 What is the engraving cost? duplicate H1
  • H1 Is advance payment required for engraving? duplicate H1
  • H1 Can engraved wallets be returned or exchanged? duplicate H1
  • H1 How long does delivery take? duplicate H1
  • H1 Is Cash on Delivery available? duplicate H1
  • H1 How can I track my order? duplicate H1
  • H1 Do Trenzo™ products come with warranty? duplicate H1
  • H1 What does the warranty cover? duplicate H1
  • H1 Join our newsletter duplicate H1
  • H1 Still Have Questions? duplicate H1
  • H1 We'd love to hear from you duplicate H1
  • H1 Trenzo duplicate H1
  • H1 We Accept duplicate H1

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

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

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

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

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

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

D
Mobile Keyboard & Autofill
Action
5/5 eligible field(s) missing autocomplete or inputmode
FIX
5/5 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">, <input type="email" name="email">
Warning::
3 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, tel.
Got: <input type="email">, <input type="email" name="email">, <input type="tel" name="phone">
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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
BANNER (missing!) MAIN CONTENTINFO (missing!)

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
Form Accessibility
7 of 7 controls have issues
REVIEW
7 of 7 controls have issues
Warning::
7 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="email">; <input type="text" name="fullName">; <input type="email" name="email">; <input type="tel" name="phone">; <input type="text" name="subject">; <textarea name="message">
7 controls
0 labeled
7 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(What are you looking for?)placeholder only
inputemail(Enter your email)placeholder only
fullNametext(Your name)placeholder only
emailemail(you@domain.com)placeholder only
phonetel(1XXXXXXXXX)placeholder only
subjecttext(Inquiry)placeholder only
messagetextarea(Write your message)placeholder only

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

<input type="text">; <input type="email">; <input type="text" name="fullName">; <input type="email" name="email">; <input type="tel" name="phone">; <input type="text" name="subject">; <textarea name="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

C
Mobile-Readable Font Sizes
Action
83% of visible text renders at >= 12 CSS px (56 below threshold)
REVIEW
83% of visible text renders at >= 12 CSS px (56 below threshold)
Warning::
56 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: <p> 11.0px ("Trending Now"); <span> 10.0px ("Item)"); <p> 10.0px ("Est. 2015"); <p> 10.0px ("NEW"); <p> 10.0px ("BEST SELLER").
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Create Next App ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
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
h1 Shopping Cart
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Subtotal
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 ৳
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Wallets that move
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 with you
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Wallets that move with you. Premium comf…
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Trusted by Thousands ! Loved by 10,000+ …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TRUSTED BY 10,000+ CUSTOMERS! FREE HOME …
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
h1 10,000+ SATISFIED CUSTOMERS
1.06:1
#000000
on
#030C09
needs 3.0:1 (large text)
32px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Shopping Cart1.06:13.0:1
#000000
#030C09
Fail
h1 Subtotal1.06:13.0:1
#000000
#030C09
Fail
h1 ৳1.06:13.0:1
#000000
#030C09
Fail
h1 Wallets that move1.06:13.0:1
#000000
#030C09
Fail
h1 with you1.06:13.0:1
#000000
#030C09
Fail
h1 Wallets that move wi…1.06:13.0:1
#000000
#030C09
Fail
h1 Trusted by Thousands…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
Fail
h1 TRUSTED BY 10,000+ C…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
Fail
h1 TRUSTED BY 10,000+ C…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
Fail
h1 TRUSTED BY 10,000+ C…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
Fail
h1 TRUSTED BY 10,000+ C…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
Fail
h1 TRUSTED BY 10,000+ C…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
Fail
h1 TRUSTED BY 10,000+ C…1.06:13.0:1
#000000
#030C09
Fail
h1 10,000+ SATISFIED CU…1.06:13.0:1
#000000
#030C09
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 20 passed
REVIEW
85

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.fixed > div.md:main-container > div.flex > button.relative div.fixed > div.md:main-container > div.flex > button.relative
div.fixed > div.flex > div.flex > button.p-2 div.fixed > div.flex > div.flex > button.p-2
div.fixed > div.flex > div.flex > button div.fixed > div.flex > div.flex > button
div.py-20 > div.flex > div.flex > button.border div.py-20 > div.flex > div.flex > button.border
div.py-20 > div.flex > div.flex > button.border div.py-20 > div.flex > div.flex > button.border

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.fixed > div.md:main-container > div.flex > a div.fixed > div.md:main-container > div.flex > a
div.flex > div.relative > p.text-[#475569] > a.text-white/50 div.flex > div.relative > p.text-[#475569] > a.text-white/50

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
TRENDING NOW div.p-6 > div.mt-8 > div > p.text-[11px]
(0 Item) div.flex > div.flex > h1.text-white > span.text-[#64748B]
Shipping and taxes calculated at checkout. div.fixed > div.flex > div.shrink-0 > p.mt-1
The Flux Series a > div > div > p.text-[#64748B]
The Flux Series a > div > div > p.text-[#64748B]
The Flux Series a > div > div > p.text-[#64748B]
iFinder – Smart Wallet Tracker a > div > div > p.text-[#64748B]
BDT 2,100 div > div > div.flex > h4.text-[#475569]
The Flux Series a > div > div > p.text-[#64748B]
BDT 1,850 div > div > div.flex > h4.text-[#475569]
The Flux Series a > div > div > p.text-[#64748B]
The Pulse Series a > div > div > p.text-[#64748B]
BDT 2,350 div > div > div.flex > h4.text-[#475569]
The Pulse Series a > div > div > p.text-[#64748B]
BDT 2,350 div > div > div.flex > h4.text-[#475569]
Premium Microfiber Leather div.bg-[#050F0C] > div.pt-12 > div.flex > p.text-[#64748B]
Explore our premium collection. div.bg-[#050F0C] > div.pt-12 > div.flex > p.mt-2
Mint Green div.p-4 > div.flex > div.flex > p.text-[#64748B]
Blue (Cross Pattern) div.p-4 > div.flex > div.flex > p.text-[#64748B]
Just Black div.p-4 > div.flex > div.flex > p.text-[#64748B]
BDT 1,850 a.group > div.p-4 > div.flex > p.text-[#64748B]
Blue div.p-4 > div.flex > div.flex > p.text-[#64748B]
Genuine Full Grain Leather div.bg-[#050F0C] > div.pt-12 > div.flex > p.text-[#64748B]
Explore our premium collection. div.bg-[#050F0C] > div.pt-12 > div.flex > p.mt-2
BDT 2,350 a.group > div.p-4 > div.flex > p.text-[#64748B]
Wine Red div.p-4 > div.flex > div.flex > p.text-[#64748B]
BDT 2,350 a.group > div.p-4 > div.flex > p.text-[#64748B]
Olive Green div.p-4 > div.flex > div.flex > p.text-[#64748B]
BDT 2,350 a.group > div.p-4 > div.flex > p.text-[#64748B]
Just Black div.p-4 > div.flex > div.flex > p.text-[#64748B]
BDT 2,350 a.group > div.p-4 > div.flex > p.text-[#64748B]
Blue div.p-4 > div.flex > div.flex > p.text-[#64748B]
Never Lose What Matters div.bg-[#050F0C] > div.pt-12 > div.flex > p.text-[#64748B]
Explore our premium collection. div.bg-[#050F0C] > div.pt-12 > div.flex > p.mt-2
BDT 2,100 a.group > div.p-4 > div.flex > p.text-[#64748B]
Black div.p-4 > div.flex > div.flex > p.text-[#64748B]
Safe and timely delivery to your door within 72 hours— premium service knows no… div.main-container-md > div.grid > div.flex > p.mt-2
Simply return the product to our delivery agent by covering the delivery fee—no… div.main-container-md > div.grid > div.flex > p.mt-2
Experience true convenience—pay only when it arrives at your doorstep. div.main-container-md > div.grid > div.flex > p.mt-2
Hear from our global community div.py-20 > div.flex > div.space-y-1 > p.text-white/40
Dhaka div.flex > div.flex > div.flex > span.text-[10px]
TRENZO div.w-[350px] > div.flex > div.opacity-20 > p.text-white
Everything You Need to Know About Trenzo Wallets & Smart Accessories div > div.pb-20 > div.pt-24 > p.mt-2
We care about your data in our privacy policy div.mt-12 > div.px-4 > div.w-full > p.text-[#52525B]
privacy policy div.px-4 > div.w-full > p.text-[#52525B] > span.underline
We're always here to assist you. div.grid > div > div > p.text-[#64748B]
CALL/WHATSAPP div.mt-6 > div.flex > div > p.text-[#64748B]
EMAIL div.mt-6 > div.flex > div > p.text-[#64748B]
LIVE CHAT div.mt-6 > div.flex > div > p.text-[#64748B]
SUPPORT HOURS div.mt-6 > div.flex > div > p.text-[#64748B]
LOCATION div.mt-6 > div.flex > div > p.text-[#64748B]
Your voice matters to us. div.grid > div > div.text-left > p.text-[#64748B]
Name * div > div.grid > div.flex > label.text-[#64748B]
Email * div > div.grid > div.flex > label.text-[#64748B]
Phone * div > div.grid > div.flex > label.text-[#64748B]
+880 div.grid > div.flex > div.flex > span.px-4
Subject * div > div.grid > div.flex > label.text-[#64748B]
Message * div > div.grid > div.flex > label.text-[#64748B]
Trenzo is your trusted source for premium wallet card holders — elegant design,… div.main-container-md > div.grid > div > p.text-[#64748B]
QUICK ACCESS div.main-container-md > div.grid > div > p.text-[#64748B]
CONTACT INFORMATION div.main-container-md > div.grid > div > p.text-[#64748B]
FOLLOW US div.main-container-md > div.grid > div > p.text-[#64748B]
© 2026 TRENZO | CARRY CONFIDENCE div.bg-black/40 > div.max-w-[85%] > div.flex > p.text-[#475569]
Design and Develop by div.max-w-[85%] > div.flex > div.relative > p.text-[#475569]

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
BDT 1,900 div > div > div.flex > h3.text-white
BDT 1,900 div > div > div.flex > h3.text-white
BDT 1,900 div > div > div.flex > h3.text-white
BDT 1,600 div > div > div.flex > h3.text-white
BDT 1,700 div > div > div.flex > h3.text-white
BDT 1,900 div > div > div.flex > h3.text-white
BDT 2,100 div > div > div.flex > h3.text-white
BDT 2,100 div > div > div.flex > h3.text-white
View All div.main-container-md > div.h-full > div.md:px-16 > h4.mt-6
Syed Saymun Rahman div.w-[350px] > div.flex > div > h3.text-white

These are opportunities to improve keyboard navigation in your application.

○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
●Image elements have `[alt]` attributes
●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
●`[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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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
○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
○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.
○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
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
1 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H1: "৳0"
Got: 1 ≤2-char heading(s)
Info::
28 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: 28 all-caps heading(s)
A+
Alt Text Quality
1 of 34 images have issues
PASS
1 of 34 images have issues
Warning::
1 image(s) with generic alt text
Info::
7 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
34 images 26 good alt text 7 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 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+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback