Barriers exist not only in physical spaces but also in the digital world. Difficult-to-use software, a lack of structure, or overly complex language can prevent websites and apps from being accessible to everyone. Applications from public bodies, which include public universities, as well as providers developing software for these institutions, must comply with laws ensuring digital accessibility. This article highlights the basis of all accessibility standards – the Web Content Accessibility Guidelines (WCAG) –, current digital accessibility regulations, and why everyone benefits from barrier-free software.
WCAG: Standards for an Accessible Web
In the early days of the internet, a team led by web inventor Tim Berners-Lee founded the World Wide Web Consortium (W3C) in 1994. With the goal of setting global web standards that benefit everyone, the forum continues to bring together experts from around the world dedicated to developing the web with social responsibility. A major milestone was reached in 1999, four years after the W3C's founding, with the publication of the first version of the Web Content Accessibility Guidelines (WCAG). These criteria include a wide range of recommendations to make web content more accessible. Since their initial release, the WCAG have been expanded several times and, as of December 2024, the current version 2.2 is considered the state of the art.
According to the four guiding principles of the WCAG, accessible software must be perceivable, operable, understandable, and robust:
Perceivable: Beyond simple access, content must be perceivable through more than one sense – for example, via screen readers and image descriptions for people with visual impairments, or through subtitles for those with hearing impairments.
Operable: The structure of a website or application must be simple and organized so that users can navigate and operate the site without a mouse, for instance.
Understandable: Website content and navigation menus must be easy to understand. Some websites also offer an easy-to-read version to make content even more accessible.
Robust: A website or application is only considered accessible if it works independently of specific browsers and remains compatible with assistive technologies used by people with disabilities.
WCAG standards are further divided into three “conformance levels”: basic (A), intermediate (AA), and advanced (AAA). Currently, due to the EU-wide Web Accessibility Directive and corresponding national laws, public sector entities are required to meet all Level AA requirements of WCAG version 2.1. Since these levels are cumulative, this means all requirements from Level A and Level AA must be met.
The Web Accessibility Directive and the European Accessibility Act are important European measures to improve digital accessibility. - Photo: Marco/PexelsLegal Foundations for Digital Accessibility
The “EU Directive on the accessibility of the websites and mobile applications of public sector bodies” defines the criteria a public sector website or app must meet to be considered accessible. Additionally, the EU adopted the EN 301 549 standard in 2021, which sets requirements for the accessibility of ICT products and services. With the European Accessibility Act, digital accessibility also became mandatory for private companies and software providers in the summer of 2025. This ensures that everyone can use digital services – from online banking and travel portals to health services and online shops – without outside help.
Accessibility Statement and Studo Software Accessibility
Several years before software accessibility became a legal requirement for public bodies, Studo began focusing on the accessibility of the Studo Campus App. What started with focus groups involving students with visual impairments was expanded step-by-step. In 2022, the first accessibility audit was conducted, and all documentation was published in an accessibility statement. Since then, Studo products like the Campus App, the Digital Attendance List, and Studo Flow are regularly audited against WCAG standards and frequently put to the test by university accessibility offices.
Accessible design for websites and apps starts right from the planning stage, when the structure and design are being decided. - Photo: Picjumbo.com/PexelsReasons to advocate digital accessibility
In addition to the legal requirements mandating accessible websites and applications in the public sector (and now also in the private sector) there are further reasons for digital accessibility: inclusive design makes platforms easier and more intuitive for everyone to use, thereby improving usability. This means more people are reached – for example, people with disabilities, but also older people – and organisations increase their own reach and the number of potential new users or customers. Ultimately, accessible digital applications promote the participation of all people – an important step towards social responsibility and inclusion on the web.
