A public assessment cycle

This example follows one website through a baseline version, an assessment report, a repair specification, a changed version and repeat assessments. It shows how evidence can support a repair decision without reducing accessibility to a single score.

A user encounters a barrier, a developer repairs the control and the user repeats the task.

Assessment timeline

  1. Version 1 of the website

    2026-09-14

  2. Assessment report 1: version 1

  3. Repair specification 1

  4. Version 2 after repairs

    2026-09-14

  5. Assessment report 2: version 2

  6. Comparison of reports 1 and 2

  7. Repair specification 2

  8. Version 3 after repairs

    2026-09-15

  9. Assessment report 3: version 3

  10. Comparison of reports 2 and 3

Follow the sequence

Open each available version or artefact from the timeline below. Compare the tested scope before comparing counts. A lower number of findings may reflect a repair, a changed sample or a test that did not run, so the execution status and evidence matter.

Language of historical artefacts

Historical websites, reports, specifications and comparisons may be in Russian. Links are labelled with the original language. Compare the recorded versions and scope before drawing conclusions about changes.

Apply the method

Use the evaluation method to define scope and evidence. Turn confirmed findings into tasks with the development method, then repeat the same checks and record any remaining manual work.

Language of the report text

The reports linked on this page are historical documents. Their text keeps the original language, Russian, and is marked as Russian. Everything around it, the navigation of the site, the headings, the explanation and the controls of this page, is English.

Report text: Russian (original language).