Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Heading Hierarchy

Action

31 headings, 3 skip(s)

FIX

31 headings, 3 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H3 → H5 (missing H4)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 Home
H1 Home duplicate H1
H2 Eurosam
H3 Innovative Air Defense
H2 GROUND SYSTEMS
H3 SAMP/T NG
H3 The New European Long-Range Ground-Based Air Defense system
H2 Naval systems
H3 SAAM and PAAMS ensure area defense, consort ship protection and ship self-defense
H2 Aster family
H3 Single missile to defeat all types of threats from short to long-range
H4 Ground Systems
H4 Naval Systems
H4 ASTER Missiles
H4 In Service Support
H5 Corporate
H3 EUROPEAN AIR DEFENSE
H5 Innovation skipped
H3 SAMP/T NG and innovation
H2 Key figures of ASTER missile-based systems
H4 12G€ skipped
H4 12
H4 >50
H4 >1000
H2 Latest news
H4 France orders the multi-layered version of the SAMP/T NG air... skipped
H4 SUCCESSFUL FIRINGS WITH THE SAMP/T NG LONG-RANGE AIR DEFENCE...
H3 Further information
H3 Corporate
H3 Media
H3 Solutions

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 ▾

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

6 issue(s) across 69 links and 20 buttons

FIX

6 issue(s) across 69 links and 20 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#section1; a#section1

4 link(s) with generic text

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

Got: /history/ ("More"); /innovation-skills/ ("More"); https://eurosam.com/france-orders-the-multi-layered-version-of-the-samp-t-ng-… ("read more"); https://eurosam.com/successful-firings-with-the-samp-t-ng-long-range-air-defe… ("read more")

3 link(s) open in new tab without warning

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

Got: https://www.cookieyes.com/product/cookie-consent; https://fr.linkedin.com/company/eurosam-gie; https://www.youtube.com/channel/UC6tBsm9zARSizcjKm3A9pYQ

60 link(s) with descriptive text

69 links

2 empty

4 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookieyes.com/product/cookie…	Cookieyes logo	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
/history/	More	generic text	Replace with descriptive text
Before: More Suggested: History
	(empty)	empty	Add link text or aria-label
/innovation-skills/	More	generic text	Replace with descriptive text
Before: More Suggested: Innovation Skills
https://eurosam.com/france-orders-the-mu…	read more	generic text	Replace with descriptive text
Before: read more Suggested: France Orders The Multi Layered Version Of The Samp T Ng Air And Missile Defence System
https://eurosam.com/successful-firings-w…	read more	generic text	Replace with descriptive text
Before: read more Suggested: Successful Firings With The Samp T Ng Long Range Air Defence Systems
https://fr.linkedin.com/company/eurosam-…	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UC6tBsm9…	YouTube	new tab	Add '(opens in new tab)' to text

80 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#section1; a#section1

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

/history/ ("More"); /innovation-skills/ ("More"); https://eurosam.com/france-orders-the-multi-layered-version-of-the-samp-t-ng-… ("read more"); https://eurosam.com/successful-firings-with-the-samp-t-ng-long-range-air-defe… ("read 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.cookieyes.com/product/cookie-consent; https://fr.linkedin.com/company/eurosam-gie; https://www.youtube.com/channel/UC6tBsm9zARSizcjKm3A9pYQ

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

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

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

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

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

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

404 Error Page

Action

Could not test

REVIEW

Could not test

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.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

title Innovative Air Defense | EUROSAM

1.18:1

#000000

#0C1922

needs 4.5:1 (normal text)

16px · top of page (header area)

p Cookie consent

2.44:1

#565662

#0D1A24

needs 4.5:1 (normal text)

16px · top of page (header area)

div This website uses cookies that help the …

2.44:1

#565662

#0E1A24

needs 4.5:1 (normal text)

16px · top of page (header area)

button Preferences

4.40:1

#7F7F7F

#0E1A24

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Home	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h1 Home	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h2 Key figures of ASTER…	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h2 Latest news	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Innovative	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Air Defense	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 SAMP/T NG	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 The New European Lon…	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 SAAM and PAAMS ensur…	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Single missile to de…	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 EUROPEAN AIR DEFENSE	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 SAMP/T NG and innova…	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Further information	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Corporate	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Media	14.69:1	3.0:1	#000000	#D4D8DF	Pass
h3 Solutions	14.69:1	3.0:1	#000000	#D4D8DF	Pass
title Innovative Air Defen…	1.18:1	4.5:1	#000000	#0C1922	Fail
p Cookie consent	2.44:1	4.5:1	#565662	#0D1A24	Fail
div This website uses co…	2.44:1	4.5:1	#565662	#0E1A24	Fail
button Preferences	4.40:1	4.5:1	#7F7F7F	#0E1A24	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H4: "12"

Got: 1 ≤2-char heading(s)

5 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 5 all-caps heading(s)

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

7 decorative image(s) correctly marked

15 image(s) with good alt text

22 images 15 good alt text 7 decorative

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#ckySwitchanalytics	checkbox	Enable Analytics	aria-label
#ckySwitchadvertisement	checkbox	Enable Advertisement	aria-label
#searchTopField	search		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

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

4 form control(s) checked, no input-semantic issues

PASS

4 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

7 explicit tabindex attribute(s) checked, no anti-patterns

PASS

7 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 58 visible text node(s) render at >= 12 CSS pixels

PASS

All 58 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 24 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.

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
Preferences `div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn`
Reject All `div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn`

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
INNOVATION `div.et_pb_column > div.et_pb_module > div.et_pb_toggle > h5.et_pb_toggle_title`
12G€ `div.et_pb_module > div.et_pb_text_inner > div > h4`
FRANCE ORDERS THE MULTI-LAYERED VERSION OF THE SAMP/T NG AIR... `div.et_pb_salvattore_content > div.column > article#post-227040 > h4.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.

●ARIA attributes are used as specified for the element's role

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

●Touch targets have sufficient size and spacing.

●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

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

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

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

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