Skip to content
https://cricketaffiliate.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 REVIEW 5 FIX
D
Mobile Keyboard & Autofill
Action
4/5 eligible field(s) missing autocomplete or inputmode
FIX
4/5 eligible field(s) missing autocomplete or inputmode
Warning::
4 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: search, email, url.
Got: <input type="search" name="adl_q" id="adl-q">, <input type="email" name="email" id="email">, <input type="url" name="url" id="url">, <input type="search" name="s" id="s">
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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Heading Hierarchy
62 headings, 1 skip(s)
REVIEW
62 headings, 1 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: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 BONUS
  • H5 FREE SPINS BONUS
  • H5 SUMMARY
  • H5 INFO
  • H5 POSITIVES
  • H5 NEGATIVES
  • H1 Crickex Affiliate Program – Commission, Requirements & How to Join.
  • H3 This page helps you: skipped
  • H1 Bangladesh Affiliate Programs duplicate H1
  • H2 Find the Right Route Before Sending Serious Traffic
  • H3 IF you are still unsure which program type fits you
  • H3 IF you already want to compare options
  • H3 IF you already picked a brand
  • H2 Choose your path first.
  • H2 Why Crickex Affiliate Selection Needs a System
  • H3 Match the program with the right traffic route.
  • H3 Recommendation
  • H3 IF the offer looks strong but payout rules are unclear
  • H3 IF your traffic source is not defined
  • H3 IF you cannot track clicks, registrations, and first deposits separately
  • H2 The 5-Step Crickex Affiliate Roadmap
  • H3 Identify Your Traffic Type
  • H3 Traffic Type Decision
  • H3 Choose the Right Evaluation Route
  • H3 Route Decision
  • H3 Check Payout Logic Before Traffic Volume
  • H3 Do Not Choose by Headline Numbers
  • H3 Verify Tracking and Dashboard Quality
  • H3 Track Campaigns by Source
  • H3 Run a Trust and Market-Fit Check
  • H3 Check the User Journey
  • H3 Check Support and Scaling Risk
  • H2 Beginner Path vs Pro Affiliate Path
  • H3 Choose this path if you are still learning how affiliate programs work.
  • H3 Choose this path if you already control traffic and understand performance data.
  • H2 Our Trust Framework for Crickex Affiliate Programs
  • H3 Payout Clarity
  • H3 Tracking Reliability
  • H3 Market Fit
  • H3 Support Quality
  • H3 Conversion and Retention Logic
  • H2 Where Should You Go Next?
  • H3 I want to compare options broadly
  • H3 I have cricket traffic
  • H3 I care most about payout
  • H3 I am new to affiliate marketing
  • H3 I run betting-focused traffic
  • H3 Not sure yet?
  • H2 Quick Decision Checklist
  • H3 Before You Choose
  • H3 Before You Scale
  • H3 IF your traffic source is unclear
  • H3 IF payout terms are unclear
  • H3 IF tracking is clear and the first test performs well
  • H2 FAQ
  • H2 Choose the right route before choosing a program.
  • H3 Leave a Reply Cancel reply
  • H2 Still deciding which affiliate route fits your traffic?
  • H3 Affiliate Routes
  • H3 Top Brand Audits
  • H3 Company & Trust
  • H3 Legal & Support

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

B
Form Accessibility
2 of 10 controls have issues
REVIEW
2 of 10 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s" id="s">
Info::
8 control(s) properly labeled
10 controls
8 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#adl-qsearchSearch programsfor/id
#adl_categoryselectCategoryfor/id
#adl_modelselectModelfor/id
#commenttextareaComment *for/id
#authortextName *for/id
#emailemailEmail *for/id
#urlurlWebsitefor/id
#wp-comment-cookies-consentcheckboxSave my name, email, and website in this browser for the next time I comment.for/id
#ssearch(Search…)placeholder only
#submitsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="submit" id="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="search" name="s" id="s">

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
86% of visible text renders at >= 12 CSS px (39 below threshold)
REVIEW
86% of visible text renders at >= 12 CSS px (39 below threshold)
Warning::
39 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: <div> 11.0px ("Terms & conditions apply"); <div> 10.5px ("Crickex affiliate roadmap"); <th> 11.0px ("Program"); <th> 11.0px ("Category"); <th> 11.0px ("Model").
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
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 Crickex Affiliate Program – Commission…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Bangladesh Affiliate Programs
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Find the Right Route Before Sending Seri…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Choose your path first.
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Crickex Affiliate Selection Needs a …
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The 5-Step Crickex Affiliate Roadmap
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Beginner Path vs Pro Affiliate Path
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Trust Framework for Crickex Affiliat…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Where Should You Go Next?
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Quick Decision Checklist
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQ
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Choose the right route before choosing a…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Still deciding which affiliate route fit…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h3 This page helps you:
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IF you are still unsure which program ty…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IF you already want to compare options
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IF you already picked a brand
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Match the program with the right traffic…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Recommendation
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IF the offer looks strong but payout rul…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Crickex Affiliate Pr…1.11:13.0:1
#000000
#111111
Fail
h1 Bangladesh Affiliate…1.11:13.0:1
#000000
#111111
Fail
h2 Find the Right Route…1.11:13.0:1
#000000
#111111
Fail
h2 Choose your path fir…1.11:13.0:1
#000000
#111111
Fail
h2 Why Crickex Affiliat…1.11:13.0:1
#000000
#111111
Fail
h2 The 5-Step Crickex A…1.11:13.0:1
#000000
#111111
Fail
h2 Beginner Path vs Pro…1.11:13.0:1
#000000
#111111
Fail
h2 Our Trust Framework …1.11:13.0:1
#000000
#111111
Fail
h2 Where Should You Go …1.11:13.0:1
#000000
#111111
Fail
h2 Quick Decision Check…1.11:13.0:1
#000000
#111111
Fail
h2 FAQ1.11:13.0:1
#000000
#111111
Fail
h2 Choose the right rou…1.11:13.0:1
#000000
#111111
Fail
h2 Still deciding which…1.11:13.0:1
#000000
#111111
Fail
h3 This page helps you:1.11:13.0:1
#000000
#111111
Fail
h3 IF you are still uns…1.11:13.0:1
#000000
#111111
Fail
h3 IF you already want …1.11:13.0:1
#000000
#111111
Fail
h3 IF you already picke…1.11:13.0:1
#000000
#111111
Fail
h3 Match the program wi…1.11:13.0:1
#000000
#111111
Fail
h3 Recommendation1.11:13.0:1
#000000
#111111
Fail
h3 IF the offer looks s…1.11:13.0:1
#000000
#111111
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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
6 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: 6 all-caps heading(s)
A
Alt Text Quality
2 of 51 images have issues
PASS
2 of 51 images have issues
Warning::
2 image(s) with generic alt text
Info::
2 decorative image(s) correctly marked
Info::
47 image(s) with good alt text
51 images 47 good alt text 2 decorative 2 generic
IssueCount
generic2 image(s)
A+
Form Input Types
10 form control(s) checked, no type mismatches
PASS
10 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
10 form control(s) checked, no input-semantic issues
PASS
10 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 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
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 - cricketaffiliate ✓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 92/100 — 4 failing, 28 passed
PASS
92

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.

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
ChatGPT div.asb-share-bar > div.asb-buttons > a.asb-btn > span.asb-btn__label
Google AI div.asb-share-bar > div.asb-buttons > a.asb-btn > span.asb-btn__label
Claude div.asb-share-bar > div.asb-buttons > a.asb-btn > span.asb-btn__label
COMPARE BEST PROGRAMS div#col-893498739 > div.col-inner > a.button > span
CHECK PAYOUT SAFETY div#col-1542839393 > div.col-inner > a.button > span
REVIEW TRUST FRAMEWORK div#col-92074199 > div.col-inner > a.button > span

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
This page helps you: div#col-150898804 > div.col-inner > div#text-2777374439 > h3

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.col-5 > div.widget-content-left > div.widget-info > a.widget-logo div.col-5 > div.widget-content-left > div.widget-info > a.widget-logo

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PROGRAM CATEGORY MODEL PAYOUT RATING Megapari Affiliate Program Megapari Gam… div#content > div.adl-directory > div.adl-table-wrap > table.adl-table
○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
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●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.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback