Skip to content
https://celebrai-ai-event.hatchable.site/?utm_source=chatgpt.com&_hbpvclear=1

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-2qdvp8
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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
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.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer

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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #1b2a6b
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 1 pass AA only
h1 অনুষ্ঠান বন্ধু
1.59:1
#000000
on
#1B2A6B
needs 3.0:1 (large text)
32px · top of page (header area)
h2 অনুষ্ঠানের তথ্…
1.59:1
#000000
on
#1B2A6B
needs 3.0:1 (large text)
24px · above the fold
title অনুষ্ঠান বন্ধু…
1.59:1
#000000
on
#1B2A6B
needs 4.5:1 (normal text)
16px · top of page (header area)
a মূল অংশে যাও
1.59:1
#000000
on
#1B2A6B
needs 4.5:1 (normal text)
16px · top of page (header area)
p পাড়ার পুজো, কলà…
1.59:1
#000000
on
#1B2A6B
needs 4.5:1 (normal text)
16px · top of page (header area)
button English
1.59:1
#000000
on
#1B2A6B
needs 4.5:1 (normal text)
16px · above the fold
p সব ঘর পূরণ করতে …
1.59:1
#000000
on
#1B2A6B
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 অনুষ্ঠঅ1.59:13.0:1
#000000
#1B2A6B
Fail
h2 অনুষ্ঠঅ1.59:13.0:1
#000000
#1B2A6B
Fail
h2 তোমার পà…18.29:13.0:1
#000000
#EDEFF7
Pass
h2 বাজেট কà…18.29:13.0:1
#000000
#EDEFF7
Pass
h2 কোন কাজ …18.29:13.0:1
#000000
#EDEFF7
Pass
h2 আইডিয়অ18.29:13.0:1
#000000
#EDEFF7
Pass
h2 প্ল্যাঅ18.29:13.0:1
#000000
#EDEFF7
Pass
h2 কিছু বদà…18.29:13.0:1
#000000
#EDEFF7
Pass
h3 সবার আগà…18.29:13.0:1
#000000
#EDEFF7
Pass
h3 তোমার অà…18.29:13.0:1
#000000
#EDEFF7
Pass
h3 খরচ কমাà…18.29:13.0:1
#000000
#EDEFF7
Pass
h3 WhatsApp-এ পাà…18.29:13.0:1
#000000
#EDEFF7
Pass
h3 উত্তর18.29:13.0:1
#000000
#EDEFF7
Pass
title অনুষ্ঠঅ1.59:14.5:1
#000000
#1B2A6B
Fail
a মূল অংশà…1.59:14.5:1
#000000
#1B2A6B
Fail
p পাড়ার à…1.59:14.5:1
#000000
#1B2A6B
Fail
button English1.59:14.5:1
#000000
#1B2A6B
Fail
p সব ঘর পূ…1.59:14.5:1
#000000
#1B2A6B
Fail
label কীসের অà…4.94:14.5:1
#000000
#6F79A3
Pass
option পাড়ার à…18.29:14.5:1
#000000
#EDEFF7
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.

A+
Heading Hierarchy
13 headings
PASS
13 headings
Info::
Single H1 present
  • H1 অনুষ্ঠান বন্ধু
  • H2 অনুষ্ঠানের তথ্য দাও
  • H2 তোমার প্ল্যান
  • H2 বাজেট কোথায় কত
  • H2 কোন কাজ কবে নাগাদ শেষ
  • H2 আইডিয়া ও পরামর্শ
  • H3 সবার আগে
  • H3 তোমার অনুষ্ঠানের জন্য আইডিয়া
  • H3 খরচ কমানোর উপায়
  • H3 WhatsApp-এ পাঠানোর বার্তা
  • H2 প্ল্যানারকে জিজ্ঞেস করো
  • H3 উত্তর
  • H2 কিছু বদলেছে?
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
12 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: 12 all-caps heading(s)
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
All 15 controls labeled
PASS
All 15 controls labeled
Info::
15 control(s) properly labeled
15 controls
15 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#eventTypeselectকীসের অনুষ্ঠান?for/id
#eventDatedateঅনুষ্ঠানের তারিখfor/id
#headcountnumberকতজন আসবে?for/id
#budgetnumberমোট বাজেট (টাকা)for/id
dietradionone
dietradionone
#notestextareaআর কিছু বলার আছে? (ঐচ্ছিক)for/id
#messageBoxtextareaবার্তার খসড়াfor/id
#qaInputtextতোমার প্রশ্নfor/id
#changeTypeselectকী বদলেছে?for/id
#delayTaskselectকোন কাজ?for/id
#delayDaysnumberকত দিন পিছোল?for/id
#newDatedateনতুন তারিখfor/id
#newBudgetnumberনতুন বাজেট (টাকা)for/id
#newHeadcountnumberনতুন অতিথির সংখ্যাfor/id
A+
Form Input Types
15 form control(s) checked, no type mismatches
PASS
15 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
15 form control(s) checked, no input-semantic issues
PASS
15 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 "bn"
PASS
Lang attribute set to "bn"
Info::
<html lang="bn"> is set and valid
Got: bn
A+
Tabindex Anti-Patterns
5 explicit tabindex attribute(s) checked, no anti-patterns
PASS
5 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+
Mobile-Readable Font Sizes
All 18 visible text node(s) render at >= 12 CSS pixels
PASS
All 18 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 26 passed
PASS
100

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.

○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
●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
●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
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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.
○Image elements have `[alt]` attributes
○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
○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.
○`<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.
○Identical links have the same purpose.
○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