Skip to content
https://festflow.online

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 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-wfeshz
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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://festflow.online/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://festflow.online/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
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: #08080a
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 ModePartial Dark Mode
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
41 headings, 2 skip(s)
REVIEW
41 headings, 2 skip(s)
Info::
Single H1 present
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: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Discover, organize & ticket campus events effortlessly.
  • H4 0% Platform Fee skipped
  • H4 Sub-Second Entry
  • H4 Team Engine
  • H2 Scroll the campus event horizon. Live Now.
  • H3 IoT InnovateX 2026
  • H3 CODESTORM 2026
  • H2 Scroll the campus event horizon. Live Now.
  • H3 IoT InnovateX 2026
  • H3 CODESTORM 2026
  • H2 Engineered for students. Optimized for organizers. Step by step.
  • H3 Discover Events
  • H3 Register Solo or Team
  • H3 Direct UPI Payment
  • H3 Organizer Verification
  • H3 Gate QR Admittance
  • H2 Everything your campus event needs. Built for scale. Zero fluff.
  • H3 Custom Registration Fields
  • H3 Team & Solo Roster Controls
  • H3 Direct UPI Payments
  • H3 Camera QR Gate Check-in
  • H3 Registered Club Profiles
  • H3 Real-Time Notification Pipeline
  • H2 Find your campus pulse. Explore by passion. All fields.
  • H3 Technical & Hackathons
  • H3 Cultural & Arts
  • H3 Sports & Tournaments
  • H3 Workshops & Bootcamps
  • H3 Gaming & Esports
  • H3 Literary & Debates
  • H2 Cryptographic digital passes. Zero gate bottlenecks. Instant entry.
  • H4 Sub-Second Camera Scan skipped
  • H4 Live Replay Defense
  • H3 Nexus Hackathon 2026
  • H2 Upcoming campus events. Register Now.
  • H3 IoT InnovateX 2026
  • H3 CODESTORM 2026
  • H2 Ready to elevate your campus events? Start in seconds.
  • H3 Platform
  • H3 Community
  • H3 Legal

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Mobile-Readable Font Sizes
Action
73% of visible text renders at >= 12 CSS px (66 below threshold)
REVIEW
73% of visible text renders at >= 12 CSS px (66 below threshold)
Warning::
66 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> 10.0px ("Direct UPI to club bank"); <p> 10.0px ("Camera QR gate scanner"); <p> 10.0px ("Solo & roster verification"); <p> 10.0px ("Engineered for University Chapters & Stu..."); <span> 10.0px ("tech").
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::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ 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
h3 IoT InnovateX 2026
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CODESTORM 2026
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IoT InnovateX 2026
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CODESTORM 2026
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Discover Events
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Register Solo or Team
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Direct UPI Payment
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Organizer Verification
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Gate QR Admittance
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Custom Registration Fields
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Team & Solo Roster Controls
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Direct UPI Payments
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Camera QR Gate Check-in
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Registered Club Profiles
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Real-Time Notification Pipeline
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Technical & Hackathons
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cultural & Arts
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sports & Tournaments
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Workshops & Bootcamps
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Gaming & Esports
1.29:1
#000000
on
#202022
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 IoT InnovateX 20261.29:13.0:1
#000000
#202022
Fail
h3 CODESTORM 20261.29:13.0:1
#000000
#202022
Fail
h3 IoT InnovateX 20261.29:13.0:1
#000000
#202022
Fail
h3 CODESTORM 20261.29:13.0:1
#000000
#202022
Fail
h3 Discover Events1.29:13.0:1
#000000
#202022
Fail
h3 Register Solo or Tea…1.29:13.0:1
#000000
#202022
Fail
h3 Direct UPI Payment1.29:13.0:1
#000000
#202022
Fail
h3 Organizer Verificati…1.29:13.0:1
#000000
#202022
Fail
h3 Gate QR Admittance1.29:13.0:1
#000000
#202022
Fail
h3 Custom Registration …1.29:13.0:1
#000000
#202022
Fail
h3 Team & Solo Roster C…1.29:13.0:1
#000000
#202022
Fail
h3 Direct UPI Payments1.29:13.0:1
#000000
#202022
Fail
h3 Camera QR Gate Check…1.29:13.0:1
#000000
#202022
Fail
h3 Registered Club Prof…1.29:13.0:1
#000000
#202022
Fail
h3 Real-Time Notificati…1.29:13.0:1
#000000
#202022
Fail
h3 Technical & Hackatho…1.29:13.0:1
#000000
#202022
Fail
h3 Cultural & Arts1.29:13.0:1
#000000
#202022
Fail
h3 Sports & Tournaments1.29:13.0:1
#000000
#202022
Fail
h3 Workshops & Bootcamp…1.29:13.0:1
#000000
#202022
Fail
h3 Gaming & Esports1.29:13.0:1
#000000
#202022
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
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" 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::
3 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: 3 all-caps heading(s)
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
8 image(s) with good alt text
8 images 8 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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
18 explicit tabindex attribute(s) checked, no anti-patterns
PASS
18 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 24 passed
PASS
91

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Interactive 3D FestFlow Campus Characters div.max-w-7xl > div.grid > div.lg:col-span-5 > div.relative

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
ENGINEERED FOR UNIVERSITY CHAPTERS & STUDENT COMMUNITIES div.w-full > main#main-content > div.py-6 > p.text-center
The 100% free event platform built for college clubs and their student communit… div.relative > div.grid > div.col-span-2 > p.text-sm
PLATFORM div.relative > div.grid > div > h3.text-[11px]
COMMUNITY div.relative > div.grid > div > h3.text-[11px]
LEGAL div.relative > div.grid > div > h3.text-[11px]
© 2026 FestFlow. All rights reserved. footer.relative > div.relative > div.pt-6 > p.text-xs
Built with for campus communities footer.relative > div.relative > div.pt-6 > p.text-xs
Discover nav.fixed > div.flex > a.flex > span.text-[10px]
For Clubs nav.fixed > div.flex > a.flex > span.text-[10px]
Sign In nav.fixed > div.flex > a.flex > span.text-[10px]

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
0% Platform Fee div.grid > div.p-3.5 > div > h4.text-xs
Sub-Second Camera Scan div.lg:col-span-7 > div.grid > div.p-4 > h4.text-xs

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
TECH TEAM ₹999 IOT CLUB - AU Registration Open IoT InnovateX 2026 Wed, 4 Nov, 2… ul.grid > li > div.h-full > a.block
TECH TEAM FREE IOT CLUB - AU Registration Open CODESTORM 2026 Sat, 21 Nov, 2026… ul.grid > li > div.h-full > a.block
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA `progressbar` elements have accessible names
●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
●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.
●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
○`[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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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