Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

27 headings, 1 skip(s)

REVIEW

27 headings, 1 skip(s)

Multiple H1 headings (6 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

H1 You chair a conference.We have all you need.One platform: EasyChair
H1 Services we provide duplicate H1
H2 Conference management system
H2 Registration
H2 Publishing
H2 Smart CFP
H2 Smart Slide
H2 WEB TRAFFIC: 21M+ PAGES PER MONTH
H1 4,738,746 duplicate H1
H1 123,788 duplicate H1
H1 21,192 duplicate H1
H2 SINCE 2002 ON THE MARKET
H1 Thousands of customers trust EasyChair, including: duplicate H1
H3 Úlfar Erlingsson skipped
H3 Pascal van Hentenryck
H3 Manuel Hermenegildo
H3 Philippe Darondeau
H3 Eugenio Moggi
H3 Leonid Libkin
H3 Moshe Vardi
H3 Achim Jung
H3 Fabio Casati
H3 Ion Mandoiu
H3 Andrei Voronkov
H3 Tetsuo Ida
H3 Robert Miner
H3 Kurt Mehlhorn

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

Alt Text Quality

Action

43 of 52 images have issues

REVIEW

43 of 52 images have issues

43 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

9 image(s) with good alt text

52 images 9 good alt text 43 missing

Issue	Count
missing	43 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

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 12 passed

REVIEW

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
Log in `div.q-buttons-container > div.q-buttons-top > div.linklogin > a`
Learn more ▶ `div.content-row > div.content-block > p.learnmore-link > a`
Learn more ▶ `div.content-row > div.content-block > p.learnmore-link > a`
Learn more ▶ `div.content-row > div.content-block > p.learnmore-link > a`
Learn more ▶ `div.content-row > div.content-block > p.learnmore-link > a`
Learn more ▶ `div.content-row > div.content-block > p.learnmore-link > a`
Organisations: `div.page > div.stripe > div.segment > div.group-logos-title`
Associations/Societies: `div.page > div.stripe > div.segment > div.group-logos-title`
North America: `div.page > div.stripe > div.segment > div.group-logos-title`
Asia and Oceania: `div.page > div.stripe > div.segment > div.group-logos-title`
Europe: `div.page > div.stripe > div.segment > div.group-logos-title`
South America: `div.page > div.stripe > div.segment > div.group-logos-title`
Conference management `div.content-block > ul.qlinks > li > a`
Registration `div.content-block > ul.qlinks > li > a`
Publishing `div.content-block > ul.qlinks > li > a`
Smart CFP `div.content-block > ul.qlinks > li > a`
Smart Slide `div.content-block > ul.qlinks > li > a`
Smart Program `div.content-block > ul.qlinks > li > a`
About Us `div.content-block > ul.qlinks > li > a`
Contact `div.content-block > ul.qlinks > li > a`
Careers `div.content-block > ul.qlinks > li > a`
Testimonials `div.content-block > ul.qlinks > li > a`
Policy for conferences `div.content-block > ul.qlinks > li > a`
Privacy `div.content-block > ul.qlinks > li > a`
Terms of service `div.content-block > ul.qlinks > li > a`
Create conference `div.content-block > ul.qlinks > li > a`
Licenses and pricing `div.content-block > ul.qlinks > li > a`
FAQ `div.content-block > ul.qlinks > li > a`
Copyright © 2002-2026 EasyChair `div.stripe > div.segment > div.content-row > div.to-center`

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
Achim Jung `div#slider:2 > div.content-row > div.content-block-testimonial > h3.testimonials`

These are opportunities to improve keyboard navigation in your application.

Best practices

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 `html`

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-hidden="true"]` is not present on the document `<body>`

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

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

○`[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]`s are contained by their required parent element

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

89 links, 0 buttons — all OK

PASS

89 links, 0 buttons — all OK

89 link(s) with descriptive text

89 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

89 links and buttons have descriptive text

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)

Element	Ratio	Required	FG	BG	Result
h1 You chair a conferen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 We have all you need…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 One platform: EasyCh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Services we provide	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 4,738,746	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 123,788	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 21,192	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Thousands of custome…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 WEB TRAFFIC:	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 PAGES PER MONTH	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SINCE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ON THE MARKET	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Úlfar Erlingsson	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pascal van Hentenryc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manuel Hermenegildo	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Philippe Darondeau	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Eugenio Moggi	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Leonid Libkin	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Moshe Vardi	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Achim Jung	21.00:1	3.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.