How to use the methodology

A shared guide connects the tasks of a service owner, content author and developer.

Choose your role and follow the steps in order. At each step one task is solved and a verifiable result appears. The detailed grounds and rules are opened through the links.

For a concise overview of differing needs and settings, read the information reference.

Resource owner

  1. Fix the scope of work. Write down the addresses, versions, sections, and roles that will enter the review. Result: a scope passport according to the evaluation methodology.
  2. Name the critical processes. List the actions without which a person does not receive the service, for example signing in, finding a document, filling in a form, and getting the result. Result: a list of processes and expected outcomes.
  3. Assign three layers of testing. Plan automated testing, manual testing by protocols, and tasks involving people separately. Result: a plan in which the coverage of each layer is visible.
  4. Accept fixes on the basis of evidence. Repeat the original checks on the same version and sample, then check the changed places. Result: a conclusion with the fixed, the remaining, and the new growth points.

Text author

  1. Describe the addressee and the action. State who the text is intended for and what a person should do after reading. Result: one verifiable goal of the text.
  2. Split the action into steps. Leave one action in each item, and name the conditions, the deadline, and the result directly. Result: an instruction with no missing transitions.
  3. Check the essential meaning. Check whether the addressee, the deadlines, the consequences, the possibility to correct the action, and the possibility to cancel it have been preserved. Result: an eased text without loss of significant information. The examples are collected in the appendix "Examples of clear instructions".
  4. Check understanding by action. Ask members of the target audience to choose the next step or to complete a safe task according to the clarity protocol. Result: observations against a success criterion set in advance, without conclusions going beyond the tested tasks and participants.

Developer

  1. Link requirements to components. For each critical process, list the pages, states, and interface elements. Result: a map from requirements to the implementation.
  2. Implement the basic rules. Use semantic structure, keyboard access, managed focus, sufficient contrast, and scaling according to the development methodology. Result: a version ready for testing.
  3. Run the applicable protocols. For each requirement, carry out the test steps and save the observable evidence. Result: cards of growth points, not an overall accessibility percentage.
  4. Repeat the critical scenarios. After the fixes, run the tasks again with the keyboard, with screen access, with magnification, and with selected participants. Result: a check of a specific version with explicitly stated boundaries.

Frequently asked question

Do the requirements for people with visual impairments and for people with ASD contradict each other?

Not necessarily. The main requirements are compatible, but individual preferences may differ. For a blind person, access to a page is provided by programmatically determined structure, which a screen reader or a braille display works with. For a person with low vision, sufficient contrast, text enlargement, and preservation of content and functions when scaling are especially important.

Contrast is not the same as colour saturation or the overall brightness of the screen. In WCAG it is determined through the ratio of the relative luminance of the text and the background. A calm design with a small number of distracting elements is therefore compatible with sufficient contrast. The W3C recommendations on cognitive accessibility also offer a clear structure, free space, and limited distractions, while preserving visible boundaries and landmarks.

Individual needs may differ. Some people are well served by colour combinations with a lower contrast. The explanation of WCAG 2.2 success criterion 1.4.3 "Contrast (Minimum)" explicitly allows user-selectable combinations with a lower contrast, if it is possible to return to the values that meet the criterion. This is a ground for managed settings without loss of information and functions, not a requirement to automatically create all possible themes.

Settings should be tied to the needs of the person, not to a rigid profile based on a diagnosis. A useful reference point for a calm presentation of content: the W3C recommendations on reducing distractions and cognitive accessibility.

The requirements referred to here are technical requirements of a digital resource. Their legal effect is determined by the applicable jurisdiction: WCAG and the W3C documents are not legal instruments on their own, and they become binding only where the applicable law, a contract, a technical specification, or a procurement instrument adopts or refers to them. The Russian materials cited on this page are a labelled national example. Their legal obligation depends on the applicable law or instrument; they may also be used voluntarily or adopted by contract outside Russia.

Brief reference

Download the PDF reference, "Differing needs in digital accessibility". It identifies the provisions of the methodologies that address differing needs and the checking of settings.

Small clarity demonstration

This is a training example of an editorial check. It does not depict the experience of a person with a particular diagnosis and is not the result of a check with participants.

Conditions of the training example: the application is saved as a draft; the details and the attachments are in the "Check" section; errors can be corrected by returning to the required field; the "Check application" button does not send data.

Difficult instruction

To proceed to the next stage of processing the application, perform a verification of the correctness of the previously entered details and the attached materials in the "Check" section. If you find inaccuracies, return to the corresponding field and make the corrections. Selecting the "Check application" button does not lead to sending data.

Clearer instruction

Check the draft of the application.

  1. Open the "Check" section.
  2. Check the details and the attachments.
  3. If you find an error, return to the required field and correct it.

The "Check application" button does not send data.

What to do next?

Show the explanation of the answer

First open the "Check" section. The clearer version names the next step, the place of action, the way to correct an error, and the consequence of the button. It does not add deadlines or guarantees that were not in the original condition.

Open guidance documents of FRC DS

  • "Accessible communication technologies", 2024. Methodological recommendations on clear language, visual support, and alternative and augmentative communication. They are useful to the authors of instructions and forms as a source of Russian-language examples. The separate numerical reference points of the guidance require verification in context and are not universal requirements for all sites.
  • "Accessible and clear in communication", 2025. A teaching and methodological guide on simple and clear language, practical ways of easing information, and checking understanding. It is useful when preparing user tasks and choosing ways of answering beyond an oral retelling.

The links are given for independent study. Both documents are Russian national materials. Their legal obligation depends on the applicable instrument; they may be used voluntarily or adopted by contract in other jurisdictions. Publication of these materials by the centre does not establish approval, support, or endorsement of the "Dostupno" project methodology by FRC DS.