Accessibility Statement
Last updated: August 2026
This website should be usable by as many people as possible — whether they navigate with a mouse, a keyboard, a screen reader, magnification or voice input.
Accessibility here is not an add-on. It sits in the markup, in the keyboard handling and in the colour values themselves.
Standard applied
The benchmark is WCAG 2.1 at conformance level AA — the level referenced by EN 301 549 and, through it, by the German Accessibility Strengthening Act (BFSG).
The public pages are tested automatically against that standard (axe-core, light and dark themes, all four language versions). The check runs as part of the test suite and fails as soon as a violation returns.
Current state
- All content is reachable without a mouse; keyboard focus is visible throughout.
- A skip link bypasses the navigation and goes straight to the main content.
- Text meets at least 4.5:1 contrast in both themes, interface elements at least 3:1.
- Dialogs hold focus, close with Escape and return focus afterwards.
- Moving elements respect the system setting for reduced motion.
- The page language is marked up machine-readably and changes with the language version.
Known limitations
Full accessibility is a goal, not a finished state. Currently known:
- A few very small labels are set in fixed pixel values and therefore do not grow with the text size setting. Browser zoom does affect them.
- The industry marquees are a continuous animation while motion is enabled. With reduced motion they become a scrollable list instead.
- Embedded third-party content (videos, for example) follows the accessibility of that provider, which is outside our control.
- PDF documents generated in the customer area are not fully tagged.
Display preferences — and why there is no overlay here
At the bottom left you will find three settings: text size, motion and contrast. They are stored in your browser only and never sent to a server.
What is deliberately not used is an accessibility overlay (AccessiBe, UserWay, AccessiYes and similar). Such tools inject ARIA attributes into the page at runtime, frequently collide with screen reader settings, and count as proof of conformance in no audit. What creates accessibility is the markup itself — not a layer on top of it.
Your own system and browser settings for text size, contrast and motion are respected regardless, and take precedence.
Reporting a barrier
If you run into something you cannot operate, please write to info@arytechsolutions.com. It helps to include the page address, your operating system and your assistive software.
You will receive a reply within five working days. Where a barrier cannot be removed quickly, we will tell you another way to obtain the information.
Legal context
The German Accessibility Strengthening Act (BFSG) has been in force since 28 June 2025. It obliges providers of certain digital services towards consumers; for micro-enterprises (fewer than 10 employees and no more than €2m annual turnover) it provides an exemption for services. As a sole proprietorship, ARY Tech Solutions falls under that exemption.
This statement therefore does not arise from a legal obligation but from our own standard: anyone implementing accessibility for clients should deliver it on their own website first.
Market surveillance for products and services under the BFSG rests with the Market Surveillance Authority of the Länder for the Accessibility of Products and Services (MLBF) in Magdeburg.
Tell me your idea;I'll build the wow.
A rough sketch is enough to start. You get an honest assessment, a realistic schedule and a fixed price — before a single line is written.
Reply within the same working day