2026-10-21 · 10 min read · Demand guide # Assessment Progress Disclosure: Page Count, Range, or No Number? Show an exact step count only when every respondent follows a fixed path with a known denominator. For branched assessments, show a stage label or an honest approximate range, or omit numeric progress. A progress bar that jumps backward, stalls, or promises eight steps while routing someone through thirteen is worse than no bar because it gives false information. ## Definition Assessment progress disclosure is the text and visual feedback that tells a respondent where they are in a multi-step flow and what remains. It may be an exact step count, a percentage, a stage label, an approximate range, or a non-numeric completion cue. ## Method and evidence On October 21, 2026, we rechecked W3C multi-page-form guidance and involve.me's current progress, page-navigation, and answer-routing documentation. We mapped four synthetic path shapes and ran ten deterministic disclosure tests. The path lengths are illustrative; no completion-rate, conversion-lift, or accessibility-conformance claim is made. Evidence type: Four-pattern disclosure matrix, versioned path contract, worked 7–9-step branch, and ten deterministic progress tests. See the [publication methodology](https://best-assessment-tool.com/methodology) and [correction path](https://best-assessment-tool.com/corrections). ## Choose among four disclosure patterns W3C says the first step should explain how many steps follow when possible and each step should communicate progress. Its example uses an approximate number when later pages depend on earlier input. That is a disclosure rule, not a reason to invent an exact denominator. Path shapeRecommended disclosureExampleMain riskFixed, every step requiredExact countStep 3 of 9Omitting hidden required stepsFixed with optional sectionsCount plus optional labelStep 3 of 9; one optional sectionTreating optional work as requiredBranched with bounded lengthHonest range or stageAbout 5–8 steps; ScoringProgress that jumps as the branch changesHighly dynamicStage label or no numberQuestions → Result → Next stepFalse precision Sources: [W3C multi-page forms](https://www.w3.org/WAI/tutorials/forms/multi-page/) · [involve.me progress and navigation](https://help.involve.me/en/articles/3619241-show-or-hide-the-page-progress-bar-and-page-navigation-buttons) ## Count the full respondent journey Define one visible step as one meaningful respondent decision or review screen. Do not count editor pages mechanically if several pages auto-advance or one page contains multiple decisions. Include a required contact gate, consent choice, review screen, and result transition in the model. Exclude background calculations and internal workflow actions. Record the path version, possible minimum and maximum visible steps, required stages, optional stages, branching rule, and the text shown to the respondent. This turns a design preference into a testable disclosure contract. Sources: [Assessment Answer Routing](https://best-assessment-tool.com/blog/assessment-answer-routing) · [Assessment Drop-Off Audit](https://best-assessment-tool.com/blog/assessment-drop-off) ## Worked example: two paths, one honest range A readiness assessment begins with two shared questions. A respondent who selects already implemented receives three evidence questions; someone who selects planning receives five preparation questions. Both then see one contact step and one result page. The first path has seven visible steps and the second has nine. Do not label the opening Step 1 of 7 for both people. Use About 7–9 steps, a three-stage label such as Context → Details → Result, or no numeric bar. If the platform recalculates the denominator after the branch is known, test both paths and confirm the accessible text changes with the visual. PathSharedBranchContactResultTotalAlready implemented23 evidence questions117Planning25 preparation questions119 ## Apply the current platform boundary accurately involve.me currently lets publishers show or hide the progress bar, page numbers, and page-navigation buttons. Its documentation recommends turning both progress and navigation off for routing branches because participants may not visit every page and larger transitions can be misleading. Answer Routing sends people to another page or outcome according to an answer or condition. A route that restarts the funnel deletes collected answers. That behavior belongs in the route test and respondent instructions; it must not be hidden behind a progress promise. Sources: [involve.me funnel navigation](https://help.involve.me/en/articles/3619241-show-or-hide-the-page-progress-bar-and-page-navigation-buttons) · [involve.me Answer Routing](https://help.involve.me/en/articles/1864380-using-answer-routing) ## Run ten deterministic tests Record the path version, displayed disclosure, expected remaining work, observed steps, accessibility result, and pass or fail. Repeat the matrix after any route or required-step change. - Complete the shortest path and compare every displayed count with the actual remaining steps. - Complete the longest path and repeat the comparison. - Trigger each optional section and verify the disclosure remains truthful. - Use the browser Back action and confirm progress and saved answers remain coherent. - Trigger validation errors and confirm the count does not advance. - Zoom to 200% and test a narrow mobile viewport. - Navigate with keyboard and a screen reader; confirm progress is communicated in text. - Resume a partial attempt and verify the restored step and progress state. - Restart the route and verify the documented deletion behavior is clear and intentional. - Change one route, rerun every path, and version the disclosure contract. ## Use stage labels when the denominator is unstable Stage labels such as Context, Evidence, Contact, and Result can orient a respondent without claiming an exact path length. Mark the current stage in text and structure, preserve a logical heading order, and avoid using color alone for completed and current states. A shorter-looking flow is not automatically better. Compare observed starts, completions, validation errors, and result quality by path before removing necessary evidence or changing the disclosure. Sources: [Accessible Online Assessment](https://best-assessment-tool.com/blog/accessible-online-assessment) · [How Many Questions Should an Assessment Have?](https://best-assessment-tool.com/blog/assessment-question-count) ## Practical next step Copy the framework or checklist into a draft, run every stated test case, and record the observed result before publishing. Recheck changing product capabilities and plan limits against the linked vendor page. --- Canonical: https://best-assessment-tool.com/blog/assessment-progress-disclosure