{ "test_case_id": "A11Y-COLOR-005", "title": "Runtime forced-colours toggle", "category": "forced_colors", "procedure_version": "2026.08.27-rc.9", "rule_type": "atomic", "wcag_criteria": [ "1.4.1", "1.4.3", "1.4.11", "2.4.7" ], "level": "AA", "risk": "medium", "risk_basis": "Checks runtime forced-colours toggle without relying on browser-only CSS emulation. People most likely affected: people with low vision or colour-perception differences who use system contrast themes. Information, boundaries, focus, selection or status may disappear or become indistinguishable. In the recorded windows-forced-colors-edge environment, inspect selected, focused, disabled, error and chart states in the named system themes; removed backgrounds and substituted colours can erase boundaries or state differences.", "review_status": "draft", "reviewed_at": "", "review_note": "Template content is subject to a hash-bound internal consistency review. Formal assessment claims require competent execution, current evidence and the applicable legal, participant and organisational authority.", "method_label": "Forced-colours check", "tester_level": "General QA tester", "estimated_duration": "Typically 40–58 minutes for the stated single-target assumptions; use the component breakdown when estimating a real sample.", "execution_class": "manual_with_automation_support", "automation_support": "supporting_evidence_only", "simulation_policy": "simulation_may_support_but_not_replace_manual_execution", "plain_summary": "Checks runtime forced-colours toggle without relying on browser-only CSS emulation.", "objective": "Verify runtime forced-colours toggle without relying on browser-only CSS emulation.", "test_subject": "The frozen web-content scope rendered with the named Windows Contrast Theme and forced colours active.", "test_targets": [ "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle." ], "applicability": "Apply Runtime forced-colours toggle when the frozen web-content scope rendered with the named Windows Contrast Theme and forced colours active. The selected focus is Runtime forced-colours toggle.", "applicability_questions": [ "Does the frozen scope contain a target relevant to Runtime forced-colours toggle?", "Are the required real environments, versions and settings identified separately from diagnostic simulations?", "Which default, revealed, error, interruption, recovery and confirmation states can change the result?", "Does a scope exclusion need to be reported separately from target applicability?" ], "inapplicability_conditions": [ "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle." ], "assumptions": [ "The selected scope identifies the product version, technologies, states and important user journeys being evaluated.", "The tester knows how to use this method and any required assistive technology.", "Known browser or assistive-technology limitations are recorded instead of being assigned to the product without evidence." ], "accessibility_support_assumptions": [ "The result covers only the browsers, platforms, readers and assistive technologies that were actually tested.", "Do not apply a result from one technology combination to an untested combination or to every user." ], "prerequisites": [ "The product area and test targets are agreed before testing starts.", "The operating system, browser, viewport and input method are recorded.", "Test data is safe to use and does not expose unnecessary personal information." ], "required_environment_fields": [ "operating_system", "operating_system_version", "browser", "browser_version", "viewport_css_pixels", "input_method", "contrast_theme" ], "steps": [ { "step_id": "S1", "title": "Prepare the scope, target and environment", "phase": "prepare", "test_target": "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.", "required_state": "For Runtime forced-colours toggle, the product version and scope are frozen; every selected target and material starting state is uniquely identified.", "tool_or_command": "Use the scope record and worksheet environment fields for Runtime forced-colours toggle: operating_system, operating_system_version, browser, browser_version, viewport_css_pixels, input_method, contrast_theme.", "action": "Before executing Runtime forced-colours toggle, freeze the product version and scope. Inventory each applicable target, select the required starting states, prepare safe test data and record every required environment value. Complete any named known-good calibration before attributing an observation to the product.", "expected": "The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.", "failure_observation": "During Runtime forced-colours toggle, the target, starting state, environment or scope record remains ambiguous for the scenario named Prepare the scope, target and environment. The preparation result cannot be demonstrated: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.", "evidence_to_record": "Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.", "decision_effect": "For Runtime forced-colours toggle, an incomplete setup blocks the affected execution or leaves the omitted target untested; it never creates a pass or product failure.", "recovery_or_repeat": "For Runtime forced-colours toggle, correct the setup gap, preserve the original blocked record and start a new execution observation before proceeding.", "novice_guidance": "For Runtime forced-colours toggle, do not begin from an undocumented browser tab, document copy, device state, participant plan or evidence set. Record the exact item you will test first.", "limitations_and_claim_boundary": "This scenario records the action named Prepare the scope, target and environment for Runtime forced-colours toggle in windows-forced-colors-edge. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.", "scenario_purpose": "For Runtime forced-colours toggle, prepare the named scenario: Prepare the scope, target and environment. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. The preparation must establish this result: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.", "user_impact": "Information, boundaries, focus, selection or status may disappear or become indistinguishable. This scenario isolates that risk in the action named Prepare the scope, target and environment.", "decision_rules": { "passed": "Record passed for the Runtime forced-colours toggle scenario named Prepare the scope, target and environment only when the evidence (Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.) supports: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.", "failed": "Record failed when the action is completed and this failure observation is reproduced: During Runtime forced-colours toggle, the target, starting state, environment or scope record remains ambiguous for the scenario named Prepare the scope, target and environment. The preparation result cannot be demonstrated: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.", "not_applicable": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "blocked": "Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed." } }, { "step_id": "S2", "title": "Record Windows build, Edge build, active contrast theme and display scale", "phase": "test", "action": "Record Windows build, Edge build, active contrast theme and display scale; save the default-state comparison.", "expected": "The operating-system forced-colours environment is reproducible.", "evidence_to_record": "Windows, Edge, contrast-theme, display-scale and zoom versions/settings.", "test_target": "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.", "required_state": "For Runtime forced-colours toggle, begin in the recorded default state for the selected Runtime forced-colours toggle target before this action; preserve the exact content, account, platform and configuration used.", "tool_or_command": "In windows-forced-colors-edge, In Windows Settings, activate the recorded Contrast Theme, then use the named browser without forced-colour emulation. Compare the default rendering with the active system theme and inspect focus, selected, disabled, error and success states.", "decision_effect": "For Runtime forced-colours toggle, compare the recorded observation with this expected result: The operating-system forced-colours environment is reproducible. A material mismatch fails this target expectation; conflicting platform or responsibility evidence is cannot tell, not a pass.", "recovery_or_repeat": "Repeat with at least one light and one dark Windows Contrast Theme and for every meaningful interactive state represented by the target. Preserve the first Runtime forced-colours toggle observation when repeating.", "novice_guidance": "For Runtime forced-colours toggle: Do not judge the original CSS colours. Check whether system colours preserve boundaries, meaning and state when author backgrounds and images are substituted or removed.", "scenario_purpose": "For Runtime forced-colours toggle, execute the named scenario: Record Windows build, Edge build, active contrast theme and display scale. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. Compare the observation with this result: The operating-system forced-colours environment is reproducible.", "user_impact": "Information, boundaries, focus, selection or status may disappear or become indistinguishable. This scenario isolates that risk in the action named Record Windows build, Edge build, active contrast theme and display scale.", "failure_observation": "After the tester completes the Runtime forced-colours toggle scenario named Record Windows build, Edge build, active contrast theme and display scale, the recorded observation for the target is inconsistent with the required result: The operating-system forced-colours environment is reproducible.", "decision_rules": { "passed": "Record passed for the Runtime forced-colours toggle scenario named Record Windows build, Edge build, active contrast theme and display scale only when the evidence (Windows, Edge, contrast-theme, display-scale and zoom versions/settings.) supports: The operating-system forced-colours environment is reproducible.", "failed": "Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Runtime forced-colours toggle scenario named Record Windows build, Edge build, active contrast theme and display scale, the recorded observation for the target is inconsistent with the required result: The operating-system forced-colours environment is reproducible.", "not_applicable": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "blocked": "Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed." }, "limitations_and_claim_boundary": "This scenario records the action named Record Windows build, Edge build, active contrast theme and display scale for Runtime forced-colours toggle in windows-forced-colors-edge. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision." }, { "step_id": "S3", "title": "With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening", "phase": "test", "action": "With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening.", "expected": "Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "evidence_to_record": "Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.", "test_target": "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.", "required_state": "For Runtime forced-colours toggle, begin in the target's default state followed by its fully revealed menu, dialog or expanded state; preserve the exact content, account, platform and configuration used.", "tool_or_command": "In windows-forced-colors-edge, In Windows Settings, activate the recorded Contrast Theme, then use the named browser without forced-colour emulation. Compare the default rendering with the active system theme and inspect focus, selected, disabled, error and success states.", "decision_effect": "For Runtime forced-colours toggle, compare the recorded observation with this expected result: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss. A material mismatch fails this target expectation; conflicting platform or responsibility evidence is cannot tell, not a pass.", "recovery_or_repeat": "Repeat with at least one light and one dark Windows Contrast Theme and for every meaningful interactive state represented by the target. Preserve the first Runtime forced-colours toggle observation when repeating.", "novice_guidance": "For Runtime forced-colours toggle: Do not judge the original CSS colours. Check whether system colours preserve boundaries, meaning and state when author backgrounds and images are substituted or removed.", "scenario_purpose": "For Runtime forced-colours toggle, execute the named scenario: With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. Compare the observation with this result: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "user_impact": "Information, boundaries, focus, selection or status may disappear or become indistinguishable. This scenario isolates that risk in the action named With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening.", "failure_observation": "After the tester completes the Runtime forced-colours toggle scenario named With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening, the recorded observation for the target is inconsistent with the required result: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "decision_rules": { "passed": "Record passed for the Runtime forced-colours toggle scenario named With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening only when the evidence (Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.) supports: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "failed": "Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Runtime forced-colours toggle scenario named With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening, the recorded observation for the target is inconsistent with the required result: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "not_applicable": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "blocked": "Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed." }, "limitations_and_claim_boundary": "This scenario records the action named With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening for Runtime forced-colours toggle in windows-forced-colors-edge. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision." }, { "step_id": "S4", "title": "Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom", "phase": "test", "action": "Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom.", "expected": "Every meaningful state remains distinguishable and focused controls remain visible.", "evidence_to_record": "Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.", "test_target": "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.", "required_state": "For Runtime forced-colours toggle, begin in the validation-error state immediately after submitting representative invalid input; preserve the exact content, account, platform and configuration used.", "tool_or_command": "In windows-forced-colors-edge, In Windows Settings, activate the recorded Contrast Theme, then use the named browser without forced-colour emulation. Compare the default rendering with the active system theme and inspect focus, selected, disabled, error and success states.", "decision_effect": "For Runtime forced-colours toggle, compare the recorded observation with this expected result: Every meaningful state remains distinguishable and focused controls remain visible. A material mismatch fails this target expectation; conflicting platform or responsibility evidence is cannot tell, not a pass.", "recovery_or_repeat": "Repeat with at least one light and one dark Windows Contrast Theme and for every meaningful interactive state represented by the target. Preserve the first Runtime forced-colours toggle observation when repeating.", "novice_guidance": "For Runtime forced-colours toggle: Do not judge the original CSS colours. Check whether system colours preserve boundaries, meaning and state when author backgrounds and images are substituted or removed.", "scenario_purpose": "For Runtime forced-colours toggle, execute the named scenario: Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. Compare the observation with this result: Every meaningful state remains distinguishable and focused controls remain visible.", "user_impact": "Information, boundaries, focus, selection or status may disappear or become indistinguishable. This scenario isolates that risk in the action named Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom.", "failure_observation": "After the tester completes the Runtime forced-colours toggle scenario named Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom, the recorded observation for the target is inconsistent with the required result: Every meaningful state remains distinguishable and focused controls remain visible.", "decision_rules": { "passed": "Record passed for the Runtime forced-colours toggle scenario named Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom only when the evidence (Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.) supports: Every meaningful state remains distinguishable and focused controls remain visible.", "failed": "Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Runtime forced-colours toggle scenario named Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom, the recorded observation for the target is inconsistent with the required result: Every meaningful state remains distinguishable and focused controls remain visible.", "not_applicable": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "blocked": "Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed." }, "limitations_and_claim_boundary": "This scenario records the action named Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom for Runtime forced-colours toggle in windows-forced-colors-edge. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision." }, { "step_id": "S5", "title": "Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict", "phase": "test", "action": "Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict.", "expected": "Evidence includes every materially different state and theme defect.", "evidence_to_record": "Meaningful graphic, system-colour mapping and any lost boundary or colour-only distinction.", "test_target": "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.", "required_state": "For Runtime forced-colours toggle, begin in the recorded default state for the selected Runtime forced-colours toggle target before this action; preserve the exact content, account, platform and configuration used.", "tool_or_command": "In windows-forced-colors-edge, In Windows Settings, activate the recorded Contrast Theme, then use the named browser without forced-colour emulation. Compare the default rendering with the active system theme and inspect focus, selected, disabled, error and success states.", "decision_effect": "For Runtime forced-colours toggle, compare the recorded observation with this expected result: Evidence includes every materially different state and theme defect. A material mismatch fails this target expectation; conflicting platform or responsibility evidence is cannot tell, not a pass.", "recovery_or_repeat": "Repeat with at least one light and one dark Windows Contrast Theme and for every meaningful interactive state represented by the target. Preserve the first Runtime forced-colours toggle observation when repeating.", "novice_guidance": "For Runtime forced-colours toggle: Do not judge the original CSS colours. Check whether system colours preserve boundaries, meaning and state when author backgrounds and images are substituted or removed.", "scenario_purpose": "For Runtime forced-colours toggle, execute the named scenario: Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. Compare the observation with this result: Evidence includes every materially different state and theme defect.", "user_impact": "Information, boundaries, focus, selection or status may disappear or become indistinguishable. This scenario isolates that risk in the action named Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict.", "failure_observation": "After the tester completes the Runtime forced-colours toggle scenario named Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict, the recorded observation for the target is inconsistent with the required result: Evidence includes every materially different state and theme defect.", "decision_rules": { "passed": "Record passed for the Runtime forced-colours toggle scenario named Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict only when the evidence (Meaningful graphic, system-colour mapping and any lost boundary or colour-only distinction.) supports: Evidence includes every materially different state and theme defect.", "failed": "Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Runtime forced-colours toggle scenario named Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict, the recorded observation for the target is inconsistent with the required result: Evidence includes every materially different state and theme defect.", "not_applicable": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "blocked": "Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed." }, "limitations_and_claim_boundary": "This scenario records the action named Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict for Runtime forced-colours toggle in windows-forced-colors-edge. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision." } ], "expectations": [ { "expectation_id": "E1", "statement": "Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "outcome_if_unmet": "failed" } ], "exceptions": [ "Use only an exception stated in the relevant standard, or an agreed out-of-scope decision. Record the reason and evidence.", "A tool limitation, lack of time or unavailable assistive technology is a limitation or incomplete result, not a pass." ], "outcome_definitions": { "passed": "The applicable test target meets every expectation in this rule or procedure.", "failed": "The applicable test target does not meet at least one expectation in this rule or procedure.", "inapplicable": "The test subject contains no target that matches this rule or procedure's applicability.", "cantTell": "The tester cannot fully determine applicability or whether every expectation is met.", "untested": "The test subject or target was not evaluated using this rule or procedure." }, "examples": [ { "example_id": "A11Y-COLOR-005-EX-PASSED", "outcome": "passed", "scenario": "Representative calibration example, not client evidence. Procedure: Runtime forced-colours toggle. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. Action: Before executing Runtime forced-colours toggle, freeze the product version and scope. Inventory each applicable target, select the required starting states, prepare safe test data and record every required environment value. Complete any named known-good calibration before attributing an observation to the product. Evidence: Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required. Observed result: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup." }, { "example_id": "A11Y-COLOR-005-EX-FAILED", "outcome": "failed", "scenario": "Representative calibration example, not client evidence. Procedure: Runtime forced-colours toggle. Target: Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle. The tester completes the recorded action, but the captured evidence does not demonstrate: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup. The failed target and state remain separate from unexecuted targets." }, { "example_id": "A11Y-COLOR-005-EX-INAPPLICABLE", "outcome": "inapplicable", "scenario": "Representative scope example, not client evidence. The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle. The completed inventory is retained as the basis for the inapplicable outcome." }, { "example_id": "A11Y-COLOR-005-EX-CANTTELL", "outcome": "cantTell", "scenario": "Representative unresolved example, not client evidence. The target is applicable, but conflicting evidence or unresolved responsibility prevents a defensible expectation decision after recorded comparison. The record identifies the conflicting evidence and the expertise or comparison needed to resolve it." }, { "example_id": "A11Y-COLOR-005-EX-UNTESTED", "outcome": "untested", "scenario": "Representative execution-gap example, not client evidence. An applicable target, required state, complete process or named real environment was not executed. The missing action, state or environment remains open and is not converted to a pass." } ], "sampling_rule": "Test every in-scope instance when practical. For a large population, document a sample that includes each template, content or control type, meaningful state and high-risk task.", "complete_process_requirement": "If this check is part of a user journey, test the selected journey from start to finish, including relevant errors and recovery. Record any path that was not tested.", "pass_criteria": "Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "fail_criteria": "Fail if any applicable sampled instance does not satisfy: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "evidence_requirements": [ "Windows, Edge, contrast-theme, display-scale and zoom versions/settings.", "Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.", "Meaningful graphic, system-colour mapping and any lost boundary or colour-only distinction." ], "official_source_ids": [ "W3C-WCAG22", "MICROSOFT-CONTRAST-THEMES", "MICROSOFT-EDGE-A11Y", "W3C-WCAG22-TECHNIQUES" ], "act_rule_mapping": { "format_alignment": "This is a project-authored manual procedure, not a W3C Approved ACT Rule.", "approved_rule_ids": [], "approved_rules": [], "mapping_status": "No supporting ACT rule selected", "registry_reviewed_at": "2026-08-27", "registry_source_id": "W3C-ACT-RULES", "mapping_rationale": "An ACT result can support only the part of this procedure covered by that rule. It does not replace the remaining manual or assistive-technology checks." }, "technique_traceability": [ { "wcag_criterion": "1.4.1", "understanding_url": "https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html", "techniques_registry_source_id": "W3C-WCAG22-TECHNIQUES", "technique_ids_applied": [], "failure_ids_applied": [], "selection_status": "Select relevant techniques during the test", "selection_note": "Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion." }, { "wcag_criterion": "1.4.3", "understanding_url": "https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html", "techniques_registry_source_id": "W3C-WCAG22-TECHNIQUES", "technique_ids_applied": [], "failure_ids_applied": [], "selection_status": "Select relevant techniques during the test", "selection_note": "Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion." }, { "wcag_criterion": "1.4.11", "understanding_url": "https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html", "techniques_registry_source_id": "W3C-WCAG22-TECHNIQUES", "technique_ids_applied": [], "failure_ids_applied": [], "selection_status": "Select relevant techniques during the test", "selection_note": "Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion." }, { "wcag_criterion": "2.4.7", "understanding_url": "https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html", "techniques_registry_source_id": "W3C-WCAG22-TECHNIQUES", "technique_ids_applied": [], "failure_ids_applied": [], "selection_status": "Select relevant techniques during the test", "selection_note": "Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion." } ], "platform_ids": [ "windows-forced-colors-edge" ], "review_requirement": "A qualified accessibility reviewer must confirm the scope, evidence and result before it is reported as final.", "known_issues": [ "Check relevant browser, tool or assistive-technology release notes before assigning unexpected behaviour to the product.", "If responsibility is unclear, record the reproducible behaviour and use cannot tell until it is resolved." ], "change_log": [ { "version": "2026.08.27-rc.9", "change": "Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status." }, { "version": "2026.08.27-rc.9", "change": "Case-specific specialist content, evidence and platform boundaries completed for hash-bound agent verification." }, { "version": "2026.08.27-rc.9", "change": "Removed administrative filler steps, added contextual risk and result boundaries, and prepared the concise worksheet flow for internal consistency review." } ], "tags": [ "contrast-theme", "forced-colors", "forced_colors" ], "status": "draft", "authoring_readiness": "content_complete", "short_title": "Runtime forced-colours toggle", "catalogue_version": "2026.08.27-rc.9", "identity": { "stable_case_id": "A11Y-COLOR-005", "procedure_title": "Runtime forced-colours toggle", "short_user_centred_title": "Runtime forced-colours toggle", "procedure_version": "2026.08.27-rc.9", "catalogue_version": "2026.08.27-rc.9", "status": "draft", "category": "forced_colors", "procedure_type": "atomic", "execution_class": "manual_with_automation_support", "intended_tester_expertise": "General QA tester", "effort_model": { "model": "component_effort_v2", "small_scope_minutes": { "minimum": 40, "maximum": 58 }, "warning": "Add a new per-target execution and evidence allowance for each additional target class or state that could produce a different result. Add setup time for each distinct environment.", "calculation_guidance": "Add the recorded setup, per-target execution, evidence and technical-review components; then apply the stated variation rule.", "unit": "minutes", "setup": { "typical": 12, "includes": "Confirm scope and target, prepare safe data, establish the required state and record the tool or environment version." }, "per_target_execution": { "typical": 12, "includes": "Perform the procedure once for one target in its selected states; this excludes remediation and retesting." }, "evidence_capture": { "typical": 8, "includes": "Capture, name and cross-reference the minimum reproducible evidence while removing unnecessary personal or secret data." }, "technical_review": { "typical": 8, "includes": "Check applicability, observations, outcome logic, evidence sufficiency and report wording before issue publication." }, "typical_total_range": { "minimum": 40, "maximum": 58 }, "assumptions": "one page in one Windows contrast theme; add themes only when product colours or assets respond differently", "variation": "Add a new per-target execution and evidence allowance for each additional target class or state that could produce a different result. Add setup time for each distinct environment.", "excludes": "Client coordination, inaccessible-environment recovery, recruitment, legal review, remediation implementation and waiting time unless the procedure states otherwise." }, "related_procedures": [ "A11Y-WCAG-012", "A11Y-WCAG-014", "A11Y-WCAG-018", "A11Y-WCAG-033" ], "replaces": [], "replaced_by": [] }, "purpose_and_user_impact": { "barrier_detected": "Checks runtime forced-colours toggle without relying on browser-only CSS emulation.", "people_likely_affected": [ "People with low vision or colour-perception differences who use system contrast themes." ], "functionality_or_information_at_risk": "Information, boundaries, focus, selection or status may disappear or become indistinguishable.", "result_scope": "platform_interoperability", "claim_boundary": "This procedure records how Runtime forced-colours toggle behaves on windows-forced-colors-edge. It can expose evidence relevant to WCAG 1.4.1, 1.4.3, 1.4.11 and 2.4.7 for the tested task and environment. Use the linked conformance procedures for WCAG 1.4.1, 1.4.3, 1.4.11 and 2.4.7 to assess the complete requirements across the declared conformance scope.", "why_it_matters": "Information, boundaries, focus, selection or status may disappear or become indistinguishable. The procedure is necessary because checks runtime forced-colours toggle without relying on browser-only CSS emulation and the result can otherwise conceal a material barrier for the affected people named here." }, "requirement_mappings": [ { "source_id": "W3C-WCAG22", "requirement_id": "1.4.1", "requirement_level": "AA", "requirement_type": "secondary", "coverage_type": "partial", "canonical_source": "https://www.w3.org/TR/WCAG22/", "source_status": "W3C Recommendation", "source_version_or_publication_date": "WCAG 2.2; 12 December 2024 Recommendation", "date_verified": "2026-08-27", "reviewer_notes": "The mapping describes the intended scope of this draft procedure. Independent standards review remains required.", "limitations": "This Forced-colours check observes Runtime forced-colours toggle in the recorded windows-forced-colors-edge environment. Use the linked WCAG 1.4.1 conformance procedure to evaluate all normative parts of WCAG 1.4.1 across the declared scope.", "dependent_fields": [ "applicability_model", "normative_exceptions", "steps", "decision_logic" ] }, { "source_id": "W3C-WCAG22", "requirement_id": "1.4.3", "requirement_level": "AA", "requirement_type": "secondary", "coverage_type": "partial", "canonical_source": "https://www.w3.org/TR/WCAG22/", "source_status": "W3C Recommendation", "source_version_or_publication_date": "WCAG 2.2; 12 December 2024 Recommendation", "date_verified": "2026-08-27", "reviewer_notes": "The mapping describes the intended scope of this draft procedure. Independent standards review remains required.", "limitations": "This Forced-colours check observes Runtime forced-colours toggle in the recorded windows-forced-colors-edge environment. Use the linked WCAG 1.4.3 conformance procedure to evaluate all normative parts of WCAG 1.4.3 across the declared scope.", "dependent_fields": [ "applicability_model", "normative_exceptions", "steps", "decision_logic" ] }, { "source_id": "W3C-WCAG22", "requirement_id": "1.4.11", "requirement_level": "AA", "requirement_type": "secondary", "coverage_type": "partial", "canonical_source": "https://www.w3.org/TR/WCAG22/", "source_status": "W3C Recommendation", "source_version_or_publication_date": "WCAG 2.2; 12 December 2024 Recommendation", "date_verified": "2026-08-27", "reviewer_notes": "The mapping describes the intended scope of this draft procedure. Independent standards review remains required.", "limitations": "This Forced-colours check observes Runtime forced-colours toggle in the recorded windows-forced-colors-edge environment. Use the linked WCAG 1.4.11 conformance procedure to evaluate all normative parts of WCAG 1.4.11 across the declared scope.", "dependent_fields": [ "applicability_model", "normative_exceptions", "steps", "decision_logic" ] }, { "source_id": "W3C-WCAG22", "requirement_id": "2.4.7", "requirement_level": "AA", "requirement_type": "secondary", "coverage_type": "partial", "canonical_source": "https://www.w3.org/TR/WCAG22/", "source_status": "W3C Recommendation", "source_version_or_publication_date": "WCAG 2.2; 12 December 2024 Recommendation", "date_verified": "2026-08-27", "reviewer_notes": "The mapping describes the intended scope of this draft procedure. Independent standards review remains required.", "limitations": "This Forced-colours check observes Runtime forced-colours toggle in the recorded windows-forced-colors-edge environment. Use the linked WCAG 2.4.7 conformance procedure to evaluate all normative parts of WCAG 2.4.7 across the declared scope.", "dependent_fields": [ "applicability_model", "normative_exceptions", "steps", "decision_logic" ] }, { "source_id": "MICROSOFT-CONTRAST-THEMES", "requirement_id": "MICROSOFT-CONTRAST-THEMES", "requirement_level": "informative", "requirement_type": "advisory", "coverage_type": "supporting", "canonical_source": "https://support.microsoft.com/en-us/accessibility/edge/accessibility-features-in-microsoft-edge", "source_status": "vendor_guidance", "source_version_or_publication_date": "Current first-party publication; exact version pending source review", "date_verified": "2026-08-27", "reviewer_notes": "Supporting source. Procedure-level content review remains recorded separately.", "limitations": "This source does not override WCAG or create an additional WCAG conformance requirement.", "dependent_fields": [ "prerequisites", "environment", "steps" ] }, { "source_id": "MICROSOFT-EDGE-A11Y", "requirement_id": "MICROSOFT-EDGE-A11Y", "requirement_level": "informative", "requirement_type": "advisory", "coverage_type": "supporting", "canonical_source": "https://learn.microsoft.com/en-us/microsoft-edge/devtools/accessibility/reference", "source_status": "vendor_guidance", "source_version_or_publication_date": "Current first-party publication; exact version pending source review", "date_verified": "2026-08-27", "reviewer_notes": "Supporting source. Procedure-level content review remains recorded separately.", "limitations": "This source does not override WCAG or create an additional WCAG conformance requirement.", "dependent_fields": [ "prerequisites", "environment", "steps" ] }, { "source_id": "W3C-WCAG22-TECHNIQUES", "requirement_id": "W3C-WCAG22-TECHNIQUES", "requirement_level": "informative", "requirement_type": "advisory", "coverage_type": "supporting", "canonical_source": "https://www.w3.org/WAI/WCAG22/Techniques/", "source_status": "living_guidance", "source_version_or_publication_date": "Techniques for WCAG 2.2", "date_verified": "2026-08-27", "reviewer_notes": "Supporting source. Procedure-level content review remains recorded separately.", "limitations": "This source does not override WCAG or create an additional WCAG conformance requirement.", "dependent_fields": [ "prerequisites", "environment", "steps" ] } ], "applicability_model": { "test_subject": "The frozen web-content scope rendered with the named Windows Contrast Theme and forced colours active.", "test_targets": [ "Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle." ], "objective_questions": [ "Does the frozen scope contain a target relevant to Runtime forced-colours toggle?", "Are the required real environments, versions and settings identified separately from diagnostic simulations?", "Which default, revealed, error, interruption, recovery and confirmation states can change the result?", "Does a scope exclusion need to be reported separately from target applicability?" ], "subjective_judgements": [ "Record any judgement about meaning, equivalence, task success, platform responsibility or exception use with evidence for independent review." ], "inapplicability_conditions": [ "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle." ], "scope_exclusions": [ "An agreed exclusion is a reporting limitation, not an inapplicable target and not a pass." ], "required_states_and_variations": [ "Default, revealed, loading, empty, validation error, interruption, recovery and confirmation where meaningful.", "Every required environment, viewport, orientation, language and authenticated state recorded in the frozen scope." ], "complete_process_dependencies": "Run each selected critical process from its defined start through success, at least one representative error, interruption and recovery, and confirmation where the focus can affect task completion.", "conforming_alternate_version_considerations": "A conforming alternate version can affect a WCAG report only when all WCAG conformance conditions are verified separately. It does not erase a platform or usability observation." }, "normative_exceptions": [], "normative_exceptions_absent_reason": "This platform, journey, usability or quality procedure creates no additional normative exception. Apply exceptions only in the linked atomic or criterion-level conformance procedure and preserve that separate decision.", "environment": { "required_tester_expertise": "General QA tester", "required_platforms": [ "windows-forced-colors-edge" ], "minimum_environment_fields": [ "operating_system", "operating_system_version", "browser", "browser_version", "viewport_css_pixels", "input_method", "contrast_theme" ], "product_and_content_version_required": true, "viewport_and_orientation_required": true, "input_mode_required": true, "relevant_settings": [ "Windows Contrast Theme", "Browser version", "Display scale", "Browser zoom", "Forced-colour adjustments" ], "known_platform_limitations": [ "One contrast theme does not represent every user colour choice. Browser emulation is diagnostic only unless the procedure explicitly says otherwise.", "Check relevant browser, tool or assistive-technology release notes before assigning unexpected behaviour to the product.", "If responsibility is unclear, record the reproducible behaviour and use cannot tell until it is resolved." ], "clean_state_requirements": [ "Complete a known-good calibration in the same environment before product testing.", "Start from a recorded clean or known state and preserve any prior preferences, extensions, cache or profile settings that can affect output." ], "test_data_and_privacy_constraints": [ "Use authorised synthetic or controlled data.", "Do not record credentials, secrets or unnecessary personal data." ], "coverage_boundary": "One contrast theme does not represent every user colour choice. Browser emulation is diagnostic only unless the procedure explicitly says otherwise." }, "decision_logic": { "target_passed": "Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "target_failed": "An applicable Runtime forced-colours toggle target has a reproducible material barrier against one or more stated expectations; identify the exact expectation, state and evidence.", "target_inapplicable": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "target_cant_tell": "The target is applicable, but conflicting evidence or unresolved responsibility prevents a defensible expectation decision after recorded comparison.", "target_untested": "An applicable target, required state, complete process or named real environment was not executed.", "aggregation": "Preserve every target/environment outcome. Any failed target prevents an overall passed procedure result. cantTell and untested remain unresolved; inapplicable is valid only when the completed inventory contains no applicable target.", "wcag_requirement_decision": "This specialist, platform, document, usability or quality result does not set a WCAG success criterion to satisfied or not_satisfied automatically. Use linked atomic and criterion-level procedures for that separate decision.", "conforming_alternate_version_effect": "Record alternate-version evidence separately. It does not erase a barrier in this tested version or environment.", "passed_automation_follow_up": "A checker, accessibility-tree inspection, emulator or simulated assistive technology is diagnostic evidence only. Complete every required manual, real-platform, contextual and exception check.", "platform_responsibility": "Compare the product with a known-good control and an authorised alternate environment. Record product defect, external limitation or unresolved responsibility only when evidence supports it; otherwise use cantTell.", "claim_readiness": "Schema validation or a passed target never creates a conformance or release claim. Required executions, a distinct competent review, limitations and any applicable legal, participant or organisational authority remain separate gates." }, "evidence_specification": [ { "evidence_id": "EV1", "method": "environment_record", "record": "Windows, Edge, contrast-theme, display-scale and zoom versions/settings.", "review_purpose": "Allow an independent reviewer to reproduce the target, environment, action, actual behaviour and decision.", "privacy_and_security": "Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.", "required_for_formal_result": true }, { "evidence_id": "EV2", "method": "state_comparison", "record": "Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.", "review_purpose": "Allow an independent reviewer to reproduce the target, environment, action, actual behaviour and decision.", "privacy_and_security": "Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.", "required_for_formal_result": true }, { "evidence_id": "EV3", "method": "graphic_record", "record": "Meaningful graphic, system-colour mapping and any lost boundary or colour-only distinction.", "review_purpose": "Allow an independent reviewer to reproduce the target, environment, action, actual behaviour and decision.", "privacy_and_security": "Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.", "required_for_formal_result": true } ], "calibration_examples": [ { "example_id": "A11Y-COLOR-005-EX-PASS", "outcome": "passed", "scenario": "In windows-forced-colors-edge, the selected Runtime forced-colours toggle target completes the recorded action and meets this expectation: Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.", "explanation": "The example is a calibration scenario, not an execution or approval.", "fixture_id": "", "fixture_version": "", "machine_testable": false }, { "example_id": "A11Y-COLOR-005-EX-FAIL", "outcome": "failed", "scenario": "An applicable Runtime forced-colours toggle target produces a reproducible barrier during the named action, with the exact state and affected user task recorded.", "explanation": "A failed target remains failed even if another environment or target passes.", "fixture_id": "", "fixture_version": "", "machine_testable": false }, { "example_id": "A11Y-COLOR-005-EX-INAPPLICABLE", "outcome": "inapplicable", "scenario": "The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.", "explanation": "Inapplicable requires a completed inventory showing that no target matches applicability; a missing environment is not inapplicable.", "fixture_id": "", "fixture_version": "", "machine_testable": false }, { "example_id": "A11Y-COLOR-005-EX-CANTTELL", "outcome": "cantTell", "scenario": "The Runtime forced-colours toggle target is applicable, but conflicting product/platform evidence or missing authoritative information prevents a defensible responsibility or expectation decision.", "explanation": "Record the conflict, comparisons attempted and person or evidence needed to resolve it.", "fixture_id": "", "fixture_version": "", "machine_testable": false }, { "example_id": "A11Y-COLOR-005-EX-UNTESTED", "outcome": "untested", "scenario": "The Runtime forced-colours toggle target is applicable, but a required state, complete process or real environment was not executed.", "explanation": "Untested remains incomplete and cannot be converted to passed or inapplicable.", "fixture_id": "", "fixture_version": "", "machine_testable": false } ], "review_record": { "author": "", "method_reviewer": "", "independent_standards_reviewer": "", "accessibility_ui_reviewer": "", "author_date": "", "method_review_date": "", "standards_review_date": "", "ui_review_date": "", "source_versions_reviewed": [], "exceptions_reviewed": false, "known_limitations": [ "One contrast theme does not represent every user colour choice. Browser emulation is diagnostic only unless the procedure explicitly says otherwise.", "Real execution evidence and any customer-required legal, participant or organisational authority remain separate." ], "open_issues": [ "Execute all required real environments and calibration cases.", "Complete a distinct competent review and retain any unresolved material finding as blocked or cantTell." ], "decision": "pending", "next_review_date": "", "status_transition_reason": "", "release_gate_id": "", "release_gate_completed_at": "", "approval_authority": "", "approval_date": "" }, "privacy_and_security": { "browser_storage": "Worksheet data is stored only in this browser's local storage until the user exports or clears it.", "network_transmission": "The static library does not upload worksheet data.", "data_minimisation": "Record only evidence necessary to reproduce and review the decision.", "redaction": "Remove credentials, secrets and unnecessary personal or participant data before export or sharing.", "retention_and_deletion": "Apply the engagement retention schedule and clear local browser data when it is no longer required." }, "version_history": [ { "version": "2026.08.27-rc.9", "change": "Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status." }, { "version": "2026.08.27-rc.9", "change": "Migrated to professional catalogue schema v3 with separated outcomes, structured authority, applicability, evidence, decision and review records." }, { "version": "2026.08.27-rc.9", "change": "Specialist procedure mapped to its task family and current first-party platform guidance and checked for internal consistency; competent review and real execution remain separate." }, { "version": "2026.08.27-rc.9", "change": "Added explicit preparation and variation/recovery steps plus a bounded representative worked example for paid-template use." }, { "version": "2026.08.27-rc.9", "change": "Procedure guidance and presentation simplified without changing draft governance status." } ], "migration": { "from_schema": "accessibility-test-catalog.v2", "from_procedure_version": "2026.08.04.1", "migrated_at": "2026-08-27", "content_review_state": "commercial_completeness_upgrade_agent_verified", "stable_identifier_preserved": true, "legacy_url_preserved": true, "delivery_model": "professional_delivery_v2", "agent_content_validation": { "status": "complete", "method": "case_specific_semantic_and_operational_checks_v1", "checked_fields": [ "target", "state", "tool", "action", "expected_observation", "failure_observation", "evidence", "outcome_rules", "claim_boundary", "compact_examples" ], "human_approval_effect": "none" } }, "test_type": "platform_interoperability", "related_procedures": [ "A11Y-WCAG-012", "A11Y-WCAG-014", "A11Y-WCAG-018", "A11Y-WCAG-033" ], "platform_validation": { "required": true, "evidence_status": "not_executed", "real_device_or_at_claimed": false, "required_environment_ids": [ "windows-forced-colors-edge" ], "calibration_required": true, "evidence_refs": [], "limitations": "One contrast theme does not represent every user colour choice. Browser emulation is diagnostic only unless the procedure explicitly says otherwise." }, "effort_guidance": { "unit": "minutes", "setup": { "typical": 12, "includes": "Confirm scope and target, prepare safe data, establish the required state and record the tool or environment version." }, "per_target_execution": { "typical": 12, "includes": "Perform the procedure once for one target in its selected states; this excludes remediation and retesting." }, "evidence_capture": { "typical": 8, "includes": "Capture, name and cross-reference the minimum reproducible evidence while removing unnecessary personal or secret data." }, "technical_review": { "typical": 8, "includes": "Check applicability, observations, outcome logic, evidence sufficiency and report wording before issue publication." }, "typical_total_range": { "minimum": 40, "maximum": 58 }, "assumptions": "one page in one Windows contrast theme; add themes only when product colours or assets respond differently", "variation": "Add a new per-target execution and evidence allowance for each additional target class or state that could produce a different result. Add setup time for each distinct environment.", "excludes": "Client coordination, inaccessible-environment recovery, recruitment, legal review, remediation implementation and waiting time unless the procedure states otherwise." }, "worked_examples": [ { "example_id": "A11Y-COLOR-005-WORKED-001", "example_kind": "representative_synthetic_example", "context": "Representative synthetic example for Runtime forced-colours toggle on a fictional, version-frozen product target; no client or participant execution occurred.", "inspected": "The tester follows S2 (Record Windows build, Edge build, active contrast theme and display scale) using the target, required state, tool and repeat rule stated in this procedure.", "observed_output": "After the tester completes the Runtime forced-colours toggle scenario named Record Windows build, Edge build, active contrast theme and display scale, the recorded observation for the target is inconsistent with the required result: The operating-system forced-colours environment is reproducible.", "evidence_captured": [ "example-evidence-001: target and state record for Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.", "example-evidence-002: contemporaneous observation from the named method — Windows, Edge, contrast-theme, display-scale and zoom versions/settings.", "example-evidence-003: comparison note linking the actual observation to the expected result and claim boundary" ], "tester_reasoning": "The recorded observation does not demonstrate the expected result: The operating-system forced-colours environment is reproducible. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.", "decision": "failed", "completed_finding": { "finding_id": "A11Y-COLOR-005-example-finding-001", "title": "Runtime forced-colours toggle: expected result is not demonstrated", "severity": "medium", "user_impact": "The represented barrier may affect People with low vision or colour-perception differences who use system contrast themes.", "evidence_refs": [ "example-evidence-001", "example-evidence-002", "example-evidence-003" ] }, "remediation_advice": "Change the represented target or process so it demonstrates this result: The operating-system forced-colours environment is reproducible. Then rerun the affected step and every dependent variation.", "reviewer_feedback": "The reviewer confirms applicability, environment, actual-versus-expected comparison, evidence references and bounded wording; unsupported product-wide or conformance language is removed.", "final_client_report_wording": "Synthetic training finding: the sampled Runtime forced-colours toggle target does not meet the procedure expectation in the recorded state. User impact and broader scope require evidence from the buyer's real execution.", "retest_outcome": "Synthetic retest example: after the represented change, repeat the failed step plus material error and recovery states. Close the finding only when new evidence demonstrates the expected result; otherwise retain the non-pass outcome.", "claim_boundary": "This is a representative, synthetic worked example for training and calibration. It is not evidence from a client product, participant or real assistive-technology execution." } ] }