Skip to content
https://confex.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 (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

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✗
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
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: #ffffff
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
No navigation patterns
FIX
No navigation patterns
Info::
2 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 2 <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.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 4 failing, 11 passed
FIX
66

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
Continue to m|events div#modal > div.modal-content > p.right > a.button
Continue to m|events div#modal > div.modal-content > p.right > a.button
Read More! header > section.special > h3 > a.button
Your meeting, your way. ul > li > a > p
Reliable support onsite, online, and behind the scenes. ul > li > a > p
Our clients are front and center. ul > li > a > p
Access, Confidentiality & Trust. ul > li > a > p
Speaker Ready Room ul > li > a > p
Digital & Print Publishing ul > li > a > p
RELIABLE & SUSTAINABLE section.content > div#able > a > h1
Helping to manage over 200,000 presenters each year. div#able > a > ul > li
Distributing and archiving over 10,000 recorded presentations every year. div#able > a > ul > li
Trusted by leading scientific and medical societies. div#able > a > ul > li

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#modal > div.modal-content > div.modal-header > img div#modal > div.modal-content > div.modal-header > img
div#modal > div.modal-content > div.modal-header > img div#modal > div.modal-content > div.modal-header > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.social > ul > li > a section.social > ul > li > a
section.social > ul > li > a section.social > ul > li > a

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
body.home > meta body.home > meta

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>`
●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.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●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.
B
Alt Text Quality
2 of 4 images have issues
REVIEW
2 of 4 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with good alt text
4 images 2 good alt text 2 missing
IssueCount
missing2 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

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::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ 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
h1 Highly
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Configurable
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Personalized
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Support
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Your
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Branding
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Data Protection Services
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Onsite Services
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Design Services
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Reliable & Sustainable
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Copyright © 1996-
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 All Rights Reserved.
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
32px · bottom of viewport
h2 As of July 1st, Confex will now be servi…
1.08:1
#000000
on
#070D19
needs 3.0:1 (large text)
24px · top of page (header area)
h2 As of July 1st, Confex will now be servi…
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
24px · above the fold
h2 Online & Onsite Event Management Softwar…
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Speakers
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Abstracts
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Conference Planning
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Presentations
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Attendee Apps
1.99:1
#000000
on
#3F3F3F
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Highly1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Configurable1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Personalized1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Support1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Your1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Branding1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Data Protection Serv…1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Onsite Services1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Design Services1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Reliable & Sustainab…1.99:13.0:1
#000000
#3F3F3F
Fail
h1 Copyright © 1996-1.99:13.0:1
#000000
#3F3F3F
Fail
h1 All Rights Reserved.1.99:13.0:1
#000000
#3F3F3F
Fail
h2 As of July 1st, Conf…1.08:13.0:1
#000000
#070D19
Fail
h2 As of July 1st, Conf…1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Online & Onsite Even…1.99:13.0:1
#000000
#3F3F3F
Fail
h2 Speakers1.99:13.0:1
#000000
#3F3F3F
Fail
h2 Abstracts1.99:13.0:1
#000000
#3F3F3F
Fail
h2 Conference Planning1.99:13.0:1
#000000
#3F3F3F
Fail
h2 Presentations1.99:13.0:1
#000000
#3F3F3F
Fail
h2 Attendee Apps1.99:13.0:1
#000000
#3F3F3F
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
Heading Hierarchy
26 headings
PASS
26 headings
Warning::
Multiple H1 headings (12 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 As of July 1st, Confex will now be serving you as m|events
  • H2 As of July 1st, Confex will now be serving you as m|events
  • H1 The Conference Exchange®
  • H2 Online & Onsite Event Management Software
  • H3 We have some exciting news! Read More!
  • H1 HighlyConfigurable duplicate H1
  • H1 PersonalizedSupport duplicate H1
  • H1 YourBranding duplicate H1
  • H1 Data Protection Services duplicate H1
  • H1 Onsite Services duplicate H1
  • H1 Design Services duplicate H1
  • H1 Manage Your ProgramCollect, Plan, Present & Distribute duplicate H1
  • H2 Speakers
  • H2 Abstracts
  • H2 Conference Planning
  • H2 Presentations
  • H2 Attendee Apps
  • H1 Manage Attendees & EventsRegistrants, Learners, Exhibitors, Logistics duplicate H1
  • H2 Registration
  • H2 Continuing Education
  • H2 Exhibitors
  • H2 Event Management
  • H1 Reliable & Sustainable duplicate H1
  • H1 The Conference Exchange® duplicate H1
  • H2 Online & Onsite Event Management Software
  • H1 Copyright © 1996-2026 The Conference Exchange®,   All Rights Reserved. duplicate H1

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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback