Digital accessibility is no longer a specialist topic. For public sector institutions in Lithuania and across the European Union, it is a core part of delivering fair, lawful and effective digital services. As accessibility requirements continue to mature in 2025 and 2026, organisations need to understand what is changing, what already applies, and what practical action is required to reduce risk and improve service delivery.
For decision-makers, the key point is simple: accessibility is not only about compliance. It affects whether residents can use essential online services independently, whether procurement decisions stand up to scrutiny, and whether digital platforms meet wider expectations around inclusion, transparency and good administration.
What WCAG is and why it matters
WCAG, or the Web Content Accessibility Guidelines, is the internationally recognised framework for making websites, documents and digital services accessible to people with disabilities. It is developed by the World Wide Web Consortium and is widely used as the benchmark for accessibility compliance in Europe.
For Lithuanian public sector bodies, accessibility obligations are not new. Public websites and mobile applications have already been subject to EU accessibility requirements for several years under the framework established for public sector digital services. What is changing in 2025 and 2026 is the level of attention, enforcement and operational maturity expected from organisations. Accessibility can no longer be treated as a one-off technical exercise or a box-ticking task before launch.
In practice, WCAG matters because it helps ensure that citizens can access information, complete forms, use online portals, read documents and interact with public services regardless of visual, auditory, motor or cognitive impairments. It also improves usability more broadly, benefiting older users, mobile users and people in low-bandwidth or constrained situations.
The four principles of WCAG
WCAG is built around four core principles. These provide a practical way for institutions to assess whether a digital service is genuinely usable by a wide range of people.
- Perceivable — Information and interface components must be presented in ways users can perceive. This means, for example, providing alternative text for meaningful images, captions or transcripts for multimedia, and sufficient colour contrast so text remains readable. For public institutions, this is especially important where websites publish service information, policy documents or emergency notices that must be accessible to everyone.
- Operable — Users must be able to operate the interface using different input methods, including a keyboard alone. Navigation should be clear, focus states visible, and time limits manageable. This is essential for public service portals, booking systems and application forms, where inaccessible controls can prevent citizens from completing important tasks.
- Understandable — Content and interface behaviour should be clear, consistent and predictable. Instructions should be easy to follow, forms should identify errors properly, and navigation patterns should not change unexpectedly. In the public sector, understandable design supports trust and reduces avoidable contact with service teams.
- Robust — Content must work reliably across browsers, devices and assistive technologies such as screen readers. Clean code, proper semantic structure and compatible components are all part of this principle. Robust implementation is particularly important for institutions managing long-term digital platforms that must remain usable as technologies evolve.
What is changing in 2025 and 2026
Greater impact of the European Accessibility Act
The European Accessibility Act becomes applicable from 28 June 2025. Its main effect is to broaden accessibility expectations across a wider range of digital products and services in the EU market. While public sector bodies already have obligations under the public sector accessibility framework, the Act still matters because many institutions procure, integrate or rely on third-party systems, platforms and service providers that may also fall within its scope.
For public sector decision-makers in Lithuania, this means accessibility should be considered not only in internally managed websites and mobile applications, but also in procurement, supplier due diligence and contract management. If a public institution adopts inaccessible software, payment tools, self-service systems or communication platforms, legal and operational risks can quickly follow.
Stronger enforcement expectations
Another important change is not necessarily a new rule, but a higher expectation of evidence. Institutions should be prepared to demonstrate how accessibility has been assessed, how issues are prioritised, and how ongoing monitoring is carried out. Accessibility statements, audit records, remediation plans and governance processes are becoming more important in practice.
This is particularly relevant for municipalities, ministries, agencies and publicly funded bodies that manage large volumes of content across multiple websites or service portals. A reactive approach is unlikely to be sufficient where accessibility complaints, reviews or procurement challenges arise.
What public sector institutions should do now
Preparing for 2026 should focus on practical delivery rather than abstract policy. The most effective organisations treat accessibility as part of service quality, procurement and compliance management.
- Audit existing websites and applications — Start with a structured accessibility review of your public-facing websites, intranets where relevant, mobile applications and key user journeys. Automated testing can help identify common issues, but manual testing is also needed to assess keyboard use, screen reader compatibility and form behaviour. This gives leadership teams a realistic view of risk and remediation effort.
- Prioritise high-impact services — Focus first on services citizens depend on most, such as applications, registrations, payments, appointment systems and information pages for essential services. Accessibility failures in these areas have the greatest impact on users and the highest reputational risk. A prioritised roadmap is more manageable than trying to fix every issue at once.
- Improve procurement requirements — Accessibility should be written into tender documentation, technical specifications and acceptance criteria. Suppliers should be asked to demonstrate how their products meet recognised accessibility standards and how issues will be resolved after launch. This is often the most effective way to prevent future compliance problems.
- Review documents and content workflows — Many accessibility barriers in the public sector come from PDFs, office documents, videos and poorly structured page content rather than from code alone. Content teams need clear guidance on headings, link text, tables, document formats and multimedia alternatives. Without this, even a technically compliant website can still fail users.
- Embed accessibility into governance — Assign responsibility for accessibility across digital, communications, procurement and legal teams. Regular reporting, issue tracking and ownership at management level help ensure accessibility remains part of normal operations. This is especially important for institutions with multiple departments or decentralised publishing processes.
Accessibility, GDPR and wider compliance
Accessibility should also be considered alongside other compliance obligations. Public institutions often collect personal data through forms, portals and online transactions, so accessibility and GDPR need to work together. If privacy notices, consent mechanisms or subject access request processes are not accessible, individuals may be prevented from exercising their rights properly.
There is also a broader governance point. Accessibility supports equal treatment, transparency and non-discrimination, all of which are central to public administration in the EU. A compliant digital service should therefore be secure, accessible, understandable and well documented. Treating these requirements separately often creates duplication and avoidable risk.
Conclusion
For Lithuanian public sector institutions, 2026 should be seen as a deadline for operational readiness rather than the start of accessibility work. WCAG remains the practical foundation for accessible digital services, but success depends on governance, procurement, content quality and ongoing monitoring as much as on technical fixes.
The organisations that respond well will be those that move early, assess their current position honestly and build accessibility into everyday digital delivery. That approach not only supports compliance, but also helps ensure public services are genuinely available to all citizens.