Skip to content
https://business-money.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (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
Heading Hierarchy
Action
58 headings, 13 skip(s)
FIX
58 headings, 13 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 info@business-money.com
  • H6 +44 (0)1458 259483
  • H2 This month's edition of Business Money
  • H2 Business Money Subscribers Directory IF/ABL
  • H1 Our latest editions
  • H3 Edition 330 – May/June 2026 skipped
  • H3 Edition 329 – March/April 2026
  • H3 Edition 328 – January/February 2026
  • H3 Edition 327 – December 2025
  • H3 Edition 326 – October/November 2025
  • H3 Edition 325 – August/September 2025
  • H3 Magazine subscription
  • H5 With a subscription you can read your edition online as well as in print. skipped
  • H3 The Forum of Private Business
  • H5 Business Money is the commercial finance partner for the Forum of Private Business. skipped
  • H3 Magazine subscription
  • H5 With a subscription you can read your edition online as well as in print. skipped
  • H3 The Forum of Private Business
  • H5 Business Money is the commercial finance partner for the Forum of Private Business. skipped
  • H1 Jobs duplicate H1
  • H1 News duplicate H1
  • H5 Daily business finance and industry news from Business Money – free to you. skipped
  • H2 Latest news
  • H5 Five of the top ten fastest scaling global data centres markets are in EMEA skipped
  • H5 Iran war pushing up the cost of borrowing for county businesses
  • H5 Why Slovenia and the Philippines are becoming strategic bases for remote‑first startups
  • H5 Used car market returns to growth as EV sales accelerate
  • H2 Latest news
  • H5 Five of the top ten fastest scaling global data centres markets are in EMEA skipped
  • H5 Iran war pushing up the cost of borrowing for county businesses
  • H5 Why Slovenia and the Philippines are becoming strategic bases for remote‑first startups
  • H5 Used car market returns to growth as EV sales accelerate
  • H1 Our latest editions duplicate H1
  • H3 Edition 330 – May/June 2026 skipped
  • H3 Edition 329 – March/April 2026
  • H3 Edition 328 – January/February 2026
  • H3 Edition 327 – December 2025
  • H3 Edition 326 – October/November 2025
  • H3 Edition 325 – August/September 2025
  • H3 Edition 324 – June/July 2025
  • H3 Edition 323 – May 2025
  • H3 Edition 322 – March/April 2025
  • H3 Edition 321 – February 2025
  • H3 The Forum of Private Business
  • H5 Business Money is the commercial finance partner for the Forum of Private Business. skipped
  • H3 Magazine subscription
  • H5 With a subscription you can read your edition online as well as in print. skipped
  • H1 Jobs duplicate H1
  • H1 News duplicate H1
  • H5 Daily business finance and industry news from Business Money – free to you. skipped
  • H2 Latest news
  • H5 Five of the top ten fastest scaling global data centres markets are in EMEA skipped
  • H5 Iran war pushing up the cost of borrowing for county businesses
  • H5 Why Slovenia and the Philippines are becoming strategic bases for remote‑first startups
  • H5 Used car market returns to growth as EV sales accelerate
  • H5 Social links
  • H5 Get in touch
  • H5 Pages

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

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

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

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

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

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

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

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

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

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

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

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

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

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
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
Iframe Accessibility
3/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://f6ff73e8.sibforms.com/serve/MUIFAKS1BQLCXE5IheMx1E9zp3Bqa_ICNWgUNnEVORd…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://f6ff73e8.sibforms.com/serve/MUIFAKS1BQLCXE5IheMx1E9zp3Bqa_ICNWgUNnEVORd…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 3 pass AA only
title Business Finance & Banking News | Busine…
1.70:1
#000000
on
#243261
needs 4.5:1 (normal text)
16px · top of page (header area)
div Manage Consent
1.70:1
#000000
on
#243261
needs 4.5:1 (normal text)
16px · top of page (header area)
p We use cookies that help us provide you …
1.70:1
#000000
on
#243261
needs 4.5:1 (normal text)
16px · top of page (header area)
span Functional
1.70:1
#000000
on
#243261
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Our latest editions14.88:13.0:1
#000000
#D9D9D9
Pass
h1 Our latest editions14.88:13.0:1
#000000
#D9D9D9
Pass
h2 This month's edition…14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Business Money Subsc…14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Latest news14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Latest news14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Latest news14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Magazine subscriptio…14.88:13.0:1
#000000
#D9D9D9
Pass
h3 The Forum of Private…14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Magazine subscriptio…14.88:13.0:1
#000000
#D9D9D9
Pass
h3 The Forum of Private…14.88:13.0:1
#000000
#D9D9D9
Pass
h3 The Forum of Private…14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Magazine subscriptio…14.88:13.0:1
#000000
#D9D9D9
Pass
title Business Finance & B…1.70:14.5:1
#000000
#243261
Fail
div Manage Consent1.70:14.5:1
#000000
#243261
Fail
p We use cookies that …1.70:14.5:1
#000000
#243261
Fail
span Functional1.70:14.5:1
#000000
#243261
Fail
span Functional4.81:14.5:1
#000000
#77797B
Pass
span Always active4.81:14.5:1
#000000
#77797B
Pass
span The technical storag…4.74:14.5:1
#000000
#76787A
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 25 passed
REVIEW
89

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
Discover more rs-slides > rs-slide > rs-layer-wrap.rs-parallax-wrap > a#slider-1-slide-1-layer-6
Sign up to our newsletter div.vc_column-inner > div.wpb_wrapper > div.rt-heading-wrapper > span.punchline
in Industry and broker news, Lender and investor news, News div.post-content-wrapper > div.entry-content > div.post_data > span.categories
Industry and broker news div.entry-content > div.post_data > span.categories > a
Lender and investor news div.entry-content > div.post_data > span.categories > a
News div.entry-content > div.post_data > span.categories > a
According to Savills Impacts global thought leadership programme, five of the t… article#118762 > div.post-content-wrapper > div.entry-content > p
in Industry and broker news, News, SME economic news div.post-content-wrapper > div.entry-content > div.post_data > span.categories
Industry and broker news div.entry-content > div.post_data > span.categories > a
News div.entry-content > div.post_data > span.categories > a
SME economic news div.entry-content > div.post_data > span.categories > a
The ongoing war in Iran which is pushing up the cost of borrowing for UK SMEs (… article#118758 > div.post-content-wrapper > div.entry-content > p
in Industry and broker news, Lender and investor news, News div.post-content-wrapper > div.entry-content > div.post_data > span.categories
Industry and broker news div.entry-content > div.post_data > span.categories > a
Lender and investor news div.entry-content > div.post_data > span.categories > a
News div.entry-content > div.post_data > span.categories > a
Remote‑first startups are increasingly choosing Slovenia and the Philippines as… article#118725 > div.post-content-wrapper > div.entry-content > p
in Industry and broker news, Lender and investor news, Motor sales, repair and … div.post-content-wrapper > div.entry-content > div.post_data > span.categories
Industry and broker news div.entry-content > div.post_data > span.categories > a
Lender and investor news div.entry-content > div.post_data > span.categories > a
Motor sales, repair and hire div.entry-content > div.post_data > span.categories > a
News div.entry-content > div.post_data > span.categories > a
The UK’s used car market returned to growth in the second quarter, up 0.7% as 2… article#118723 > div.post-content-wrapper > div.entry-content > p

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe div.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe

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#text-1 > div.textwidget > p > a div#text-1 > div.textwidget > p > 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.

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
Edition 330 – May/June 2026 article#117247 > div.post-content-wrapper > div.entry-content > h3.entry-title
Business Money is the commercial finance partner for the Forum of Private Busin… div.vc_column-inner > div.wpb_wrapper > div.rt-heading-wrapper > h5.rt-heading
With a subscription you can read your edition online as well as in print. div.vc_column-inner > div.wpb_wrapper > div.rt-heading-wrapper > h5.rt-heading
Daily business finance and industry news from Business Money – free to you. div.vc_column-inner > div.wpb_wrapper > div.rt-heading-wrapper > h5.rt-heading
Five of the top ten fastest scaling global data centres markets are in EMEA article#118762 > div.post-content-wrapper > div.entry-content > h5.entry-title

These are opportunities to improve keyboard navigation in your application.

○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
●`[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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`<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.
○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+
Heading Text Quality
All 58 heading(s) have substantive, well-formed text
PASS
All 58 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 85 images OK
PASS
All 85 images OK
Info::
79 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
85 images 6 good alt text 79 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 15 controls have issues
PASS
1 of 15 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" id="gform_submit_button_1">
Info::
14 control(s) properly labeled
15 controls
14 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
#input_1_1textareaPresent loan facilities*for/id
#input_1_2textareaFinance currently provided by*for/id
#input_1_10textLast year’s turnover*for/id
#input_1_4textBusiness name*for/id
#input_1_6emailYour emailfor/id
#input_1_7telPhone number*for/id
#input_1_11_1checkboxFPBfor/id
#input_1_8_1checkboxI give my consent for you to retain my data for the purposes of processing and completing my request(s) **for/id
#input_1_12textCommentsfor/id
ak_hp_textareatextareaΔnone
#gform_submit_button_1submit(none)none

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

<input type="submit" id="gform_submit_button_1">

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+
Form Input Types
15 form control(s) checked, no type mismatches
PASS
15 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
15 form control(s) checked, no input-semantic issues
PASS
15 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
5 explicit tabindex attribute(s) checked, no anti-patterns
PASS
5 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 113 visible text node(s) render at >= 12 CSS pixels
PASS
All 113 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback