Skip to content
https://informa.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Alt Text Quality
Action
7 of 32 images have issues
FIX
7 of 32 images have issues
Critical::
7 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::
25 image(s) with good alt text
32 images 25 good alt text 7 missing
IssueCount
missing7 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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 64/100 — 9 failing, 17 passed
FIX
64

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
News div.col-6 > div.tabsToAccordion > div.tabsToAccordion-container > h2#tab_item-0
Calendar div.col-6 > div.tabsToAccordion > div.tabsToAccordion-container > h2#tab_item-1
Results div.col-6 > div.tabsToAccordion > div.tabsToAccordion-container > h2#tab_item-2

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
News div.col-6 > div.tabsToAccordion > div.tabsToAccordion-container > h2#tab_item-0
Calendar div.col-6 > div.tabsToAccordion > div.tabsToAccordion-container > h2#tab_item-1
Results div.col-6 > div.tabsToAccordion > div.tabsToAccordion-container > h2#tab_item-2

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
Learn more about Informa div.wysiwyg > ul.ctaWhiteList > li > a
Read the 2025 Full Year Results release ul.ctaWhiteList > ul.ctaWhiteList > li > a
Watch the Group CEO summary message ul.ctaWhiteList > ul.ctaWhiteList > li > a
Watch the investor presentation ul.ctaWhiteList > ul.ctaWhiteList > li > a
View the presentation slides ul.ctaWhiteList > ul.ctaWhiteList > li > a
Visit the microsite div.multiHeroBodyWrap > div.wysiwyg > p > a.ctaSkyBlue
Why invest in Informa div.campaignPromoBlockBody > ul.ctaWhiteList > li > a
Financial summary div.campaignPromoBlockBody > ul.ctaWhiteList > li > a
Shareholder centre div.campaignPromoBlockBody > ul.ctaWhiteList > li > a
Trends in our markets div.campaignPromoBlock > div.campaignPromoBlockBody > p > a.ctaSkyBlue
Life at Informa div > ul.ctaWhiteList > li > a
Purpose & principles div > ul.ctaWhiteList > li > a
Diversity & inclusion div > ul.ctaWhiteList > li > a
Vacancies div > ul.ctaWhiteList > li > a
Our FasterForward programme div.wysiwyg > ul.ctaWhiteList > li > a.ctaSkyBlue
Sustainability in our products div.wysiwyg > ul.ctaWhiteList > li > a
Climate commitments and progress div.wysiwyg > ul.ctaWhiteList > li > a

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
14,000 div.owl-item > div.carouselSmall-item > div.carouselSmall-body > h3.carouselSmall-title

These are opportunities to improve keyboard navigation in your application.

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.campaignPromoBlock > div.campaignPromoBlockImg > a > img div.campaignPromoBlock > div.campaignPromoBlockImg > a > img
div.campaignPromoBlock > div.campaignPromoBlockImg > a > img div.campaignPromoBlock > div.campaignPromoBlockImg > a > img
div.campaignPromoBlock > div.campaignPromoBlockImg > a > img div.campaignPromoBlock > div.campaignPromoBlockImg > a > img
div.owl-item > div.largeCarousel-item > picture.shelf-img > img div.owl-item > div.largeCarousel-item > picture.shelf-img > img
div.owl-item > div.largeCarousel-item > picture.shelf-img > img div.owl-item > div.largeCarousel-item > picture.shelf-img > img
div.owl-item > div.largeCarousel-item > picture.shelf-img > img div.owl-item > div.largeCarousel-item > picture.shelf-img > img
div.owl-item > div.largeCarousel-item > picture.shelf-img > img div.owl-item > div.largeCarousel-item > picture.shelf-img > 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
div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockImg > a div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockImg > a
div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockImg > a div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockImg > a
div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockImg > a div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockImg > 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.

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
Read the 2025 Full Year Results release Watch the Group CEO summary message Wat… div.col-6 > div.campaignPromoBlock > div.campaignPromoBlockBody > ul.ctaWhiteList
Read the 2025 Full Year Results release Watch the Group CEO summary message Wat… div.campaignPromoBlock > div.campaignPromoBlockBody > ul.ctaWhiteList > ul.ctaWhiteList
Read the 2025 Full Year Results release Watch the Group CEO summary message Wat… div.campaignPromoBlockBody > ul.ctaWhiteList > ul.ctaWhiteList > ul.ctaWhiteList

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
Accessibility Statement div.footerBottomLinks > ul > li > a
Terms & Conditions div.footerBottomLinks > ul > li > a
Privacy Policy div.footerBottomLinks > ul > li > a
Cookie Policy div.footerBottomLinks > ul > li > a
Modern Slavery Statement div.footerBottomLinks > ul > li > a
Site Map div.footerBottomLinks > ul > li > a

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.js html.js

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 are valid and not misspelled
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Skip links are focusable.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
○`[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.
○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
○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
○`<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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
C
Landmark Structure
Action
4 landmarks
REVIEW
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.
Info::
Skip navigation link present
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

B
Heading Hierarchy
57 headings, 1 skip(s)
REVIEW
57 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Championing the specialist
  • H3 14,000 skipped
  • H3 30
  • H3 FTSE 100
  • H3 100s
  • H3 14,000
  • H3 30
  • H3 FTSE 100
  • H3 100s
  • H2 Informa 2025 Results
  • H2 News
  • H2 Calendar
  • H2 Results
  • H2 What's new at Informa?
  • H2 Investing in Informa
  • H2 Our Specialist Markets
  • H2 Far from business as usual
  • H2 Far from business as usual
  • H2 Life at Informa
  • H3 (empty)
  • H2 Learn about Life@Informa
  • H2 Our Divisions
  • H3 Informa Connect
  • H4 Connect, Learn, Network
  • H5 Discover Informa Connect
  • H3 Informa Festivals
  • H4 Experience-led Events
  • H5 Discover Informa Festivals
  • H3 Informa TechTarget
  • H4 B2B Data & Market Access
  • H5 Discover Informa TechTarget
  • H3 Taylor & Francis
  • H4 Academic Research
  • H5 Discover Taylor & Francis
  • H3 Informa Markets
  • H4 Trade, Innovate, Grow
  • H5 Discover Informa Markets
  • H3 Informa Connect
  • H4 Connect, Learn, Network
  • H5 Discover Informa Connect
  • H3 Informa Festivals
  • H4 Experience-led Events
  • H5 Discover Informa Festivals
  • H3 Informa TechTarget
  • H4 B2B Data & Market Access
  • H5 Discover Informa TechTarget
  • H3 Taylor & Francis
  • H4 Academic Research
  • H5 Discover Taylor & Francis
  • H3 Informa Markets
  • H4 Trade, Innovate, Grow
  • H5 Discover Informa Markets
  • H3 Informa Connect
  • H4 Connect, Learn, Network
  • H5 Discover Informa Connect
  • H2 Sustainability
  • H2 2024 Sustainability Report

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Home ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-sitetextSearch Informafor/id
inputsubmit(none)none

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

<input type="submit">

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

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 Championing the spec…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Informa 2025 Results21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Calendar21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Results21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What's new at Inform…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Investing in Informa21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Specialist Marke…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Far from business as…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Life at Informa21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Learn about Life@Inf…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Divisions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sustainability21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2024 Sustainability …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 14,00021.00:13.0:1
#000000
#FFFFFF
Pass
h3 FTSE 10021.00:13.0:1
#000000
#FFFFFF
Pass
h3 100s21.00:13.0:1
#000000
#FFFFFF
Pass
h3 14,00021.00:13.0:1
#000000
#FFFFFF
Pass
h3 FTSE 10021.00:13.0:1
#000000
#FFFFFF
Pass
h3 100s21.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