Skip to content
https://allevents.in

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Alt Text Quality
Action
3 of 140 images have issues
FIX
3 of 140 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
137 image(s) with good alt text
140 images 137 good alt text 3 missing
IssueCount
missing3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Form Accessibility
Action
10 of 10 controls have issues
FIX
10 of 10 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="daterange">; <input type="text" name="daterange">
Warning::
8 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="searchd-input">; <input type="search" name="hs_search_text">; <input type="search" name="search_text">; <input type="text">; <input type="search">; <input type="search">; <input type="search">; <input type="search">
10 controls
0 labeled
8 placeholder only
2 unlabeled
ControlTypeLabelMethod
#searchd-inputtext(Search All Events)placeholder only
hs_search_textsearch(Search Events, Categories, Location...)placeholder only
search_textsearch(Search Events, Categories, Location...)placeholder only
inputtext(Enter your city)placeholder only
inputsearch(Category)placeholder only
inputsearch(Format)placeholder only
inputsearch(Date)placeholder only
inputsearch(Price)placeholder only
daterangetext(none)none
daterangetext(none)none

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

<input type="text" name="daterange">; <input type="text" name="daterange">

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="text" id="searchd-input">; <input type="search" name="hs_search_text">; <input type="search" name="search_text">; <input type="text">; <input type="search">; <input type="search">; <input type="search">; <input type="search">

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

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-b8pceq
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.

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: #2e363f
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::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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!) NAV "Main Navigation" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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
Favicon & Branding
12 icon(s) detected
REVIEW
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Heading Hierarchy
38 headings
PASS
38 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Live. Don't Just Exist.
  • H2 São Paulo's Most-Loved
  • H2 Popular Events in São Paulo
  • H2 Trending Events in the Brazil
  • H3 TODO MUNDO NO RIO 2026
  • H3 Carnaval Rio 2027
  • H3 Thiago Ventura em Osasco - SP | 24 de Abril
  • H3 CIDADE NEGRA no Araújo Vianna | Porto Alegre/RS
  • H3 FIRE SHOW 🇧🇷 2026 – International Fire Fair
  • H3 3º Festival do Orgulho Nerd
  • H3 Candlelight: Tributo a Rush | Rio de Janeiro
  • H3 BETO CARRERO + BALNEÁRIO CAMBORIÚ
  • H3 Aline Nascimento - Vozes Silenciadas
  • H3 parada gay de sao paulo 2026
  • H2 Explore Events across the Globe
  • H1 Loved by millions. Lived on AllEvents duplicate H1
  • H2 Events Trending Worldwide
  • H3 DEEPSKY STARGAZING AT BHANDARDARA
  • H3 #DIF26 Donauinselfest 2026
  • H3 Golden Gate Comedy Night
  • H3 Fiesta Broadway 2026
  • H3 Women’s Wednesday Special! BUY 2 GET 2 FREE @ MGM Dizzee World
  • H3 AI Expo Africa 2026
  • H3 18th Solar PV and Energy Storage World Expo 2026 (PV Guangzhou)
  • H3 International West Africa Water Expo – Nigeria WAWE
  • H3 MEGA CLIMA NIGERIA HVAC+R EXPO 2026
  • H3 Melbourne's - True Crime Tour
  • H3 Meat-GEDS EXPO 2026
  • H3 Thursday Evening Class Wheel Throwing, Throwing Tasters and Hand Building
  • H3 Discover Events.
  • H3 Anywhere, Anytime.
  • H2 Site Navigation
  • H3 Discover Events
  • H3 For Organizers
  • H3 Host Better Events
  • H3 Explore
  • H3 Trending in Worldwide
  • H3 {{performer.name}}

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

A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: All Events in City
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name All Events in City ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=manifest ✓Display Mode standalone ✓
Name All Events in City Display Mode standalone Theme Color #20c0e8 Background Color #e8ecf1 Icons 7 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Don't Just Exist.10.36:13.0:1
#000000
#B4B7B3
Pass
h1 Loved by millions. L…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular Events in S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Events in t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events Trending Worl…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Site Navigation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TODO MUNDO NO RIO 20…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Carnaval Rio 202721.00:13.0:1
#000000
#FFFFFF
Pass
h3 Thiago Ventura em Os…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CIDADE NEGRA no Ara…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 FIRE SHOW 🇧🇷 2…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 3º Festival do Orgu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Candlelight: Tributo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 BETO CARRERO + BALNE…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Aline Nascimento - V…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 parada gay de sao pa…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 DEEPSKY STARGAZING A…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 #DIF26 Donauinselfes…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Golden Gate Comedy N…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fiesta Broadway 202621.00:13.0:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 21 passed
PASS
90

Accessibility

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

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
View all div.row-fluid > div.container > div.head-label > button.btn
Sat, 02 May • 09:45 PM div.meta > div.meta-top > div.meta-top-info > div.date
Praia de Copacabana - Rio de Janeiro li.event-card > div.meta > div.meta-middle > div.location
Fri, 05 Feb • 09:00 AM div.meta > div.meta-top > div.meta-top-info > div.date
Marques De Sapucai Sambodromo li.event-card > div.meta > div.meta-middle > div.location
1 day ago div.memories-card-review-content > div.memories-user-info > div > div.memories-user-time
Sat, 25 Apr Onwards div.meta > div.meta-top > div.meta-top-info > div.date
Bhandardara, India li.event-card > div.meta > div.meta-middle > div.location
Fri, 03 Jul Onwards div.meta > div.meta-top > div.meta-top-info > div.date
Vienna, Austria li.event-card > div.meta > div.meta-middle > div.location
© Copyright 2026. All Rights Reserved div.home-footer4 > div.container > div.span6 > span

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Manage Drover div.row > div.span7 > div.tbsearch_manage_drover_btn > button#manage-drover-btn

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.fonts-loaded html.fonts-loaded

These items highlight common accessibility best practices.

○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.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●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-hidden="true"]` elements do not contain focusable descendents
○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
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback