Skip to content
https://iec.ch

Accessibility

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

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

F
404 Error Page
Action
HTTP 202, bare page
FIX
HTTP 202, bare page
Warning::
Unexpected status code: HTTP 202
Expected HTTP 404 but received 202. This may confuse search engine crawlers.
Got: HTTP 202
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 202 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 23 passed
REVIEW
81

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
We use cookies on this site to enhance your user experience By clicking the Ac… body.path-node > div#sliding-popup

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
Past two weeks list section#single-element-text-7837 > div.text-link-container > div.item-link > a.hvr-icon-forward
Final Draft International Standards div.text-block-content > div.field > p > a
See details  section#single-element-text-7839 > div.text-link-container > div.item-link > a.hvr-icon-forward
Visit here section#single-element-text-3592 > div.text-link-container > div.item-link > a.hvr-icon-forward
Energy a > div.paragraph > div.iec-slide-item-title > div.field
Healthcare a > div.paragraph > div.iec-slide-item-title > div.field
SDGs a > div.paragraph > div.iec-slide-item-title > div.field
Cities & Communities a > div.paragraph > div.iec-slide-item-title > div.field
Climate action a > div.paragraph > div.iec-slide-item-title > div.field
Cyber security a > div.paragraph > div.iec-slide-item-title > div.field
Smart manufacturing a > div.paragraph > div.iec-slide-item-title > div.field
Transportation a > div.paragraph > div.iec-slide-item-title > div.field
Industry a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Government and regulators a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Developing countries a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Academia a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Read more div.iec-white-papers-slider-item > article.document > div.iec-document-card-read-more-container > a.iec-read-more
Read more div.iec-white-papers-slider-item > article.document > div.iec-document-card-read-more-container > a.iec-read-more
Please select the services that are of interest to you, and stay up to date wit… div.cs-container > div.iec-block-container > div.col-sm-12 > h2.block-subtitle
Details about our newsletters div.iec-block-container > div.block-readmore > div.field > a

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
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img

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.text-block-content > div.field > p > iframe.fw-iframe div.text-block-content > div.field > p > iframe.fw-iframe
div.text-block-content > div.field > p > iframe.fw-iframe div.text-block-content > div.field > p > iframe.fw-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.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.paragraph > ul.social-media-links--platforms > li > a.iec-facebook div.paragraph > ul.social-media-links--platforms > li > a.iec-facebook
div.paragraph > ul.social-media-links--platforms > li > a.iec-linkedin div.paragraph > ul.social-media-links--platforms > li > a.iec-linkedin
div.paragraph > ul.social-media-links--platforms > li > a.iec-youtube_channel div.paragraph > ul.social-media-links--platforms > li > a.iec-youtube_channel

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
countries div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
standards div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
certificates div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
experts div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-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
●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.
●ARIA attributes are used as specified for the element's role
●`[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
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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 Hierarchy
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 403 ERROR
  • H2 The request could not be satisfied.
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
6 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.

6 pass
Show all checked elements (6)
ElementRatioRequiredFGBGResult
h1 403 ERROR21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The request could no…21.00:13.0:1
#000000
#FFFFFF
Pass
title ERROR: The request c…21.00:14.5:1
#000000
#FFFFFF
Pass
body Request blocked. We …21.00:14.5:1
#000000
#FFFFFF
Pass
body If you provide conte…21.00:14.5:1
#000000
#FFFFFF
Pass
pre Generated by cloudfr…21.00:14.5: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