Accessibility (WCAG): why does it matter for public-sector websites?
WCAG (from Web Content Accessibility Guidelines) are international web content accessibility guidelines that help ensure that as many people as possible can use digital services, including people with visual, hearing, mobility or cognitive impairments. In practice, this means that a website must be clear, understandable, operable not only by mouse but also by keyboard, and its content must be properly conveyed to assistive technologies, for example screen readers.
For the Lithuanian public sector, accessibility is not just a technical improvement or “good practice”. The websites of municipalities, schools, museums, libraries and other public bodies are often the main source of information for residents: this is where news, service descriptions, documents, registration forms and event calendars are published. If such information is inaccessible to some users, the organisation is effectively restricting access to services and information.
What do the WCAG guidelines define?
The WCAG guidelines are based on four main principles: content must be perceivable, operable, understandable and robust. This means that the user must be able to see or hear the content, use it comfortably on different devices, understand the information provided and rely on the website working with assistive technologies.
The guidelines are divided into three conformance levels: A, AA and AAA. In the public sector, the WCAG 2.1 AA level is most commonly applied, as it is considered a realistic and sufficient standard for most institutional websites and electronic services.
Accessibility requirements for the public sector
Under European Union requirements, public-sector institution websites and mobile apps must meet the set accessibility standards. For Lithuanian institutions, this is relevant not only formally but also in practice: accessibility assessment is increasingly becoming part of website updates, public procurement and digitalisation projects.
It is especially important to understand that accessibility covers more than the main website template. The requirements also apply to documents, forms, buttons, links, search, menu structure, news publishing and even third-party integrations. If, for example, a library publishes PDF documents or a school provides a registration form, these elements must also be accessible.
What makes a website accessible?
- Sufficient text and background contrast. Content must be easy to read in different conditions, including for people with visual impairments or colour perception differences. This is especially important on municipality and school websites, where a lot of important text information is often published.
- Keyboard operation. All main website elements must be accessible without using a mouse. This is relevant for users who, because of motor impairments, use only a keyboard or special control tools.
- Alternative image descriptions. Photographs, icons and other visual elements must have meaningful descriptions if they convey information. For example, a museum exhibition poster or a library event notice must also be understandable to screen reader users.
- Clear heading and content structure. Properly marked headings make it easier to navigate the page and find the needed information more quickly. This matters to all users, but especially to those using assistive technologies.
- Clear forms and error messages. If a user fills in an application, registration or contact form, the system must clearly indicate what needs to be entered and how to correct errors. In the public sector this is especially important, as forms are often related to service requests or the submission of official data.
- Accessible video and audio content. Videos should have subtitles, and audio content should have text alternatives where needed. This helps ensure that information is accessible to a wider range of users.
Accessibility and GDPR: how are they linked?
Although GDPR primarily regulates personal data protection, accessibility and data protection often meet in the same places in practice – in forms, registrations and self-service solutions. If the user cannot understand what data they are providing, what it is used for or how to give consent, there is not only a usability issue but also a compliance issue.
An accessible website helps present privacy information, cookie choices, consent texts and data processing terms more clearly. This is especially important for schools, cultural institutions and municipalities, which process more sensitive or larger volumes of residents’ data.
Most common accessibility problems
Public-sector websites often have recurring errors: insufficient contrast, an inconsistent heading hierarchy, buttons without descriptions, non-adapted PDF documents, unclear links and keyboard navigation that does not work. Such problems may seem minor, but together they make the website much harder to use.
Another common situation is a technically sound website design, but daily content that is inaccessible. For example, if staff upload scanned documents without a text layer or publish images instead of text, accessibility quickly deteriorates even with a good technological foundation.
How can accessibility be ensured in the long term?
Accessibility should not be treated as a one-off project. It must become a continuous part of website maintenance, content creation and technical development. That is why it is important not only to create an accessible website, but also to train the staff who publish news, documents or event information every day.
For public-sector organisations, it is useful to choose solutions in which accessibility requirements are considered already at the design stage: from the design system and content management to forms, documents and integrations. This reduces the risk that major errors will have to be fixed after launch or that expensive additional work will be needed.
Accessibility means a better experience for everyone
Although WCAG is most often associated with people with disabilities, an accessible website is in fact useful to all users. A clearer structure, more understandable texts, more convenient navigation, properly designed forms and better readability improve the overall user experience for every visitor.
For public-sector institutions, this means not only compliance with requirements, but also better resident service. When municipalities, schools, museums or libraries create accessible digital services, they become more open, more reliable and more people-centred.
Would you like to know whether your website meets WCAG requirements? Get a free accessibility and contrast report — Tobalt will check your website and provide specific recommendations to ensure compliance.