Accessibility statement

What we aim for

Brokaro should be usable if you rely on a screen reader, work by keyboard alone, magnify the page heavily, or perceive colour differently. The benchmark we work to is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the same level the European standard EN 301 549 points at in its currently harmonised edition.

That is a target, not a certificate. This site has not been audited externally and there is no third-party conformance assessment. What follows is the state of our own implementation and our own tests — including where both fall short.

The legal position

The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025, transposed in Germany as the Barrierefreiheitsstärkungsgesetz (BFSG) and in Austria as the Barrierefreiheitsgesetz (BaFG). It does not cover the web as such, but a closed list of products and services. For a site like this one only a single category is in play: "e-commerce services" — services provided at a distance, by electronic means and at the individual request of a consumer with a view to concluding a consumer contract.

Whether this site falls inside that scope depends on two questions. Both turn on the operator, so no blanket answer is claimed here:

1. 1Is a contract concluded here? Not on Brokaro: we compare and we link, and the brokerage agreement is formed between you and the broker. Purely informational and comparative offerings that conclude no contract of their own are, on the prevailing reading, outside the scope. That reading is not settled, and adding functions tied to contract formation would move the line.
2. 2Does the micro-enterprise exemption apply? An enterprise employing fewer than ten people with either an annual turnover of at most EUR 2 million or an annual balance sheet total of at most EUR 2 million is exempt, as a service provider, from the accessibility requirements (Art. 4(5) of the Directive, § 3(3) BFSG). The exemption does not extend to products.

In Switzerland the disability equality act binds public bodies only. Private providers are subject to a prohibition on discrimination but not to a general WCAG obligation; an extension to private digital services is in the legislative process, not in force.

Note to the operator: this statement is published regardless of whether it is legally

required. Whether it is required depends on company size, seat and the actual shape of the

service, and belongs in front of a lawyer. If the service does fall under the BFSG, Annex 3

No. 1 additionally requires a description of how the service meets the requirements and the name

of the competent market surveillance authority.

What is implemented

Everything below is verifiable in the source and was checked individually before this statement was published:

• Page structure. Every page carries the header, nav, main and footer landmarks and exactly one h1. Editorial prose can technically only produce headings from h2 downwards.
• Skip link. The first Tab press on any page lands on "Skip to content", which moves straight into the main landmark.
• Keyboard operation. Controls are buttons, links or form fields, so they are keyboard operable without extra work. Focus is always visible: a two-pixel ring with offset that clears 3:1 contrast against every surface in both colour schemes.
• Dialogs. The mobile menu, the filter sheet on narrow screens and the search overlay are real dialogs (role="dialog", aria-modal). Tab is trapped inside them, Escape closes them, and focus returns to whatever opened them.
• Search. The search field is a combobox wired to its result list. Arrow keys move through the results and aria-activedescendant reports which one is active.
• Buttons without text. Icon-only buttons — close, menu, search, pagination, remove — carry an aria-label, and the graphic inside them is hidden from screen readers.
• Tables. Every header cell in the project carries a scope attribute. The broker table also has a caption that only screen readers read out.
• Ratings are text. Stars and score dials expose their value as text — "4.6 out of 5 stars" and "4.6 out of 5" respectively; the graphic itself is hidden.
• Forms. Every input has an associated label. Help text is tied to the field through aria-describedby, and filter groups are fieldset with legend.
• Contrast. Body text clears 4.5:1 on every background surface in both colour schemes; the lowest ratio measured is 4.55:1. The vivid signal colours are used as graphics only, because as text on a light surface they would land at around 2:1.
• Motion. prefers-reduced-motion is honoured globally: animations, transitions and smooth scrolling are switched off.
• Images. Every image either has a text alternative or is explicitly marked decorative. Where a monogram stands in for a missing broker logo, the tile is decorative and the broker's name sits next to it as text.
• Wide tables scroll inside their own container; the page itself never scrolls sideways, down to a 375-pixel viewport.

The points about headings, text alternatives, the skip link and sideways-scrolling tables are checked automatically on every test run and fail that run if they break.

What is still missing

This list is deliberately complete rather than flattering:

1. 1No testing with real assistive technology. The implementation has not been worked through with NVDA, JAWS, VoiceOver or TalkBack. Automated checks catch structural faults, not every confusing announcement.
2. 2No external audit and no systematic pass over all WCAG 2.1 AA success criteria. A number of them — magnification to 200%, reflow at 320 pixels, focus order across whole pages — have not been tested rigorously.
3. 3Sideways-scrolling tables are not focusable regions. Someone working by keyboard alone can, in some browsers, only move them by tabbing to a link inside them.
4. 4~~The document language is fixed to German.~~ Fixed on 20 September 2026: every page now declares its language and writing direction on the document itself — the Arabic version as <html lang="ar" dir="rtl">, the Portuguese one as lang="pt-PT", and so on for all sixteen languages.
5. 5Filter results are not announced. In the broker directory a filter change rewrites the address without reporting the new result count through a live region. The guides and deals listings already do this.
6. 6Form errors appear as a single summary message. Individual fields are not marked invalid and are not linked to that message.
7. 7~~The three theme buttons are labelled in English.~~ Fixed on 30 August 2026: the German version now reads „Hell", „System" and „Dunkel".
8. 8Linked broker websites are outside our control. Their accessibility is the responsibility of the provider in question.

If you hit a barrier that is not on this list, that is a fault in the list — please tell us.

Reporting a barrier

Write to us through the contact form. Useful, though not required:

• the address of the page affected,
• what you were trying to do and where it broke down,
• browser, operating system and, if relevant, the assistive technology you were using.

We reply as soon as we can and tell you whether and by when we can remove the barrier. Where a fix is not possible quickly, we will give you another route to the information you were after.

Enforcement

If our answer does not satisfy you, or none arrives, you can escalate to the competent body:

Which body that is follows from the operator's seat and from the classification above; it is deliberately not guessed here. We will name it here together with the legal notice. In Germany the federal states jointly supervise compliance with the BFSG through a market surveillance authority established for that purpose.

Status of this statement

Prepared on 30 August 2026, on the basis of a self-assessment of this project's source code and automated tests.