Dostupno: practical accessibility methods

Dostupno is a collection of methods, protocols, examples and tools for making digital services easier to use by people with different access needs. Web Content Accessibility Guidelines (WCAG 2.2) at levels A and AA form the common technical core. National standards and procurement practices are presented as profiles that can be applied where relevant.

The project develops a reproducible assessment procedure: another assessor should be able to follow the same scope, collect comparable evidence and explain the result. Web and web-application methods have passed internal trials. Protocols for other resource types have been issued, but their trials are not complete.

Automated analysis, expert review and keyboard testing examine the same interface.

Project at a glance

  • 55WCAG 2.2 criteria at levels A and AA
  • 11methodology documents and reference brief
  • 3assessment layers: automated, expert and user testing
  • 0.3.8edition, open for discussion and trial

What the project offers

Principles

Open methods
The texts, protocols and decision rules are available for reading and discussion.
Automation supports people
Tools identify only some barriers. Expert checks and tasks with disabled users remain necessary.
No single accessibility percentage
Report evidence, coverage and limitations rather than collapsing different checks into one score.
Different access needs considered together
Sufficient contrast can coexist with calm presentation. Semantic structure, text alternatives and adjustable settings support different and combined needs. See the reference brief.
Standards and project rules distinguished
National requirements apply within their own scope. Additional project practices are identified separately from normative requirements.
Conclusions follow the evidence
One confirmed failure can disprove a claim of full conformance; one successful run cannot establish conformance of an entire service.

How assessment works

  1. Define the scope

    Record the owner, version, domains, user roles, target standard and applicable jurisdiction.

  2. Select pages and processes

    Cover templates, functions, states and complete critical processes. Add the random sample specified by the evaluation method.

  3. Check in three layers

    Record automated, expert and user checks separately, including criteria that were not tested.

  4. Document barriers

    Give each finding reproducible evidence, impact, priority and an owner for repair.

  5. Conclude and check again

    State the sample and limits of the conclusion. After repair, recheck the original cases and the changed scope.

Choose a path

Learn through examples

The demonstrations show several interface barriers. They are learning aids and do not reproduce a disabled person's full experience. The assessment examples and assessment cycle show how evidence can lead to repairs and a repeat check. Historical report payloads may remain in their original language and are labelled on the relevant pages.

Explore the demonstrations

Use the tools with care

The website check can find reproducible signals on a public sample. It cannot certify a whole service or replace keyboard checks, assistive technology checks and sessions with disabled users. Read the check limits before submitting a site.

A concise English reference to differing accessibility needs is available as a PDF brief.

Documents

Status and next steps

The methods are drafts for discussion and trial, not approved standards or certification. The website and web-application section has passed internal trials; trials of the other resource protocols remain incomplete. A user pilot must provide evidence from real participants before claims about practical usability can be made. See the readiness table for the scope of each section.

About the project

Read about the project's scope, evidence and national profiles on the project page. Comments on the methods and contributions to their practical evaluation are welcome through the contact links below.

About the project