Aaccessibilitychecker.eu
← Back home

Accessibility Audit Report

eur-lex.europa.eu/eli/dir/2019/882/oj

Completed28 Jun 2026, 11:43viewport 1366 × 900

Results from cache — scanned less than 24 hours ago

Accessibility score

F31 / 100
Critical issues

Weighted by issue severity and affected elements.

Affected elements by severity

Critical1
Serious105
Moderate20
Minor0

9

Rule violations

126

Affected elements

51

Passed checks

3

Manual review

Executive summary

eur-lex.europa.eu/eli/dir/2019/882/oj scored 31/100 — a failing grade driven by issues that block core functionality for people with disabilities.

Across the page, automated checks flagged 9 distinct rule violations affecting 126 elements: 1 critical, 105 serious, and 20 moderate. The critical failures — certain ARIA roles must contain particular children — prevent screen-reader and keyboard users from completing key tasks.

A further 3 checks could not be evaluated automatically and require manual review, while 51 checks passed. Remediating the one critical rule and the most frequent serious issue — links must be distinguishable without relying on color — will clear the highest-impact barriers first.

Methodology

Scanned against WCAG 2.0 / 2.1 success criteria at a 1366 × 900 viewport, with the results mapped to practical EN 301 549 and European Accessibility Act readiness. Automated testing detects only part of WCAG risk; pair it with manual keyboard and assistive-technology testing for full coverage.

Legal compliance risk

Digital Accessibility Act readiness

Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to covered digital services across the EU market. Many organizations refer to this as the Digital Accessibility Act in procurement and compliance work. In practice, websites, apps, e-commerce, banking, transport, media and support journeys should align with EN 301 549 and WCAG AA expectations.

Non-compliance can trigger formal complaints, corrective orders, national authority investigations, financial penalties in EUR, reputational harm, contract loss, and restrictions on placing or keeping a non-conforming service in the market. This audit found 9 accessibility issues that may expose your organization to this risk and should be remediated promptly.

Priority implication: treat critical checkout, booking, account, payment and support barriers as commercial and compliance risks, not only technical defects. Remediation evidence can help demonstrate due diligence if customers, public buyers or regulators request proof of accessibility work.

Findings

9 rule violations, grouped by severity.

Critical1 rule · 1 element
Serious4 rules · 105 elements
Moderate4 rules · 20 elements

Critical

1 rule · 1 element
Criticalaria-required-children

1

element

Certain ARIA roles must contain particular children

Ensure elements with an ARIA role that require child roles contain them

WCAG 2.0 AWCAG 1.3.1

Why it matters

Blocks people with disabilities from using core functionality. Fix as a top priority.

How to fix

  • Element has children which are not allowed: div[aria-labelledby], [role=tabpanel]

Where — sample elements

.panel-group

<div class="panel-group" role="tablist" aria-multiselectable="true">

Serious

4 rules · 105 elements
Seriouslink-in-text-block

98

elements

Links must be distinguishable without relying on color

Ensure links are distinguished from surrounding text in a way that does not rely on color

WCAG 2.0 AWCAG 1.4.1

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

  • The link has insufficient color contrast of 1.67:1 with the surrounding text. (Minimum contrast is 3:1, link text: #0e47cb, surrounding text: #333333)
  • The link has no styling (such as underline) to distinguish it from the surrounding text

Where — sample elements

#ntc1-L_2019151EN\.01007001-E0001

<a id="ntc1-L_2019151EN.01007001-E0001" href="#ntr1-L_2019151EN.01007001-E0001">(<span class="oj-super oj-note-tag">1</span>)</a>

#ntc2-L_2019151EN\.01007001-E0002

<a id="ntc2-L_2019151EN.01007001-E0002" href="#ntr2-L_2019151EN.01007001-E0002">(<span class="oj-super oj-note-tag">2</span>)</a>

#ntc3-L_2019151EN\.01007001-E0003

<a id="ntc3-L_2019151EN.01007001-E0003" href="#ntr3-L_2019151EN.01007001-E0003">(<span class="oj-super oj-note-tag">3</span>)</a>

+ 95 more affected elements

Seriousnested-interactive

3

elements

Interactive controls must not be nested

Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies

WCAG 2.0 AWCAG 4.1.2

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

  • Element has focusable descendants

Where — sample elements

#PP2

<div class="panel-heading" role="tab" id="PP2">

#PP3

<div class="panel-heading" role="tab" id="PP3">

#PP4

<div class="panel-heading" role="tab" id="PP4">
Serioussvg-img-alt

3

elements

<svg> elements with an img role must have alternative text

Ensure <svg> elements with an img, graphics-document or graphics-symbol role have accessible text

WCAG 2.0 AWCAG 1.1.1

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

  • Element has no child that is a title
  • aria-label attribute does not exist or is empty
  • aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  • Element has no title attribute

Where — sample elements

.ecl-site-header__language-icon > .ecl-site-header__icon.login-lang-image-size[\"=""]

<svg class="ecl-icon ecl-icon--s ecl-site-header__icon login-lang-image-size" focusable="false" aria-hidden="false" role="img" "="" viewBox="0 0 24 24">

.ef-questionmark-icon

<svg class="ef-questionmark-icon" focusable="false" aria-hidden="false" role="img" "="" viewBox="0 0 29.536 29.536">

.ShareBar > .PageShare > ul > .hidden-sm.hidden-xs:nth-child(1) > .PSHelp[aria-description="Help"][data-original-title="Help"] > .faq-image-size.ecl-icon--s[aria-hidden="false"]

<svg class="ecl-icon ecl-icon--s faq-image-size" focusable="false" aria-hidden="false" role="img" viewBox="0 0 24 24">
Seriouslink-name

1

element

Links must have discernible text

Ensure links have discernible text

WCAG 2.0 AWCAG 2.4.4WCAG 4.1.2

Why it matters

Causes significant barriers for assistive-technology users. Should be fixed soon.

How to fix

  • Element does not have text that is visible to screen readers
  • aria-label attribute does not exist or is empty
  • aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  • Element has an empty title attribute
  • Element is in tab order and does not have accessible text

Where — sample elements

.ecl-site-footer__link.ecl-link[title=""]

<a href="http://op.europa.eu/en/web/eu-law-in-force" title="" class="ecl-link ecl-link--standalone ecl-site-footer__link">
                 
             </a>

Moderate

4 rules · 20 elements
Moderateregion

17

elements

All page content should be contained by landmarks

Ensure all page content is contained by landmarks

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

  • Some page content is not contained by landmarks

Where — sample elements

.wt-globan--text-long

<span class="wt-globan--text-long">An official website of the European Union</span>

.sr-only-focusable

<a class="sr-only sr-only-focusable SkipLink" href="#MainContent">Skip to main content</a>

.col-md-8

<div class="col-md-8 breadcrumbs-padding">

+ 14 more affected elements

Moderatelandmark-one-main

1

element

Document should have one main landmark

Ensure the document has a main landmark

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

  • Document does not have a main landmark

Where — sample elements

html

<html lang="en" class="js " xml:lang="en" prefix="eli: http://data.europa.eu/eli/ontology#">
Moderatelandmark-unique

1

element

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

Ensure landmarks are unique

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

  • The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable

Where — sample elements

#AffixSidebar

<nav class="Sidebar affix-top" id="AffixSidebar" style="width: 299.5px;">
Moderatepage-has-heading-one

1

element

Page should contain a level-one heading

Ensure that the page, or at least one of its frames contains a level-one heading

Best practice

Why it matters

Creates friction and a degraded experience for some users.

How to fix

  • Page must have a level-one heading

Where — sample elements

html

<html lang="en" class="js " xml:lang="en" prefix="eli: http://data.europa.eu/eli/ontology#">

Needs manual review

3 checks could not be decided automatically and should be verified by a person.

aria-allowed-role1

ARIA role should be appropriate for the element

Ensure role attribute has an appropriate value for the element

aria-prohibited-attr1

Elements must only use permitted ARIA attributes

Ensure ARIA attributes are not prohibited for an element's role

color-contrast4

Elements must meet minimum color contrast ratio thresholds

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

Passed checks51

Automated checks that returned no violations on this page.

  • aria-allowed-attr
  • aria-allowed-role
  • aria-conditional-attr
  • aria-deprecated-role
  • aria-hidden-body
  • aria-hidden-focus
  • aria-prohibited-attr
  • aria-required-attr
  • aria-required-parent
  • aria-roles
  • aria-tab-name
  • aria-valid-attr-value
  • aria-valid-attr
  • autocomplete-valid
  • avoid-inline-spacing
  • button-name

+ 35 more passed checks

Choose Your Path to Compliance

Select the option that works best for you

AI-Powered Fix Instructions

Get detailed, step-by-step instructions with AI assistance to fix issues yourself

  • Code examples and solutions
  • Priority-based guidance
  • Instant access

Full Manual Audit by Expert

Order a comprehensive manual audit from accessibility specialists

  • Expert human review
  • Detailed remediation report
  • Priority support