Accessibility Test Cases

A11Y-DOC-009

DOCX checker and semantic styles

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.

MethodDocument review
TesterDocument accessibility specialist
Indicative effort67–97 min small scope

Checks docx checker and semantic styles on the final deliverable, not only the authoring source.

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 docx checker and semantic styles on the final deliverable, not only the authoring source.

What this result means: This procedure records how DOCX checker and semantic styles behaves on document-office. It can expose evidence relevant to WCAG 1.3.1 and 2.4.6 for the tested task and environment. Use the linked conformance procedures for WCAG 1.3.1 and 2.4.6 to assess the complete requirements across the declared conformance scope.

Why it matters

Checks docx checker and semantic styles on the final deliverable, not only the authoring source. People most likely affected: people who use screen readers, braille, keyboard access, magnification, reflow or adapted document presentations. Document structure, content or controls may be unavailable or presented in a misleading order. In the recorded document-office environment, review source semantics and the delivered file in its intended reader; conversion can lose headings, reading order, alternatives, table relationships or form behaviour that existed in the authoring tool.

When to use it

Apply DOCX checker and semantic styles when the immutable document file identified by checksum, format and authoring/export version. The selected focus is DOCX checker and semantic styles.

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 page, object, structure and operation relevant to DOCX checker and semantic styles in the final file.
  • 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
15 min
Per target
25 min
Evidence
12 min
Technical review
15 min

Assumptions: one document of up to ten pages with representative structures; long or structurally varied documents require sampling plus full automated scans

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 DOCX checker and semantic styles, prepare the named scenario: Prepare the scope, target and environment. Target: Each page, object, structure and operation relevant to DOCX checker and semantic styles in the final file. 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: Document structure, content or controls may be unavailable or presented in a misleading order. This scenario isolates that risk in the action named Prepare the scope, target and environment.

Before executing DOCX checker and semantic styles, 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 DOCX checker and semantic styles, 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 page, object, structure and operation relevant to DOCX checker and semantic styles in the final file.
Required state
For DOCX checker and semantic styles, 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 DOCX checker and semantic styles: operating_system, operating_system_version, document_application, document_application_version, document_format, document_identifier_or_checksum, authoring_or_export_tool, authoring_or_export_tool_version, accessibility_checker, accessibility_checker_version, assistive_technology, assistive_technology_version, input_method.
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 DOCX checker and semantic styles 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 DOCX checker and semantic styles, 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 immutable file contains no object, structure or operation relevant to DOCX checker and semantic styles.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
For DOCX checker and semantic styles, 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 DOCX checker and semantic styles in document-office. 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 DOCX checker and semantic styles, 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

Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane

Purpose: For DOCX checker and semantic styles, execute the named scenario: Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane. Target: Each page, object, structure and operation relevant to DOCX checker and semantic styles in the final file. Compare the observation with this result: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

User impact: Document structure, content or controls may be unavailable or presented in a misleading order. This scenario isolates that risk in the action named Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane.

Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane.

Expected result

The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

Failure observation

After the tester completes the DOCX checker and semantic styles scenario named Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane, the recorded observation for the target is inconsistent with the required result: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

Setup, evidence and decision guidance
Target
Each page, object, structure and operation relevant to DOCX checker and semantic styles in the final file.
Required state
For DOCX checker and semantic styles, begin in the recorded default state for the selected DOCX checker and semantic styles target before this action; preserve the exact content, account, platform and configuration used.
Tool or command
In document-office, Inspect the immutable delivered file in its intended reader. For PDF use Acrobat Pro's Accessibility Check, Tags panel and Reading Order tool as diagnostics; for Microsoft 365 files use Review > Check Accessibility, then confirm the result manually and with the required real reader or assistive technology.
Record
Checker name/version, exported report and disposition of every error, warning and manual check. Save checker output, structural evidence, screen-reader notes and page/slide/sheet/cell locations for each result.
Pass
Record passed for the DOCX checker and semantic styles scenario named Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane only when the evidence (Checker name/version, exported report and disposition of every error, warning and manual check. Save checker output, structural evidence, screen-reader notes and page/slide/sheet/cell locations for each result.) supports: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the DOCX checker and semantic styles scenario named Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane, the recorded observation for the target is inconsistent with the required result: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.
Not applicable
The immutable file contains no object, structure or operation relevant to DOCX checker and semantic styles.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat representative reading/navigation with keyboard and a real screen reader; inspect every unique layout/template and all complex content. Repeat for every unique structure and every instance that changes meaning, reading order or interaction, including exported and remediated versions. Preserve the first DOCX checker and semantic styles observation when repeating.
Limitations
This scenario records the action named Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane for DOCX checker and semantic styles in document-office. 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 DOCX checker and semantic styles: A clean checker result is not a pass. Locate the exact object in the delivered file and verify its semantics, reading order and operation in the reader used by the procedure.
Record this step

Step 3

Repeat material variations and recovery

Purpose: For DOCX checker and semantic styles, execute the named scenario: Repeat material variations and recovery. Target: Each page, object, structure and operation relevant to DOCX checker and semantic styles in the final file. Compare the observation with this result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

User impact: Document structure, content or controls may be unavailable or presented in a misleading order. This scenario isolates that risk in the action named Repeat material variations and recovery.

Repeat the DOCX checker and semantic styles action for each inventoried variation that can change the outcome. Include relevant default, revealed, error, interruption, recovery and confirmation states and complete the selected process from start to finish where this test can affect task completion.

Expected result

Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Failure observation

After the tester completes the DOCX checker and semantic styles scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Setup, evidence and decision guidance
Target
Each page, object, structure and operation relevant to DOCX checker and semantic styles in the final file.
Required state
For DOCX checker and semantic styles: 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.
Tool or command
For DOCX checker and semantic styles, use the same recorded method, then change only the state, environment or recovery condition being compared.
Record
Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.
Pass
Record passed for the DOCX checker and semantic styles scenario named Repeat material variations and recovery only when the evidence (Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.) supports: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the DOCX checker and semantic styles scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Not applicable
The immutable file contains no object, structure or operation relevant to DOCX checker and semantic styles.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat this action for every required variation of DOCX checker and semantic styles and after a material target, content, state, environment or configuration change. Preserve the original observation.
Limitations
This scenario records the action named Repeat material variations and recovery for DOCX checker and semantic styles in document-office. 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 DOCX checker and semantic styles, change one material condition at a time where practical. Do not assume that a passing default state covers errors, overlays, orientation changes, interruptions or recovery.
Record this step

Decide

How to decide

Passed

The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

Failed

An applicable DOCX checker and semantic styles target has a reproducible material barrier against one or more stated expectations; identify the exact expectation, state and evidence.

Not applicable
The immutable file contains no object, structure or operation relevant to DOCX checker and semantic styles.
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

Component expectation results

Use these controls only when the procedure has distinct component expectations. The overall outcome must agree with them.

E1 The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

E2 Every selected target and meaningful state is tested using the stated method.

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.3.1 secondary · partial

    This Document review observes DOCX checker and semantic styles in the recorded document-office environment. Use the linked WCAG 1.3.1 conformance procedure to evaluate all normative parts of WCAG 1.3.1 across the declared scope.

  • W3C-WCAG22 · 2.4.6 secondary · partial

    This Document review observes DOCX checker and semantic styles in the recorded document-office environment. Use the linked WCAG 2.4.6 conformance procedure to evaluate all normative parts of WCAG 2.4.6 across the declared scope.

  • W3C-WCAG2ICT · W3C-WCAG2ICT advisory · supporting

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

  • MICROSOFT-WORD-A11Y · MICROSOFT-WORD-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.

  • MICROSOFT-OFFICE-CHECKER · MICROSOFT-OFFICE-CHECKER platform · supporting

    Vendor documentation defines product operation only. It does not override WCAG or prove product accessibility.

Supporting and advisory guidance

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

Evidence specification
  • File integrity

    Filename, SHA-256 checksum, document version and authoring/export/remediation tools.

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

  • Tool report

    Checker name/version, exported report and disposition of every error, warning and manual check.

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

  • Document structure

    Page/object/cell/slide location and tag tree, reading order, metadata or relationship evidence.

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

  • Functional record

    Keyboard, reflow and exact assistive-technology output for each applicable complete process.

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

Worked example and outcome calibration

A11Y-DOC-009-WORKED-001: representative worked example

Context: Representative synthetic example for DOCX checker and semantic styles on a fictional, version-frozen product target; no client or participant execution occurred.

Inspected: The tester follows S2 (Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane) using the target, required state, tool and repeat rule stated in this procedure.

Observed output: After the tester completes the DOCX checker and semantic styles scenario named Run Word Accessibility Checker, then inspect title, heading styles/order, lists, columns, page breaks, headers/footers and navigation pane, the recorded observation for the target is inconsistent with the required result: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

Evidence:

  • example-evidence-001: target and state record for Each page, object, structure and operation relevant to DOCX checker and semantic styles in the final file.
  • example-evidence-002: contemporaneous observation from the named method — Checker name/version, exported report and disposition of every error, warning and manual check. Save checker output, structural evidence, screen-reader notes and page/slide/sheet/cell locations for each result.
  • 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 document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.

Decision: failed

Finding: A11Y-DOC-009-example-finding-001 — DOCX checker and semantic styles: expected result is not demonstrated. The represented barrier may affect People who use screen readers, braille, keyboard access, magnification, reflow or adapted document presentations.

Remediation: Change the represented target or process so it demonstrates this result: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed. 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 DOCX checker and semantic styles 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 document-office, the selected DOCX checker and semantic styles target completes the recorded action and meets this expectation: The document uses semantic styles in a logical hierarchy and checker findings are resolved or reviewed.

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

Failed
An applicable DOCX checker and semantic styles 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 immutable file contains no object, structure or operation relevant to DOCX checker and semantic styles.

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

Cannot tell
The DOCX checker and semantic styles 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 DOCX checker and semantic styles 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 each selected content type, state and critical task. Document what was included and any known limitation.

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.

  • A document checker supplies diagnostics only. Manual structure, reading-order and functional evidence remain necessary where applicable.
  • 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-007
  • A11Y-WCAG-032
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.3.1. 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.6. 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.3.1, SC 2.4.6
Execution
Manual test with tool support
Catalogue version
2026.08.27-rc.9