Accessibility statement | Tab Organizer

Our commitment

The provider wants this website to be usable by as many people as possible, including people who navigate by keyboard, use a screen reader, magnify the page, or need reduced motion.

The target is the Web Content Accessibility Guidelines (WCAG) 2.2 at conformance level AA. That target guides how the site is built and tested. This statement describes the current status honestly: it is a self-assessment, not a certification, and it does not claim full conformance.

Scope

This statement covers the public pages of www.taborganizer.app.

It does not cover the interface of the Tab Organizer browser extension, which runs inside your browser and follows its own development cycle, and it does not cover third-party destinations such as the Chrome Web Store listing or external sites reached from a link here. Those are outside the provider's control and have their own accessibility positions.

What is in place today

The following are implemented across the public pages:

Keyboard operation. A skip link at the start of each page moves focus to the main content. Links, buttons, form fields, and other interactive elements are reachable in a logical order.
Visible focus. Interactive elements show a focus indicator when they are reached from the keyboard, including a high-contrast indicator when the operating system is in a forced-colours or high-contrast mode.
Structure for assistive technology. Pages use a single main landmark, headings in a meaningful order, labelled controls, and accessible names for interactive elements. Every page declares its language.
Language of the language chooser. On most pages the chooser is a labelled select whose option elements each carry the lang attribute of the language they lead to, so the option text is announced in that language. On the page shown after the extension is removed, where no preference may be stored, the chooser is a pair of ordinary links; each link carries the same lang attribute and the matching hreflang.
Provider and controller details. The operator name and contact email on these pages are shown as ordinary-looking text, but they are split into small inline pieces in the page markup and are not wrapped in a mailto: link. That is intentional, to make automated harvesting of the address harder. Statute titles are rendered as ordinary text.
Reduced motion. When your browser or operating system asks for reduced motion, animation and transitions are suppressed.
Appearance. A light and a dark appearance can be selected. The control states, in its accessible name, that the choice will be saved on the device for up to one year; the language chooser does the same.
Text alternatives. Product images carry alternative text in the page language.
Zoom and reflow. The main layouts are responsive and reflow at small viewport sizes and at high zoom, so reading a page does not require scrolling it sideways. Data tables are the exception the guidelines themselves make for content that needs two dimensions: the tables in the legal documents keep their table structure and, where they are wider than the viewport, scroll sideways inside a labelled region that can be reached and panned with the keyboard rather than only by pointer or touch.
No interfering third-party layers. The site loads no advertising, no analytics scripts, no consent overlay, no accessibility overlay widget, no embedded video, and no external fonts. Nothing third-party is injected that could change focus order or announcements.

How this has been tested

Accessibility is checked during development rather than once at the end:

Automated checks against the WCAG 2.0, 2.1, and 2.2 A and AA rule sets run in a real browser on the landing page, the documentation home, and the four legal pages including this one, in both English and German. They also verify that each page exposes its language and a single main region.
Layout is checked at desktop, tablet, and mobile viewport sizes.

How that check is enforced, stated exactly. These checks are a separate command that has to be started deliberately, against a built copy of the site. They are not part of the automated gate that runs type checking, linting, and unit tests, and this repository has no continuous-integration pipeline that would run them on every change. So an automated accessibility finding does not by itself block a release: it is a check the provider runs and acts on, not a technical barrier. This statement does not claim otherwise.

Two further limits should be stated plainly. Automated tooling can only detect a portion of accessibility problems; judgement-based criteria such as meaningful sequence, clear link purpose, or the quality of an alternative text are not fully machine-testable. And the routes listed above are a sample of the site, not every page.

Beyond that, the site has not been audited by an external accessibility specialist, has not been tested in a formal usability study with disabled participants, and holds no accessibility certification or seal. Where this statement says something is in place, it refers to the implementation and the checks described here.

Known limitations

The provider is aware of the following:

Not every page is covered by the automated checks described above, so individual pages may contain issues that have not yet been found.
Documentation pages contain longer technical content, tables, and keyboard-shortcut references whose presentation has not been reviewed criterion by criterion against WCAG 2.2 AA.
Screenshots of the product interface are described by alternative text, but the detail visible in a screenshot is not always fully reproduced in text.
Content on linked third-party pages, including the Chrome Web Store listing, is not under the provider's control.

This list is based on the provider's own assessment and is updated as issues are found and fixed.

Feedback and reporting a barrier

If a part of this website is difficult or impossible for you to use, please report it. A short description of the page, what you were trying to do, and the assistive technology, browser, and operating system you use helps most.

The provider aims to answer within a few working days and to fix confirmed barriers as quickly as is reasonably possible. If the fix takes longer, you will be told what is planned and, where one can be offered, how to get the same information or function another way.

Enforcement and escalation

If you are not satisfied with the response, you can pursue the matter under the accessibility or anti-discrimination rules that apply where you live, and you may contact the body responsible for them in your country. Nothing in this statement limits those rights.

Status of this statement

This statement is based on the provider's own assessment of the site as it is published on the effective date shown at the top of this page. It is reviewed when the site changes materially, when a barrier is reported, and otherwise at least once a year.