Accessibility Test Cases

A11Y-PDFUA-002

PDF/UA human-judgement conditions

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.

MethodPDF/UA protocol review
TesterPDF/UA specialist
Indicative effort180–261 min small scope

Checks PDF/UA human-judgement conditions on the checksum-identified final PDF.

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 PDF/UA human-judgement conditions on the checksum-identified final PDF.

What this result means: This procedure records how PDF/UA human-judgement conditions behaves on document-pdf. It can expose evidence relevant to WCAG 1.1.1, 1.3.1, 1.3.2, 2.1.1 and 4.1.2 for the tested task and environment. Use the linked conformance procedures for WCAG 1.1.1, 1.3.1, 1.3.2, 2.1.1 and 4.1.2 to assess the complete requirements across the declared conformance scope.

Why it matters

Checks PDF/UA human-judgement conditions on the checksum-identified final PDF. People most likely affected: people who depend on reliable PDF semantics, navigation, input, reflow, speech or braille output. A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. In the recorded document-pdf environment, use the version-matched PDF/UA protocol on the immutable file and pair machine checks with every required interpretive and functional check; a clean checker result cannot prove reading order, alternatives or interaction.

When to use it

Apply PDF/UA human-judgement conditions when the immutable PDF identified by SHA-256 checksum and an explicitly selected PDF/UA part. The selected focus is PDF/UA human-judgement conditions.

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

  • The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
  • 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
25 min
Per target
90 min
Evidence
30 min
Technical review
35 min

Assumptions: one checksum-frozen PDF with a valid protocol manifest; page count, unique structures and manual Matterhorn conditions dominate effort

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 PDF/UA human-judgement conditions, prepare the named scenario: Prepare the scope, target and environment. Target: The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions. 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: A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. This scenario isolates that risk in the action named Prepare the scope, target and environment.

Before executing PDF/UA human-judgement conditions, 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 PDF/UA human-judgement conditions, 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
The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
Required state
For PDF/UA human-judgement conditions, 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 PDF/UA human-judgement conditions: operating_system, operating_system_version, pdf_viewer, pdf_viewer_version, pdfua_part, pdf_sha256, accessibility_checker, accessibility_checker_version, authoring_or_remediation_tool, authoring_or_remediation_tool_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 PDF/UA human-judgement conditions 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 PDF/UA human-judgement conditions, 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
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
For PDF/UA human-judgement conditions, 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 PDF/UA human-judgement conditions in document-pdf. 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 PDF/UA human-judgement conditions, 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

Freeze the PDF identity, tools and protocol

Purpose: For PDF/UA human-judgement conditions, execute the named scenario: Freeze the PDF identity, tools and protocol. Target: The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions. Compare the observation with this result: The exact immutable artifact, claim and toolchain are reproducible.

User impact: A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. This scenario isolates that risk in the action named Freeze the PDF identity, tools and protocol.

Record final PDF checksum, PDF version, PDF/UA identifier, authoring/export/remediation tools, checker/version and applicable protocol before opening the file for assessment.

Expected result

The exact immutable artifact, claim and toolchain are reproducible.

Failure observation

After the tester completes the PDF/UA human-judgement conditions scenario named Freeze the PDF identity, tools and protocol, the recorded observation for the target is inconsistent with the required result: The exact immutable artifact, claim and toolchain are reproducible.

Setup, evidence and decision guidance
Target
The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
Required state
For PDF/UA human-judgement conditions, 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 document-pdf, Use a qualified PDF/UA checker whose version and condition manifest are frozen, then inspect every required manually evaluated condition in Acrobat Pro or an equivalent tag-tree and content-order inspection tool.
Record
Immutable PDF SHA-256 checksum, PDF version, PDF/UA identifier and toolchain.
Pass
Record passed for the PDF/UA human-judgement conditions scenario named Freeze the PDF identity, tools and protocol only when the evidence (Immutable PDF SHA-256 checksum, PDF version, PDF/UA identifier and toolchain.) supports: The exact immutable artifact, claim and toolchain are reproducible.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the PDF/UA human-judgement conditions scenario named Freeze the PDF identity, tools and protocol, the recorded observation for the target is inconsistent with the required result: The exact immutable artifact, claim and toolchain are reproducible.
Not applicable
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat the affected protocol conditions after remediation and reconcile changed machine results with all related human checks against the same file checksum. Preserve the first PDF/UA human-judgement conditions observation when repeating.
Limitations
This scenario records the action named Freeze the PDF identity, tools and protocol for PDF/UA human-judgement conditions in document-pdf. 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 PDF/UA human-judgement conditions: Confirm the PDF version, PDF/UA identifier and selected ISO part before running any protocol. Never apply a PDF/UA-1 Matterhorn result to PDF/UA-2.
Record this step

Step 3

Inspect every human-judgement Matterhorn condition

Purpose: For PDF/UA human-judgement conditions, execute the named scenario: Inspect every human-judgement Matterhorn condition. Target: The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions. Compare the observation with this result: Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.

User impact: A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. This scenario isolates that risk in the action named Inspect every human-judgement Matterhorn condition.

Independently inspect every Matterhorn condition designated for human judgment, including semantic appropriateness, reading order, meaningful alternatives, tables, headings, lists and sensory information.

Expected result

Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.

Failure observation

After the tester completes the PDF/UA human-judgement conditions scenario named Inspect every human-judgement Matterhorn condition, the recorded observation for the target is inconsistent with the required result: Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.

Setup, evidence and decision guidance
Target
The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
Required state
For PDF/UA human-judgement conditions, begin in keyboard focus on the last confirmed target before the action, with no pointer assistance; preserve the exact content, account, platform and configuration used.
Tool or command
In document-pdf, Use a qualified PDF/UA checker whose version and condition manifest are frozen, then inspect every required manually evaluated condition in Acrobat Pro or an equivalent tag-tree and content-order inspection tool.
Record
Tag tree, reading order, semantics and human-judgement evidence linked to page/object.
Pass
Record passed for the PDF/UA human-judgement conditions scenario named Inspect every human-judgement Matterhorn condition only when the evidence (Tag tree, reading order, semantics and human-judgement evidence linked to page/object.) supports: Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the PDF/UA human-judgement conditions scenario named Inspect every human-judgement Matterhorn condition, the recorded observation for the target is inconsistent with the required result: Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.
Not applicable
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat the affected protocol conditions after remediation and reconcile changed machine results with all related human checks against the same file checksum. Preserve the first PDF/UA human-judgement conditions observation when repeating.
Limitations
This scenario records the action named Inspect every human-judgement Matterhorn condition for PDF/UA human-judgement conditions in document-pdf. 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 PDF/UA human-judgement conditions: Confirm the PDF version, PDF/UA identifier and selected ISO part before running any protocol. Never apply a PDF/UA-1 Matterhorn result to PDF/UA-2.
Record this step

Step 4

Manually verify checker conclusions

Purpose: For PDF/UA human-judgement conditions, execute the named scenario: Manually verify checker conclusions. Target: The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions. Compare the observation with this result: Technical conformance evidence is reconciled with human judgment and functional accessibility without overclaiming either.

User impact: A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. This scenario isolates that risk in the action named Manually verify checker conclusions.

Manually verify checker conclusions with tag tree, content/reading order, keyboard, reflow and real screen-reader evidence on every unique structure and complete process.

Expected result

Technical conformance evidence is reconciled with human judgment and functional accessibility without overclaiming either.

Failure observation

After the tester completes the PDF/UA human-judgement conditions scenario named Manually verify checker conclusions, the recorded observation for the target is inconsistent with the required result: Technical conformance evidence is reconciled with human judgment and functional accessibility without overclaiming either.

Setup, evidence and decision guidance
Target
The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
Required state
For PDF/UA human-judgement conditions, begin in keyboard focus on the last confirmed target before the action, with no pointer assistance; preserve the exact content, account, platform and configuration used.
Tool or command
In document-pdf, Use a qualified PDF/UA checker whose version and condition manifest are frozen, then inspect every required manually evaluated condition in Acrobat Pro or an equivalent tag-tree and content-order inspection tool.
Record
Viewer, keyboard, reflow and real assistive-technology evidence where applicable.
Pass
Record passed for the PDF/UA human-judgement conditions scenario named Manually verify checker conclusions only when the evidence (Viewer, keyboard, reflow and real assistive-technology evidence where applicable.) supports: Technical conformance evidence is reconciled with human judgment and functional accessibility without overclaiming either.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the PDF/UA human-judgement conditions scenario named Manually verify checker conclusions, the recorded observation for the target is inconsistent with the required result: Technical conformance evidence is reconciled with human judgment and functional accessibility without overclaiming either.
Not applicable
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat the affected protocol conditions after remediation and reconcile changed machine results with all related human checks against the same file checksum. Preserve the first PDF/UA human-judgement conditions observation when repeating.
Limitations
This scenario records the action named Manually verify checker conclusions for PDF/UA human-judgement conditions in document-pdf. 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 PDF/UA human-judgement conditions: Confirm the PDF version, PDF/UA identifier and selected ISO part before running any protocol. Never apply a PDF/UA-1 Matterhorn result to PDF/UA-2.
Record this step

Step 5

Export the condition manifest, checker report, manual review record, exception rationale and final decision

Purpose: For PDF/UA human-judgement conditions, execute the named scenario: Export the condition manifest, checker report, manual review record, exception rationale and final decision. Target: The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions. Compare the observation with this result: An independent reviewer can reconcile every protocol result to the exact PDF and report claim.

User impact: A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. This scenario isolates that risk in the action named Export the condition manifest, checker report, manual review record, exception rationale and final decision.

Export the condition manifest, checker report, manual review record, exception rationale and final decision; preserve all non-pass outcomes.

Expected result

An independent reviewer can reconcile every protocol result to the exact PDF and report claim.

Failure observation

After the tester completes the PDF/UA human-judgement conditions scenario named Export the condition manifest, checker report, manual review record, exception rationale and final decision, the recorded observation for the target is inconsistent with the required result: An independent reviewer can reconcile every protocol result to the exact PDF and report claim.

Setup, evidence and decision guidance
Target
The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
Required state
For PDF/UA human-judgement conditions, begin in the recorded default state for the selected PDF/UA human-judgement conditions target before this action; preserve the exact content, account, platform and configuration used.
Tool or command
In document-pdf, Use a qualified PDF/UA checker whose version and condition manifest are frozen, then inspect every required manually evaluated condition in Acrobat Pro or an equivalent tag-tree and content-order inspection tool.
Record
Selected ISO part, matching protocol/version and every condition outcome with no silent omission.
Pass
Record passed for the PDF/UA human-judgement conditions scenario named Export the condition manifest, checker report, manual review record, exception rationale and final decision only when the evidence (Selected ISO part, matching protocol/version and every condition outcome with no silent omission.) supports: An independent reviewer can reconcile every protocol result to the exact PDF and report claim.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the PDF/UA human-judgement conditions scenario named Export the condition manifest, checker report, manual review record, exception rationale and final decision, the recorded observation for the target is inconsistent with the required result: An independent reviewer can reconcile every protocol result to the exact PDF and report claim.
Not applicable
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat the affected protocol conditions after remediation and reconcile changed machine results with all related human checks against the same file checksum. Preserve the first PDF/UA human-judgement conditions observation when repeating.
Limitations
This scenario records the action named Export the condition manifest, checker report, manual review record, exception rationale and final decision for PDF/UA human-judgement conditions in document-pdf. 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 PDF/UA human-judgement conditions: Confirm the PDF version, PDF/UA identifier and selected ISO part before running any protocol. Never apply a PDF/UA-1 Matterhorn result to PDF/UA-2.
Record this step

Step 6

Repeat material variations and recovery

Purpose: For PDF/UA human-judgement conditions, execute the named scenario: Repeat material variations and recovery. Target: The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions. 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: A checker or mismatched protocol may produce an unsupported PDF/UA claim while material barriers remain. This scenario isolates that risk in the action named Repeat material variations and recovery.

Repeat the PDF/UA human-judgement conditions 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 PDF/UA human-judgement conditions 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
The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
Required state
For PDF/UA human-judgement conditions: 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 PDF/UA human-judgement conditions, 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 PDF/UA human-judgement conditions 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 PDF/UA human-judgement conditions 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
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
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 PDF/UA human-judgement conditions 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 PDF/UA human-judgement conditions in document-pdf. 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 PDF/UA human-judgement conditions, 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

Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.

Failed

An applicable PDF/UA human-judgement conditions target has a reproducible material barrier against one or more stated expectations; identify the exact expectation, state and evidence.

Not applicable
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.
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.1.1 secondary · partial

    This PDF/UA protocol review observes PDF/UA human-judgement conditions in the recorded document-pdf environment. Use the linked WCAG 1.1.1 conformance procedure to evaluate all normative parts of WCAG 1.1.1 across the declared scope.

  • W3C-WCAG22 · 1.3.1 secondary · partial

    This PDF/UA protocol review observes PDF/UA human-judgement conditions in the recorded document-pdf 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 · 1.3.2 secondary · partial

    This PDF/UA protocol review observes PDF/UA human-judgement conditions in the recorded document-pdf environment. Use the linked WCAG 1.3.2 conformance procedure to evaluate all normative parts of WCAG 1.3.2 across the declared scope.

  • W3C-WCAG22 · 2.1.1 secondary · partial

    This PDF/UA protocol review observes PDF/UA human-judgement conditions in the recorded document-pdf environment. Use the linked WCAG 2.1.1 conformance procedure to evaluate all normative parts of WCAG 2.1.1 across the declared scope.

  • W3C-WCAG22 · 4.1.2 secondary · partial

    This PDF/UA protocol review observes PDF/UA human-judgement conditions in the recorded document-pdf environment. Use the linked WCAG 4.1.2 conformance procedure to evaluate all normative parts of WCAG 4.1.2 across the declared scope.

  • W3C-WCAG2ICT · W3C-WCAG2ICT advisory · supporting

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

  • W3C-PDF-TECHNIQUES · W3C-PDF-TECHNIQUES advisory · supporting

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

  • PDFASSOC-MATTERHORN-1.1 · PDFASSOC-MATTERHORN-1.1 advisory · supporting

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

  • PDFASSOC-PDFUA · PDFASSOC-PDFUA 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.

  • ISO-14289-1-2014 · ISO 14289-1:2014 conformance · partial

    The procedure alone is not complete ISO 14289-1 conformance evidence and supplies no PDF/UA-2 evidence.

Supporting and advisory guidance

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

Evidence specification
  • File integrity

    Immutable PDF SHA-256 checksum, PDF version, PDF/UA identifier and toolchain.

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

  • Protocol manifest

    Selected ISO part, matching protocol/version and every condition outcome with no silent omission.

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

  • Document structure

    Tag tree, reading order, semantics and human-judgement evidence linked to page/object.

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

  • Functional record

    Viewer, keyboard, reflow and real assistive-technology evidence where applicable.

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

Worked example and outcome calibration

A11Y-PDFUA-002-WORKED-001: representative worked example

Context: Representative synthetic example for PDF/UA human-judgement conditions on a fictional, version-frozen product target; no client or participant execution occurred.

Inspected: The tester follows S2 (Freeze the PDF identity, tools and protocol) using the target, required state, tool and repeat rule stated in this procedure.

Observed output: After the tester completes the PDF/UA human-judgement conditions scenario named Freeze the PDF identity, tools and protocol, the recorded observation for the target is inconsistent with the required result: The exact immutable artifact, claim and toolchain are reproducible.

Evidence:

  • example-evidence-001: target and state record for The exact PDF/UA protocol conditions and manual checks relevant to PDF/UA human-judgement conditions.
  • example-evidence-002: contemporaneous observation from the named method — Immutable PDF SHA-256 checksum, PDF version, PDF/UA identifier and toolchain.
  • 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 exact immutable artifact, claim and toolchain are reproducible. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.

Decision: failed

Finding: A11Y-PDFUA-002-example-finding-001 — PDF/UA human-judgement conditions: expected result is not demonstrated. The represented barrier may affect People who depend on reliable PDF semantics, navigation, input, reflow, speech or braille output.

Remediation: Change the represented target or process so it demonstrates this result: The exact immutable artifact, claim and toolchain are 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 PDF/UA human-judgement conditions 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-pdf, the selected PDF/UA human-judgement conditions target completes the recorded action and meets this expectation: Human-judgement decisions identify the target object/page, rationale and evidence and are not replaced by checker success.

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

Failed
An applicable PDF/UA human-judgement conditions 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
No immutable PDF with the required PDF version and selected PDF/UA part exists in the frozen scope.

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

Cannot tell
The PDF/UA human-judgement conditions 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 PDF/UA human-judgement conditions 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

Follow the named external protocol and record every required condition. Do not infer full protocol coverage from a partial checker result.

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.

  • PDF/UA-1 and PDF/UA-2 are separate standards. Checker success and Matterhorn Protocol 1.1 do not establish PDF/UA-2 conformance.
  • 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-001
  • A11Y-WCAG-007
  • A11Y-WCAG-008
  • A11Y-WCAG-021
  • A11Y-WCAG-054
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.1.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.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 1.3.2. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 2.1.1. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 4.1.2. 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.1.1, SC 1.3.1, SC 1.3.2, SC 2.1.1, SC 4.1.2
Execution
Manual test with tool support
Catalogue version
2026.08.27-rc.9