Accessibility statement

Where we stand

“Partly conforms” means: some parts are known not to conform, and some requirements have not been checked yet. We do not claim full conformance with WCAG 2.2 (W3C Recommendation, current version dated 12 December 2024, checked 23 October 2026), or with EN 301 549, the European accessibility standard, whose current version (V3.2.1) points to WCAG 2.1 level AA.

This statement was written on 23 October 2026 for version 5.5.1, from the project's test files and style sheets. It is not the output of a fresh test run, and we do not publish test logs.

What this covers

• The popup opened from the toolbar icon.
• Settings.
• The welcome page shown after installation.
• “Site broken?”, the repair page.
• The malware warning page shown instead of a dangerous site.
• This website, adblock.carbonstealth.eu.

It does not cover the websites you visit. The extension changes what they show, but their own accessibility is the business of their owners.

How it is tested

Automated axe-core run, extension pages

A script starts a real Chromium with the extension loaded and runs axe-core on each page. The rule sets are WCAG 2.0 and 2.1 level A and AA, the WCAG 2.2 level AA rules, and axe's best-practice rules; automated rules cover only part of the success criteria. Any violation fails the run. It is run by hand before a release, not in the automated build, and it needs axe-core installed next to the test tool, otherwise it is skipped.

It runs in both themes, Carbon Stealth (dark) and light, on these pages and states, in the English interface:

• The popup, 320 px wide and 600 px high, with the site row shown.
• The popup with the review card open.
• The popup with the undo button (↶ N) next to Hide element.
• The popup with Connections on this page expanded.
• Settings, the welcome page, and the repair page.
• The malware warning page.

Keyboard

Two browser checks look at the keyboard. With the review card open, nothing underneath it can take focus, and Escape closes the card and returns focus to the content. In Settings, a keyboard-focused switch shows a visible outline. Everything else about keyboard use is covered only by axe's rules, not by a full walk-through of each page.

Two shortcuts work without the mouse: Alt+Shift+U turns blocking on this site on or off, and Alt+Shift+Q pauses or resumes (Ctrl+Shift on a Mac).

Display preferences

The style sheets respond to these system settings:

• Forced colors (Windows high contrast): switches, borders and the warning page use system colors.
• More contrast: secondary text takes the main text color, in the popup, Settings, the welcome page and the warning page.
• Reduced motion: transitions are switched off in the popup and the welcome page.
• Reduced transparency: the popup's glass panels become solid.

These are written into the style sheets. A test run confirms the pages still pass axe, but no test switches these settings on and checks the result.

Fit and languages

Chrome limits a popup to 600 px in height; anything more becomes a scrollbar. A second script loads the popup text of all 73 locale folders (70 languages) and checks that the popup fits, the footer does not clip a label, and the review card stays under half the popup. For Arabic, Hebrew, Persian and Urdu it sets right-to-left direction. The style sheets use logical properties (start and end, not left and right).

This website

Most pages have a “Skip to content” link, a visible focus outline and one main heading; the topic pages (YouTube, cookie banners, support, and this one) also have breadcrumbs and reduced-motion support. The privacy policy page has a focus outline and one main heading, but no skip link, breadcrumbs or reduced-motion rule. The automated test for the site checks structure (one main heading per page), metadata and links, not accessibility rules.

Known limits

• No screen reader test. We have no documented manual test with a screen reader such as NVDA, JAWS, VoiceOver or Orca. The axe run finds missing names and roles; it cannot tell whether the result is pleasant to use.
• This website is not in the axe run. The axe run covers extension pages only. The website pages have no automated WCAG check, and no manual review is on record.
• Only the English interface is audited with axe. Other languages are checked for fit, not for accessibility rules.
• Language and direction are fixed in the markup. The extension pages declare lang="en" and set no text direction. We found no code that adapts either to the interface language, so a screen reader may use the wrong voice, and right-to-left languages are tested only in the popup-fit script, not in a real browser set to Arabic or Hebrew. We have not confirmed how Chrome handles this. This likely does not meet WCAG success criterion 3.1.1 (Language of Page) when the interface is not in English.
• Display preferences are not tested end to end. See above.
• Reduced motion is not set in Settings. Its style sheet has no reduced-motion rule.
• No test with real users with disabilities is on record.
• The “Hide element” picker works by clicking an element on a page with the mouse. We have not documented a keyboard way to choose an element. This likely does not meet WCAG success criterion 2.1.1 (Keyboard) for that feature; Escape cancels the picker.

Report a barrier

Email info@carbonstealth.eu. Tell us the page, what you tried to do, and the assistive technology and browser you use. We read every message and aim to reply; requests about your personal data are answered within one month (see the privacy policy).

What the extension collects, and what it does not: privacy policy.