Business software is used by people with different abilities, devices and working conditions. Accessibility according to the Web Content Accessibility Guidelines is therefore a quality requirement for the entire usage process, not just for individual colours or texts.
Understand the legal framework and references
Austria’s Accessibility Act (Barrierefreiheitsgesetz, BaFG), which implements the European Accessibility Act, has applied since 28 June 2025, mainly to certain consumer products and services. Internal business software usually does not fall within its scope. For public bodies, the Web Accessibility Act (Web-Zugänglichkeits-Gesetz, WZG) is particularly relevant.
EN 301 549 and WCAG 2.1 at conformance level AA often serve as a reference. WCAG 2.2 AA is a sensible target for new projects but does not replace checking the law that applies in each case. This article does not constitute legal advice.
Use WCAG as a working basis
WCAG organises requirements under the principles perceivable, operable, understandable and robust. For a project, concrete acceptance criteria for navigation, forms, error messages, media and dynamic content are derived from them.
An early review of the target group and the most important business processes prevents only the home page from being considered. Barriers in login, search or completing a transaction often have the greatest practical impact.
Consider keyboard and assistive technologies
All functions must be reachable without a mouse and operable in a sensible order. Focus states, dialogs, tables and complex components need clear interaction so that users can follow the current state.
Semantic HTML and correctly used ARIA attributes support screen readers and other assistive tools. ARIA should not mask missing semantics but be used deliberately and tested.
Design content and forms to be understandable
Good contrast, scalable text, meaningful headings and clear link texts help many user groups. Information must not be conveyed solely through colour, position or a symbol.
Forms need labelled fields, clear required-field indications, helpful error messages and a way to correct input. Complex business forms in particular should be tested with real workflows and different input methods.
Test accessibility continuously
Automated checks find recurring technical problems but do not replace manual keyboard testing or testing with assistive technologies. In addition, affected users should be involved in evaluating key workflows.
Accessibility belongs in the design system, code review, regression tests and acceptance. An accessibility statement listing known limitations and planned improvements makes the current status transparent.
Facing a similar problem?
We analyse your starting point and show you a pragmatic next step.
Book an initial consultation