Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Form Accessibility

2 of 24 controls have issues

REVIEW

2 of 24 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit" name="wp-submit" id="wp-submit">; <input type="submit">

22 control(s) properly labeled

24 controls

22 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#user_login	text	Username or Email Address	for/id
#user_pass	password	Password	for/id
#rememberme	checkbox		none
#wccSwitchfunctional	checkbox	Enable Functional	aria-label
#wccSwitchanalytics	checkbox	Enable Analytics	aria-label
#wccSwitchadvertisement	checkbox	Enable Advertisement	aria-label
#wccSwitchothers	checkbox	Enable Others	aria-label
_sf_s	search	Search for:	none
#sf-input-3d33023bbd8eab2b9c09885a3ac22ca2	checkbox	Artificial Intelligence and automation	for/id
#sf-input-47fdd7c17cb17b5b9bad8d3b092e87d0	checkbox	Broadcasting	for/id
#sf-input-f22f7f2fc344083d929d262757682025	checkbox	Cybersecurity, privacy and users	for/id
#sf-input-11acab5f9edbdb2e0f1a0b888df82b9b	checkbox	ICT infrastructure and operations	for/id
#sf-input-137cd92b212a6af775be82be190f86a1	checkbox	Next generation technologies	for/id
#sf-input-24c72e7e5b0a63b83de7a50fd3528ed7	checkbox	Software for standards	for/id
#sf-input-c41705a882b5212703cce35f59f1ac8c	checkbox	Technologies for life	for/id
#sf-input-d8a3b0b5928fbd4bbb47b284af8921c1	checkbox	Testing and interoperability	for/id
#sf-input-8dc5fb049f8a7e9f6450dfc6dfb7dace	checkbox	Transport technologies	for/id
#sf-input-036e06d0c60743094b02ce48a266462b	checkbox	Wireless and mobile technologies	for/id
#sf-input-bfc09607117fe9e1de84cbf19784f59b	checkbox	Technologies	for/id
#sf-input-25679078df41dd5e58ac7d96e17ca191	checkbox	Technical groups	for/id
#sf-input-b88b16c0680ea8415c43bf87b9cd6a88	checkbox	Events	for/id
#sf-input-8ffef0121a51c3316a634da9f7bb392e	checkbox	News / Press Releases	for/id
#wp-submit	submit	(none)	none
input	submit	(none)	none

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

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

Link & Button Quality

Action

5 issue(s) across 137 links and 18 buttons

REVIEW

5 issue(s) across 137 links and 18 buttons

5 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /membership/micro-enterprises ("Learn more"); /membership/large-corporations ("Learn more"); /membership/universities ("Learn more"); /membership/research-bodies ("Learn more"); /membership/public-authorities ("Learn more")

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.webtoffee.com/product/gdpr-cookie-consent/; https://portal.etsi.org/; https://www.etsi.org/subscribe-events/; https://www.etsi.org/subcribe-news/; https://www.youtube.com/user/ETSIstandards; https://www.linkedin.com/company/etsi?trk=biz-companies-cym

126 link(s) with descriptive text

137 links

0 empty

5 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.webtoffee.com/product/gdpr-c…	WebToffee product page, opens …	new tab	Add '(opens in new tab)' to text
https://portal.etsi.org/	Member Portal	new tab	Add '(opens in new tab)' to text
https://www.etsi.org/subscribe-events/	Sign up for Events news	new tab	Add '(opens in new tab)' to text
/membership/micro-enterprises	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Micro Enterprises
/membership/large-corporations	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Large Corporations
/membership/universities	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Universities
/membership/research-bodies	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Research Bodies
/membership/public-authorities	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Public Authorities
https://www.etsi.org/subcribe-news/	Sign up for ETSI newsletter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/ETSIstandar…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/etsi?tr…	LinkedIn	new tab	Add '(opens in new tab)' to text

144 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/membership/micro-enterprises ("Learn more"); /membership/large-corporations ("Learn more"); /membership/universities ("Learn more"); /membership/research-bodies ("Learn more"); /membership/public-authorities ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.webtoffee.com/product/gdpr-cookie-consent/; https://portal.etsi.org/; https://www.etsi.org/subscribe-events/; https://www.etsi.org/subcribe-news/; https://www.youtube.com/user/ETSIstandards; https://www.linkedin.com/company/etsi?trk=biz-companies-cym

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Heading Hierarchy

50 headings, 1 skip(s)

PASS

50 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Welcome
H2 to the global community that is shaping tomorrow’s technology standards
H3 We are the standards people.
H2 Explore our technology landscape
H4 Step 1 - Select your technology area of interest skipped
H4 Step 2 - Discover ETSI work, technical groups, events and news related to that technology area
H3 ETSI’s Response to the European Commission’s Proposal for the Cybersecurity Act 2
H3 Technology Radar
H3 Electronic Attestation of Attributes (EAA) PlugtestsTM
H3 ETSI General Assembly: the time for ETSI is now!
H2 Upcoming events
H3 FutureNet World 2026
H3 CRA Standards Unlocked – EU Tour
H3 Defense Communications Forum
H3 Electronic Attestation of Attributes (EAA) PlugtestsTM
H3 Webinar: ETSI OpenOP – Enabling Telco Cloud Network Federation & 6G Experimentation
H3 10th MCX PlugtestsTM
H3 POSTPONED – TFS#9 Hackfest
H3 Webinar: AI in evolution of Autonomous Networks
H3 NG112 PlugtestsTM 2026
H3 NG eCall PlugtestsTM 2026
H3 EuCNC & 6G Summit
H3 ETSI/IQC Quantum Safe Cryptography Conference 2026
H3 Stay up to date on latest ETSI events.
H2 Why work with ETSI? Empowering innovation with global standards
H3 Network & collaborate
H3 Access & influence
H3 Gain competitive edge
H3 Maximise impact
H2 ETSI serves all types of organisations
H3 Micro, Small and Medium-sized Enterprises (MSMEs)
H3 Large corporations
H3 Universities
H3 Research bodies
H3 Public authorities, regulators & NSOs
H2 Trending news
H3 ETSI’s Response to the European Commission’s Proposal for the Cybersecurity Act 2
H3 ETSI General Assembly: the time for ETSI is now!
H3 ETSI announces OpenCAPIF Release 4 aligned with 3GPP
H3 ETSI 2026 Fellows Unveiled at General Assembly Dinner
H3 From vision to action: Strengthening EU–Japan standards cooperation for trusted digital futures
H3 ETSI Releases First Version of Open-Source Operator Platform to Enable Telco Cloud Network Federation & 6G Experimentation
H3 Shaping Europe’s Cybersecurity Standards: Highlights from the 10th Cybersecurity Standardisation Conference
H3 ETSI issues new Report on Security, Privacy, Trustworthiness and Sustainability for 6G Integrated Sensing and Communications
H3 ETSI issues new Report on ISAC System and RAN Architectures
H3 ETSI AI & DATA conference Ecosystem Collaboration, Education and “AI‑Native” Standardisation
H3 ETSI Open Source MANO announces OSM Release NINETEEN, bringing a significant modernization of its codebase
H3 One year on: Strengthening ETSI’s Voice in Global Digital Policy
H3 Get regular news from ETSI
H2 Follow us on LinkedIn

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

A+

Alt Text Quality

All 40 images OK

PASS

All 40 images OK

18 decorative image(s) correctly marked

22 image(s) with good alt text

40 images 22 good alt text 18 decorative

All images have appropriate alt text.

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - ETSI ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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 Welcome	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 to the global commun…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Explore our technolo…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Upcoming events	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Empowering innovatio…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 ETSI serves all type…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Trending news	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Follow us on LinkedI…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 We are the standards…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 ETSI’s Response to…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Technology Radar	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Electronic Attestati…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 ETSI General Assembl…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 FutureNet World 2026	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 CRA Standards Unlock…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Defense Communicatio…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Electronic Attestati…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Webinar: ETSI OpenOP…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 10th MCX Plugtests	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 POSTPONED – TFS#9 …	20.12:1	3.0:1	#000000	#FAFAFA	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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 27 passed

PASS

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.

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
Step 1 - Select your technology area of interest `form#search-filter-form-27 > ul > li.sf-field-taxonomy-technology > h4`

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 9 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 10 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 11 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 12 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 1 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 9 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 10 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 11 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 12 `div.swiper_arrows_adjust > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.