Accessibility Test Cases

A11Y-COLOR-005

Runtime forced-colours toggle

Generated file current Authoring: Content complete
What file status means

This status reports only whether the generated procedure matches the current controlled source hash. It is not independent content verification, regulatory approval, product evidence or a conformance decision.

Recorded standards review: No optional specialist review recorded. Next review: Not scheduled.

MethodForced-colours check
TesterGeneral QA tester
Indicative effort40–58 min small scope

Checks runtime forced-colours toggle without relying on browser-only CSS emulation.

Available formats

Use this test in the format you need

The HTML procedure includes the working worksheet. JSON provides the structured source data. Editable Markdown files are delivered inside package downloads.

Purpose

What this test checks

Checks runtime forced-colours toggle without relying on browser-only CSS emulation.

What this result means: 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

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.

When to use it

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.

Confirm before starting

Mark it not applicable only when

Exceptions

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.

Prepare

What you need

  • 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.

Targets and required variations

  • Each selected control, graphic and meaningful state relevant to Runtime forced-colours toggle.
  • 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.

Clean state

  • 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.

Effort estimate

Setup
12 min
Per target
12 min
Evidence
8 min
Technical review
8 min

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.

Excluded: Client coordination, inaccessible-environment recovery, recruitment, legal review, remediation implementation and waiting time unless the procedure states otherwise.

Execute

Test steps

Follow each action in order. The expected result is always visible; open the guidance when you need setup, tool, evidence, decision or repeat details. Step-level recording is optional while work is in progress and required only to export a completed execution.

Step 1

Prepare the scope, target and environment

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.

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 result

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.

Setup, evidence and decision guidance
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.
Record
Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.
Pass
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.
Fail
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.
Repeat or recover
For Runtime forced-colours toggle, correct the setup gap, preserve the original blocked record and start a new execution observation before proceeding.
Limitations
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.
If you are new to this test
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.
Record this step

Step 2

Record Windows build, Edge build, active contrast theme and display scale

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.

Record Windows build, Edge build, active contrast theme and display scale; save the default-state comparison.

Expected result

The operating-system forced-colours environment is reproducible.

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.

Setup, evidence and decision guidance
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.
Record
Windows, Edge, contrast-theme, display-scale and zoom versions/settings.
Pass
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.
Fail
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.
Repeat or recover
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.
Limitations
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.
If you are new to this test
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.
Record this step

Step 3

With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening

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.

With the application open, toggle a Windows Contrast Theme off and on, then repeat after navigation and dialog opening.

Expected result

Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.

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.

Setup, evidence and decision guidance
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.
Record
Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.
Pass
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.
Fail
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.
Repeat or recover
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.
Limitations
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.
If you are new to this test
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.
Record this step

Step 4

Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom

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.

Use keyboard only through hover, focus, active, selected, checked, disabled, error, success and loading states at 200% zoom.

Expected result

Every meaningful state remains distinguishable and focused controls remain visible.

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.

Setup, evidence and decision guidance
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.
Record
Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.
Pass
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.
Fail
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.
Repeat or recover
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.
Limitations
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.
If you are new to this test
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.
Record this step

Step 5

Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict

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.

Capture representative screenshots and record any image/icon replacement, lost border, transparent control or system-colour conflict.

Expected result

Evidence includes every materially different state and theme defect.

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.

Setup, evidence and decision guidance
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.
Record
Meaningful graphic, system-colour mapping and any lost boundary or colour-only distinction.
Pass
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.
Fail
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.
Repeat or recover
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.
Limitations
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.
If you are new to this test
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.
Record this step

Decide

How to decide

Passed

Text and controls remain readable; boundaries, focus, selection, errors, status and meaningful graphics remain distinguishable without hard-coded colour loss.

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.

Not applicable
The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.
Cannot tell
The target is applicable, but conflicting evidence or unresolved responsibility prevents a defensible expectation decision after recorded comparison.
Not tested
An applicable target, required state, complete process or named real environment was not executed.
Aggregation and reporting boundaries

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 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.

Automation: A checker, accessibility-tree inspection, emulator or simulated assistive technology is diagnostic evidence only. Complete every required manual, real-platform, contextual and exception check.

Record

Record the result

Record the target, state and observed behaviour. Add evidence or technical details only when needed.

Choose the option that best matches what happened to this target.

Describe the actual behaviour and why it supports the selected result.

When more than one target is recorded, the overall procedure result is calculated from all target results.

Environment: Not set.
Add evidence or details

Choose only the group needed for this record. These fields remain optional for a working draft.

Evidence references

Enter one file name, issue ID or evidence reference per line. Files stay on your device.

Test environment

Save a named profile once to reuse the same product, platform and environment details on other procedures in this browser.

Engagement and tester identifiers

Formal completion and limitations

Identify the frozen list or sampling record used to select every target represented by this execution.

Choose a final result before marking the execution complete. Completed records require the full environment, step, evidence and method-specific information.

Data management

Export before clearing if the record must be retained. Apply the engagement retention schedule and delete browser data when it is no longer needed.

Saved drafts stay in this browser and are not uploaded. Do not enter credentials, secrets or unnecessary personal data.

Reference

Supporting information

Standards and requirement mappings
  • W3C-WCAG22 · 1.4.1 secondary · partial

    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.

  • W3C-WCAG22 · 1.4.3 secondary · partial

    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.

  • W3C-WCAG22 · 1.4.11 secondary · partial

    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.

  • W3C-WCAG22 · 2.4.7 secondary · partial

    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.

  • MICROSOFT-CONTRAST-THEMES · MICROSOFT-CONTRAST-THEMES advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • MICROSOFT-EDGE-A11Y · MICROSOFT-EDGE-A11Y advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • W3C-WCAG22-TECHNIQUES · W3C-WCAG22-TECHNIQUES advisory · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

Supporting and advisory guidance

Supporting sources are identified in the mappings and source register. They do not add conformance requirements.

Evidence specification
  • Environment record

    Windows, Edge, contrast-theme, display-scale and zoom versions/settings.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

  • State comparison

    Default and forced-colour evidence for focus, selected, disabled, error, success and loading states.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

  • Graphic record

    Meaningful graphic, system-colour mapping and any lost boundary or colour-only distinction.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

Worked example and outcome calibration

A11Y-COLOR-005-WORKED-001: representative worked 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:

  • 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

Finding: A11Y-COLOR-005-example-finding-001 — Runtime forced-colours toggle: expected result is not demonstrated. The represented barrier may affect People with low vision or colour-perception differences who use system contrast themes.

Remediation: 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 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: 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.

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.

Outcome calibration

Passed
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.

The example is a calibration scenario, not an execution or approval.

Failed
An applicable Runtime forced-colours toggle target produces a reproducible barrier during the named action, with the exact state and affected user task recorded.

A failed target remains failed even if another environment or target passes.

Not applicable
The frozen scope contains no rendered content or state relevant to Runtime forced-colours toggle.

Inapplicable requires a completed inventory showing that no target matches applicability; a missing environment is not inapplicable.

Cannot tell
The Runtime forced-colours toggle target is applicable, but conflicting product/platform evidence or missing authoritative information prevents a defensible responsibility or expectation decision.

Record the conflict, comparisons attempted and person or evidence needed to resolve it.

Not tested
The Runtime forced-colours toggle target is applicable, but a required state, complete process or real environment was not executed.

Untested remains incomplete and cannot be converted to passed or inapplicable.

Sampling, complete processes and platform limitations

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.

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.

  • 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.
Related procedures
  • A11Y-WCAG-012
  • A11Y-WCAG-014
  • A11Y-WCAG-018
  • A11Y-WCAG-033
ACT rules and WCAG technique traceability

This is a project-authored manual procedure, not a W3C Approved ACT Rule. 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.

No supporting W3C Approved ACT Rule is selected for this procedure.

  • Understanding SC 1.4.1. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 1.4.3. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 1.4.11. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 2.4.7. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
Review history and source register
  1. 2026.08.27-rc.9 — Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status.
  2. 2026.08.27-rc.9 — Migrated to professional catalogue schema v3 with separated outcomes, structured authority, applicability, evidence, decision and review records.
  3. 2026.08.27-rc.9 — 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.
  4. 2026.08.27-rc.9 — Added explicit preparation and variation/recovery steps plus a bounded representative worked example for paid-template use.
  5. 2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.

Review decision: pending. 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.

Source historyReport an accuracy issue
WCAG
SC 1.4.1, SC 1.4.3, SC 1.4.11, SC 2.4.7
Execution
Manual test with tool support
Catalogue version
2026.08.27-rc.9