Websites need to be usable by more people.
Good accessibility helps people with visual, motor, hearing or cognitive impairments and makes content more understandable overall.
Accessibility
Accessible websites are more accessible, more robust and often better structured.
We support companies in checking websites for accessibility and technically improving them: from contrasts, keyboard operation and semantic structure to forms, components, WordPress templates and BFSG-relevant requirements.
- BFSG relevant since June 28, 2025
- WCAG technical test basis
- A11Y Connect UX, SEO and participation
overview
Accessibility is more than just a legal requirement.
Since June 28, 2025, the Accessibility Strengthening Act in Germany has been fully applicable to products and services that fall within its scope. Digital services such as online shops, booking routes, customer portals or comparable consumer offers are particularly relevant for websites. Even if a website does not directly fall under the BFSG, accessibility is a quality feature for digital offerings and can be technical Search Engine Optimization support.
Many barriers arise in the code.
Missing semantics, weak contrasts, unclear focus states, inoperable menus or form errors can be technically improved.
We provide technical implementation, not legal advice.
We check and optimize the website level. Whether and to what extent a specific obligation exists should be legally examined if necessary.
Services
What we do about accessibility for websites.
The start can be an audit, a targeted examination of individual page types or the technical implementation of prioritized measures.
Accessibility audit
We check typical barriers in layout, navigation, text structure, media, forms, components and interactive elements.
BFSG and WCAG examination
We examine technical requirements pragmatically and use standards such as WCAG as a basis for concrete measures.
Technical optimization
Contrasts, focus states, keyboard operation, ARIA attributes, semantics, labels and error states are improved in the frontend.
WordPress templates
Themes, Gutenberg blocks, navigation, forms and recurring components can be specifically made more accessible.
Partial areas instead of complete renovation
A prioritized approach often makes sense: checkout, contact form, landing pages, navigation or central templates first.
Documentation and roadmap
We record findings, implemented measures and open points in such a way that teams and service providers can continue to work with them.
Test levels
Accessibility arises from the interaction of design, content and technology.
A single tool is not enough. What is crucial is whether real usage situations are taken into account and technical problems are thoroughly resolved.
Audit
Make barriers visible
Automated checks help you get started, but must be supplemented by manual checks of the keyboard, focus, structure and usability.
- contrast
- semantics
- focus
Content
Keep structure understandable
Headings, link texts, alternative texts, error messages and clear language make content easier to understand for people and machines.
- Headings
- Alt texts
- Link texts
Service
Make interactions achievable
Menus, sliders, tabs, forms, filters and cookie banners must remain understandable and usable even without a mouse.
- Keyboard
- focus
- Forms
Front end
Solidly implement design systems
Recurring components need stable contrasts, clearly visible states and robust responsive rules.
- Buttons
- Cards
- Modules
Sequence
This is how we approach accessibility pragmatically.
Not every website needs a completely new build immediately. It is important to clearly prioritize according to risk, usage and effort.
- 01
Clarify goal and scope
We define which page types, functions or user paths should be checked and whether BFSG questions play a role.
- 02
Analyze website
Automated checks, manual checks, keyboard tests and technical triage show the most important barriers.
- 03
Prioritize actions
Findings are sorted according to impact, effort, user relevance and technical dependency.
- 04
Implement technically
We specifically adapt templates, CSS, JavaScript, components, forms and editorial structures.
Deepening
Why accessibility also makes sense for websites without an immediate obligation.
Accessibility is often only discussed through the BFSG. In practice, however, it's about digital quality: people should be able to find, understand and use content.
The BFSG is a trigger, not the only reason.
The Accessibility Strengthening Act implements the European Accessibility Act in Germany and affects certain products and services. Offers through which consumers use, order, book or conclude contracts with digital services are particularly relevant for websites.
Not every company website is automatically affected to the same extent. Nevertheless, it makes sense to make central pages and functions more accessible. Anyone who makes contact forms, career areas, offer pages or shops more accessible reduces hurdles for real users.
Accessibility and SEO share common ground.
Structured headings, descriptive link texts, alternative texts, meaningful form labels, robust mobile display and fast interactions not only help assistive technologies. They also improve the structure that search engines and AI systems can evaluate.
That's why we don't look at accessibility in isolation. It belongs in relaunches Web design & conception, with existing systems often in a technical test like a WordPress inspection or targeted front-end optimization.
Own software
Accessibility Helper as an additional component.
The Accessibility Helper is not the focus of our accessibility service, but it shows that we also practically translate the topic into our own software.
A free helper from the Bajorat Media Cockpit.
The Accessibility Helper is a tool developed by Bajorat Media that can be integrated into websites as a script. Visitors can use it to adjust contrasts, font sizes, readability, highlighting and animation behavior, among other things.
The tool is available free of charge via the Bajorat Media Cockpit. It does not replace technically sound accessibility, but can be useful as a supplementary convenience function and shows that we do not just view accessibility in theory.
To ensure a reliable result, we always check the website itself first: semantics, usability, contrasts, forms and components must work well even without an additional widget.
Entry
Accessibility can start as an audit, implementation or support.
The appropriate scope depends on whether an existing website is to be checked, a relaunch is to be supported or a specific user path is to be improved.
Accessibility audit
For existing websites where the most important barriers and risks should be visible first.
- Checking central page types
- Prioritized findings
- Action roadmap
Technical optimization
For websites where known barriers in templates, components or forms need to be resolved.
- Frontend adjustments
- Keyboard and focus states
- Form and component QA
Relaunch support
For new websites where accessibility should be incorporated directly into the conception, design system and implementation.
- UX and design review
- Component rules
- Quality assurance before launch
competence
Accessibility benefits from technical website experience.
Many accessibility problems arise in templates, components, plugins and editorial workflows. That's exactly where we start.
We know websites, WordPress, front-end implementation and typical technical legacy problems from many projects.
We prioritize measures based on real impact rather than purely tool scores.
With the Accessibility Helper, we have developed our own tool that can give website operators additional options.
FAQ
Frequently asked questions about accessibility.
Briefly explained: BFSG, audit, technical implementation and accessibility helper.
Since when has the Accessibility Strengthening Act been in effect?
The BFSG has been in force in Germany since it came into full force on June 28, 2025. It does not automatically affect every website in the same way, but rather certain products and services within the legal scope of application.
Is an accessibility widget alone sufficient?
No. A widget or helper can offer additional operating options, but does not replace technically sound accessibility. Semantics, contrasts, keyboard operation, forms and content must work on the website itself.
Can existing websites be made more accessible later?
Yes, there is often a lot that can be improved. Depending on the technical basis, targeted adjustments to templates, CSS, JavaScript and forms are sufficient. For very old systems, a relaunch can be more economical.
Does accessibility impact SEO?
Indirectly, yes. Clear structure, descriptive link texts, alternative texts, mobile usability and understandable content help users, assistive technologies and often search engine optimization.
Check accessibility
Leave us your website
more accessible and more robust make.
We examine key barriers, prioritize measures and implement technical improvements pragmatically.
