Website accessibility for people with disabilities — what a public body needs to know

We adapt websites to WCAG 2.1 AA requirements so that all residents can use them and organisations comply with the law.

Check accessibility

Choose organisation type

  • Klaipėda Cultures Communication Centre
  • Lithuanian Radio and Television Centre (Telecentras)
  • Plungė Cultural Centre
  • “Sava visiems” (public body)
  • Environmental Projects Management Agency (APVA)
  • LIFE Integrated Project “Natura 2000” (Naturalit)
  • Anykščiai Cultural Centre
  • Kaunas City Museum
  • Kaunas District Public Health Bureau
  • Maironis Museum of Lithuanian Literature
  • Utena Adolfas Šapoka Secondary School
  • Klaipėda Chamber of Commerce, Industry and Crafts (KCCI)
  • CPO LT (public body)
  • Vilniaus miesto būstas
  • Šiauliai “Dermė” School
  • UAB “Biržų vandenys”
  • UAB “Mažeikių vandenys”
  • Žiežmariai Cultural Centre
  • Pasvalys Cultural Centre
  • Šiauliai Julius Janonis Secondary School
  • Telšiai Regional Waste Management Centre
  • UAB Molėtų autobusų parkas
  • UAB “Kauno vandenys”
  • “Lithuanian Dance Centre” (public body)
  • Institute of Hygiene

What “accessibility for people with disabilities” means in practice

Website accessibility is not a separate feature or plugin. It is the principle that a website can be used by a person:

  • who cannot see — and uses a screen reader (e.g. NVDA, JAWS, VoiceOver)
  • who has low vision — and uses large text and high contrast
  • who cannot use a mouse — and navigates by keyboard or voice control
  • who has cognitive difficulties — and needs a clear structure and plain text
  • who is older — and finds it harder to read small text or find their way through complex navigation

In Lithuania, about 250 000 people have a registered disability. Public-sector websites are often their only way to reach services — so accessibility is not a “nice extra” but a necessity.

Which standards apply to the Lithuanian public sector

Several laws and standards govern the accessibility of public-sector websites:

WCAG 2.1 AA — the main international standard. It defines specific criteria: colour contrast, keyboard navigation, alternative text for images, form labels, captions for video content and more.

EU Web Accessibility Directive (2016/2102) — requires all EU public-sector websites and mobile apps to meet WCAG 2.1 AA. Lithuania has transposed this directive into national law.

European Accessibility Act (EAA, 2025) — since June 2025 it covers a wider range of services, including e-commerce, banking and transport services.

Law of the Republic of Lithuania on the Social Integration of Persons with Disabilities — sets general accessibility principles for public services.

In practice this means: if your website does not meet WCAG 2.1 AA, it breaches the law.

The most common accessibility problems on public-sector websites

In the audits we have carried out on Lithuanian public-sector websites, these are the most common problems:

Images without alternative text — a screen reader cannot see the image, so a blind user does not know what it shows. This is the most common error — found on 90% of the websites checked.

Insufficient colour contrast — grey text on a light background, low-contrast buttons. WCAG requires a contrast ratio of at least 4.5:1 for normal text.

Broken keyboard navigation — the user cannot use the Tab key to move through menus, forms and buttons. A common cause is non-standard JavaScript elements.

Forms without labels — a screen reader cannot tell the user what to enter in a given field.

PDF documents without structure — public-sector websites often publish PDFs that are simply scanned images — screen readers cannot read them.

Patikrinti svetainės prieinamumą

How to assess your website's accessibility

You can start with simple checks yourself:

  • try navigating the website using only the keyboard (Tab, Enter, Escape) — can you reach every element?
  • increase the browser text size to 200% — does everything remain readable?
  • check colour contrast with free tools (e.g. WebAIM Contrast Checker)
  • turn on a screen reader (Windows: NVDA, Mac: VoiceOver) and try using the website
  • check that every image has alt text

If even one of these tests fails, the website needs accessibility improvements. For a full assessment we recommend a professional WCAG audit that checks all 50+ criteria.

What value accessibility creates for an organisation

Accessibility is not just a legal duty. A properly adapted website:

  • reaches all residents — not only people with disabilities but also older people, mobile users and users on slow connections
  • improves SEO — Google rewards structured, semantically correct content, which overlaps with accessibility requirements
  • reduces legal risk — meeting WCAG 2.1 AA protects you from fines and complaints
  • improves the organisation’s image — it shows that the organisation cares about all residents
  • makes things easier for everyone — clear navigation, large buttons and good contrast benefit every user

Accessibility and good design are not opposites — they reinforce each other.

How we make a website accessible

  1. Accessibility audit

    We check the website against the WCAG 2.1 AA criteria and provide a list of problems ranked by importance, with specific recommendations.

  2. Fixing code and content

    We fix the problems found — from keyboard navigation and contrast to alternative text and form labels.

  3. Testing and statement

    We test with assistive technologies, prepare the accessibility statement and train your team to keep the website accessible.

Not sure whether your website meets accessibility requirements?

We can run a quick accessibility check and tell you where you stand. If all is well, you will know. If not, you will get a clear plan of what to fix.

  • The price is fixed in the contract, we agree the timeline after the first call

Or book a call in the calendar (opens in a new window)

No registration needed. You will see the result straight away. How do we check?

Frequently asked questions

Answers to the most common questions about website accessibility for people with disabilities in the public sector.

Does our website have to meet WCAG standards?

If you are a public-sector body — yes. The EU Web Accessibility Directive and Lithuanian legislation require all public-sector websites to meet WCAG 2.1 AA. This covers municipalities, schools, libraries, museums, hospitals and other state-funded organisations.

Does an accessibility plugin (overlay) solve the problem?

No. Accessibility overlay plugins (e.g. AccessiBe, UserWay) add controls on top of the website but do not fix the real problems in the code. They often create additional problems for screen reader users. WCAG requires the website itself to be accessible, not an extra layer placed on top of it.

How much does making a website accessible cost?

It depends on the size of the website and the number of existing problems. An audit is the first step to understand the scope. Simpler websites (up to 20 pages) are adapted faster; larger ones with a lot of content and forms take more work. We give an exact price after the audit.

Will accessibility work affect the website's design?

Usually only minimally. Good design and accessibility complement each other. The main changes are technical: code structure, alternative text, contrast adjustments. Visually the website can look almost identical but work much better for all users.

How often should accessibility be checked?

We recommend an audit at least once a year or after every major website update. New content (images, documents, videos) should be checked before publishing — this is easy if staff know the basic rules.