Skip to content
disclosura

Accessibility

Accessibility statement

An AI notice that some people cannot see, hear or reach does not do its job. Article 50(5) of the AI Act asks that the information “conform to the applicable accessibility requirements”. For a public body’s website those requirements come from Directive (EU) 2016/2102 and the standard EN 301 549, which points to the Web Content Accessibility Guidelines (WCAG).

We test the notice widget and this site against WCAG 2.2 level AA. The W3C states that content that conforms to WCAG 2.2 also conforms to WCAG 2.1, the version behind EN 301 549 V3.2.1. WCAG 2.2 dropped one criterion of WCAG 2.1, 4.1.1 Parsing, as obsolete; the results on this page do not list it. Last test: 13 November 2026.

The notice widget (version 1.5.0)

Tested in three browser engines: Chromium 153, Firefox 155 and WebKit 26.6 (the engine of Safari). 74 checks passed, none failed. Two were skipped because the layout-shift measure exists in Chromium only.

What was checkedWCAG 2.2Result
Automated rules (axe-core: WCAG 2.0, 2.1 and 2.2, levels A and AA) on the card, the bar and the badge, at four screen sizes, open and closedseveral0 violations in 24 runs per engine
The same rules in all 24 languages, chat and content noticeseveral0 violations in 48 runs (Chromium only)
Text contrast1.4.3lowest 5.17:1 over 80 texts (4.5:1 needed)
The sentence is on screen when the page loads and is exposed to assistive technology as a status region, in all 24 languages4.1.3passed, 48 of 48 loads, also at 320 × 256
The language of the notice is marked when it differs from the page3.1.2passed
Keyboard: close, Escape, reopen; focus goes back to the badge2.1.1, 2.4.3passed, 19 of 19 steps
The button names contain their visible words2.5.3passed
A visible focus ring of its own, also on a page that removes all outlines2.4.7passed
In the test, no focused link or button of the page was hidden under the notice (60 elements in Chromium and Firefox, 54 in WebKit, at 320 and 390 px, notice at the bottom). A page element that is itself fixed to the screen is not moved2.4.11passed: 0% covered
Text spacing override: nothing cut off (Irish, German, Croatian, Greek)1.4.12passed, 16 of 16 cases
Reflow and zoom: 200% and 400%, no sideways scrolling, the whole notice on screen1.4.10passed
Target size: every target at least 24 px with a mouse; on touch the close button is 44 × 44 px and the badge 44 px high, the other targets 24 px (touch emulated in Chromium and WebKit)2.5.8passed
Forced colours, the mode behind Windows high contrast (emulated by the browser): a visible edge on card, bar and badge—passed
No movement on load (layout shift 0, measured in Chromium) and no animation—passed
Works when the browser blocks storage, and under a strict content security policy—passed

This site

Tested on 20 of this site’s pages (this page is not one of them) at 1440, 390 and 320 px wide in Chromium, with axe-core and keyboard runs:

  • Text contrast: 0 failures (small grey text is now 6.1:1 on white and 5.7:1 on the tinted background).
  • A “skip to content” link, a visible focus ring on every link and button, and a menu on phones without sideways scrolling.
  • The free check marks each new question for assistive technology (a live region), moves focus to the result when it appears, and says what it needs when JavaScript is off.
  • Motion and smooth scrolling only when the visitor has not asked to reduce motion.

What we have not tested yet

  • A real screen reader (NVDA, JAWS, VoiceOver, TalkBack). We checked what the accessibility tree exposes, not what is spoken.
  • Real phones and tablets, and Safari itself. We used screen sizes in the three engines and touch emulation in Chromium and WebKit only. The WebKit we ran is the engine as built for test tools, not Safari on a Mac or an iPhone.
  • The site pages in Firefox and WebKit, and the Kit delivery page and the PDF record.

So we do not claim full conformance. We claim what the tables show, and we fix what a test or a reader finds.

For your own accessibility statement

If you place the notice on your website, its accessibility is part of your statement. You may use this paragraph, adapted to your site:

Our website shows a notice that some answers or content are produced with artificial intelligence. The notice is a component by Disclosura (version 1.5.0), tested by its maker against WCAG 2.2 level AA on 13 November 2026 in three browser engines with automated and keyboard checks; the results are published at https://disclosura.eu/accessibility/. It has not been tested with a screen reader.

Report a problem

If something in the notice or on this site does not work for you, write to contact@disclosura.eu. Say which page and what happened. We answer by email.