Skip to content
https://weezevent.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Alt Text Quality
Action
21 of 66 images have issues
FIX
21 of 66 images have issues
Critical::
21 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
8 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
66 images 37 good alt text 8 decorative 21 missing
IssueCount
missing21 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
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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Weezevent
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Weezevent ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Weezevent Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 26 passed
REVIEW
83

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
Copyright © Weezevent 2026 div#wrapper > footer.footer > div.row > span.footer__copyright

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flickity-viewport > div.flickity-slider > figure.is-selected > img.js-lazy div.flickity-viewport > div.flickity-slider > figure.is-selected > img.js-lazy

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
L’interface de gestion de la billetterie et l’application de scan sont pratique… section.o-ice > div.row > div.cell-start-0 > ul.testimonies

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Notre partenariat avec Weezevent nous donne les moyens de rassembler l’écosystè… ul.testimonies > div.slick-list > div.slick-track > li.testimony-tile
Cela fait plusieurs années que nous proposons les services de Weezevent à nos c… ul.testimonies > div.slick-list > div.slick-track > li.testimony-tile

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Nous contacter nav.nav > ul > li.item-contact > a.nav__item-first
Nous rejoindre nav.nav > ul > li.item-nous-rejoindre > a.nav__item-first
Espace médias nav.nav > ul > li.item-medias > a.nav__item-first
Aide en ligne nav.nav > ul > li.item-aide-en-ligne-4 > a.nav__item-first
Participants nav.nav > ul > li.item-participants > a.nav__item-first
État des services nav.nav > ul > li.item-etat-des-services-3 > a.nav__item-first
Avis Weezevent nav.nav > ul > li.item-satisfaction-client > a.nav__item-first
Cashless nav.nav > ul > li.item-cashless > a.nav__item-first
Sécurité nav.nav > ul > li.item-securite > a.nav__item-first
CGUS nav.nav > ul > li.item-cgus > a.nav__item-first
CGL nav.nav > ul > li.item-cgl > a.nav__item-first

These items highlight common accessibility best practices.

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
Ajuster div.cf2L3T > div.cf3Tgk > div.cf1lHZ > button.cf2Lf6
○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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●Links are distinguishable without relying on color.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○`<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
○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 Hierarchy
25 headings
PASS
25 headings
Info::
Single H1 present
  • H1 Lancez rapidement. Vendez plus.
  • H2 La billetterie plébiscitée par 1 million d'événements.
  • H3 Flexible.
  • H3 Accessible.
  • H3 Fiable.
  • H2 Une expérience simplifiée pour vous, vos équipes et vos participants.
  • H2 80% des participants réservent depuis leur téléphone. Scannez et testez !
  • H2 Un événement commence par sa billetterie.
  • H2 500 000 événements de tous types et de toutes tailles nous font confiance.
  • H2 weezaccess
  • H3 Contrôle d’Accès
  • H2 weezpay
  • H3 Paiement Cashless
  • H2 weezcrew .st0{fill:#fff}.st1{fill:#93f}
  • H3 Staff & Accréditations
  • H2 weeztarget
  • H3 Marketing & CRM
  • H2 Aide en ligne
  • H2 Accompagnement sur-mesure
  • H2 Actualités
  • H3 Organiser un flashmob en 7 étapes
  • H3 Quel coût envisagé pour un salon professionnel ?
  • H3 What’s new @ Weezevent – Avril 2026
  • H2 Prêt à lancer votre événement ?
  • H2 Bienvenue sur Weezevent !
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemail(Votre email)placeholder only

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

<input type="email" name="email">

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

A
Favicon & Branding
7 icon(s) detected
PASS
7 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 Present
✓ Multiple Sizes Present
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
h2 La billetterie pléb…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Une expérience simp…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 80% des participants…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Un événement comme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 500 000 événements…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 weezaccess21.00:13.0:1
#000000
#FFFFFF
Pass
h2 weezpay21.00:13.0:1
#000000
#FFFFFF
Pass
h2 weezcrew21.00:13.0:1
#000000
#FFFFFF
Pass
h2 weeztarget21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aide en ligne21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Accompagnement sur-m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Actualités21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Prêt à lancer votr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bienvenue sur Weezev…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Flexible.21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Accessible.21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fiable.21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contrôle d’Accès21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Paiement Cashless21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Staff & Accréditati…21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback