From 28.06.2025, the EU's Guideline (EU) 2019/882 - even in the private sector. For example, in the field of e-commerce. Who, for example, a web shop is affected. Germany has adopted this directive the ‘Freedom Reinforcement Act’ transferred to national law. With the ‘Regulation on Accessibility Reinforcement Act’ the implementation is regulated. §3 para. 2 names the Website of the Federal Centre for Accessibility as a source for standards to be observed according to the current state of the art. At present (Jan 2023) the European standard is the Standard EN 301 549 only to read between the lines, but will in Videos , Meetings and Lectures as the norm to be implemented. Standard EN 301 549 BITV and WCAG as a regulation to be implemented or Directive. BITV? WCAG? Doesn't the browser provide accessibility? Or the technical application? What exactly does it matter? What procedures are offered?
Closer viewed
Accessibility is about providing more than one screen reader with appropriate texts, so that the page is read correctly in the browser. It is true that, especially in web applications, the Focus on visual impairments, but disabilities are diverse. Someone with a motor Handicap looks excellent, but does not hit the button, does not get the wizard gesture, etc. Looking at BITV in the currently valid version 2.0, you will be faced with a question catalog with almost 100 Points. The amount of questions alone makes clear: Accessibility is probably not just a question by chance. The question catalogue is structured in terms of tasks. It focuses on how to obtain information must be so that people with disabilities can use them. The questions are well documented, explain why something is a problem and show ways of solving it. Other technically detachable questions (e.g. abbreviated texts: “Geb.-Dat.” display – “Geburtsdatum” read in) among other things, why it is not a good idea to transport information only about colors, when Information in sign language and when must be present in “simplified language” and much more.
An example (WCAG: 1.4.2 Use of colors):
If you want to visually show whether a recycle bin is empty or not, it does not help it green (empty) or red (not empty) because a person with red-green weakness cannot distinguish this. It makes sense to integrate accessibility already where (mainly normal-sighted) users wish a coloured recycle bin.
In the further course of the article, the point BITV/WCAG with what to consider everything (colors, sizes, can be operated without mouse, texts are understandable, etc.) and the point Best practice How to can arise in order to meet the “what” appropriately.
BITV/WCAG
BITV (barrier-free information technology regulation)
WCAG (Web Content Accessibility Guidelines) For quick classification: BITV is a regulation to which public administrations must adhere. It is based on the rules of WCAG. WCAG are guidelines set up by w3c (World Wide Web Consortium) which provide access to Information for people with disabilities should be improved.
WCAG
WCAG systematically lists problem zones, explains why this is a problem and gives suggestions for solutions with. The problem areas (recognisable/perceptible, operable, understandable, robust) are further broken down. So the above example (colored recycle bin) can be found below: 1. recognizable/perceivable
1.4. distinguishable
1.4.1 Use of colors
The individual points are weighted from A to AAA. A – absolute minimum
AA – expressly recommended
AAA – additional recommendations for specific user groups WCAG looks at individual pages - not entire applications. One page is Level-A, Level-AA or Level-AAA-compliant. One page meets Level A when all Level A points, Level AA when all Level A and all Level A points and Level AAA if all Level A, all Level AA and all Level AA points were met.
BITV
BITV consists of a question catalogue with approx. 100 questions based on the WCAG points. BITV also looks at individual pages and the questions can be “fulfilled”, “here fulfilled”, “partly ‘not fulfilled’ or ‘not fulfilled’ shall be answered. For the assessment of the conformity of individual requirements, only the first two are considered to be compliant. Requirements with multiple test steps are compliant if all substeps are compliant.
Tool list (Browser plugins, screen reader, validators, bookmarklets)
Best practice
For a first look into your own web presence, provide browser tools (developer tools, plugins) first indication points and are later suitable for fast rudimentary tests. The installation of a free screenreaders is revealing when you close your eyes and try only with its help navigate through your own application – or if the screen reader ceases to speak, Abbreviations such as ‘Geb.-Dat’, etc. For a systematic review for the purpose of certification, BITV test in connection with an external test, e.g. via one of the BITV test sites a good choice. The BITV test offers Possibility of self-assessment and is also suitable for its informative, structured form as well as Entering the topic. External exams are also recommended when you are actually familiar with web technologies. Self Manufacturers of web components use external testing and thereby improve their products. Example be here the Fa. Vaadin called their products Annual externally and through Improvements reports on accessibility. Tools such as browsers and browser plugins for evaluating accessibility are helpful. Nevertheless, Be careful. If a Chrome/Lighthouse shows a 100% barrier-freeness, the appearance is likely to be crumbling. Perhaps there are missing parts that should actually be visible from a specific zoom stage no longer are. Suddenly, a part of a table is missing because its container has its contents via CSS Visibility: hidden cut off. Even UI testing with tools such as selenium are only suitable to a limited extent. They need a definition of how something barrier-free can be seen in the browser. This must be defined in advance so that deviations can be identified and reported. Thus, only the application can be examined regularly by hand. Best especially before Background of accessibility. Only then you test different zoom levels, use the screen reader etc.
The following questions can help to find suitable ways:
Should the application only be internal or only externally examined? Or both?
Should the investigation be carried out regularly?
Should tools (screen readers, browser plugins) be purchased and installed?
Who is to install the tools?
Who should be sensitized for the topic?
From which group of people come wishes, how colored paper baskets?
How flexible is this group of people with regard to changes in their wishes?
Who should be trained? Development teams? Design teams?
Do you want to be regularly trained/refreshed?
Should principles and rules be established?
Should accessibility be an integral part of the development process?
Do you want control bodies?
Who would be suitable for this (who knows about accessibility/WCAG/BITV)?
Should deliveries be prevented if a certain degree of accessibility has not been achieved?
How high is the risk? Threatened complaints?
What is the degree of accessibility?
Not sure if your platform is already barrier-free?
As a specialist in the field of digitalization, we are happy to assist you in the evaluation and optimization of your application regarding accessibility.
Markus has many years of experience in full-stack development. In addition to his preference for backend development, he is interested in everything new and innovative. At actidoo he deals with fast database access and other server-side topics as well as the possibilities of modern browsers. Before that, he helped to implement the accessibility of various web applications for public administrations.
