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.

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
Methods and check protocols
Plan accessible products with the development method, assess them with the evaluation method and use the WCAG protocols to record evidence.
Assessment in three layers
Combine automated checks, expert review and testing with disabled users. The website check supports the automated layer and states its limits.
Accessibility specifications
Connect user needs, critical processes, repair tasks and acceptance evidence in a specification. Identify the applicable jurisdiction and contractual requirements.
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
Define the scope
Record the owner, version, domains, user roles, target standard and applicable jurisdiction.
Select pages and processes
Cover templates, functions, states and complete critical processes. Add the random sample specified by the evaluation method.
Check in three layers
Record automated, expert and user checks separately, including criteria that were not tested.
Document barriers
Give each finding reproducible evidence, impact, priority and an owner for repair.
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
- Readers and service owners: start with the guide, then review the evaluation method.
- Designers and developers: use the development method, components and manual checks.
- Assessors: select a protocol, record the tested scope and combine tools with human review.
- Procurers: define user needs and critical processes before requesting a specification.
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.
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
Developing accessible websites
Requirements, design, implementation and acceptance.
Read the development methodAssessing digital resources
Scope, sampling, evidence and conclusions across resource types.
Read the evaluation methodWebsites and web applications
Check protocols for the 55 active WCAG 2.2 A and AA criteria.
Read the web protocolsElectronic documents
Structure, reading order and access to document content.
Read the document protocolsMobile applications
Platform accessibility, interactions and complete tasks.
Read the mobile protocolsDesktop software
Keyboard access, assistive technologies and application states.
Read the desktop protocolsDigital services
Accounts, authentication and end-to-end processes.
Read the service protocolsSelf-service terminals
Physical access, controls and independent task completion.
Read the terminal protocolsClarity and cognitive accessibility
Comprehension checks with people and evidence of task completion.
Read the clarity protocolSources and national profiles
International standards, national experiences and the limits of their application.
Read the sourcesDiffering accessibility needs
Contrast, calm presentation and adjustable settings.
Read the PDF brief
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.