Accessibility Test Cases

A11Y-PDFUA-001

PDF/UA-1 Matterhorn 1.1 complete protocol

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

Assess one checksum-identified PDF/UA-1 file against Matterhorn Protocol 1.1 and required manual functional checks.

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

Assess one checksum-identified PDF/UA-1 file against Matterhorn Protocol 1.1 and required manual functional checks.

What this result means: This PDF/UA-1 Matterhorn 1.1 complete protocol procedure determines whether the recorded targets meet WCAG 1.1.1, WCAG 1.3.1, WCAG 1.3.2, WCAG 2.1.1, WCAG 4.1.2 on document-pdf in the tested states. A broader conformance decision must also account for every applicable target in the declared scope, complete processes, accessibility-supported use and the other WCAG conformance requirements.

Why it matters

Detect PDF/UA-1 failures and functional accessibility barriers in the exact immutable PDF artifact. People most likely affected: people using screen readers, refreshable braille, keyboard access, reflow or magnification with PDF documents. A structurally invalid or functionally unusable PDF can expose the wrong reading order, omit content, prevent navigation or make forms and controls unusable. 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 only to PDF/UA-1 assessment. Do not use this procedure or its evidence for a PDF/UA-2 claim.

Confirm before starting

Mark it not applicable only when

Exceptions

Exceptions and applicability are decided condition by condition under ISO 14289-1:2014 and Matterhorn Protocol 1.1. This wrapper procedure does not invent an additional global exception.

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

  • All 136 Matterhorn Protocol 1.1 failure conditions for the exact file.
  • The file's manual tag-tree, reading-order, keyboard, reflow and real assistive-technology behaviour.
  • Every page, annotation, form state and unique tagged structure required by the protocol.
  • Keyboard, reflow and real screen-reader reading for applicable content and complete processes.

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

Freeze the PDF and claimed standard

Purpose: Bind every result to one immutable document and one PDF/UA part.

User impact: Changed files or ambiguous claims invalidate otherwise useful evidence.

Calculate SHA-256 and record filename, bytes, PDF version, PDF/UA identifier and authoring/export/remediation tool versions. Stop if the checksum changes.

Expected result

The artifact and PDF/UA-1 claim are unique and reproducible.

Failure observation

The checksum is absent, changes during testing or the file declares another/ambiguous PDF/UA part.

Setup, evidence and decision guidance
Target
One final PDF file.
Required state
Final candidate before any checker or manual run.
Tool or command
SHA-256 utility and PDF properties inspector.
Record
File ID, checksum, size, metadata extract and toolchain.
Pass
The immutable file is identified as the intended PDF/UA-1 candidate.
Fail
No stable artifact or applicable claim can be established.
Not applicable
The approved plan does not require PDF/UA-1 assessment for this document.
Blocked
The final file or required metadata cannot be accessed.
Repeat or recover
Obtain the final file; never overwrite evidence from an earlier checksum.
Limitations
This scenario identifies the subject and claim only.
If you are new to this test
Obtain the final file; never overwrite evidence from an earlier checksum.
Record this step

Step 2

Record the protocol and licensed references

Purpose: Use the correct Matterhorn and ISO references for PDF/UA-1.

User impact: Applying the wrong protocol can produce a misleading conformance decision.

Record protocol/version, checker/version, applicable ISO part, viewer versions and qualified reviewer role. Confirm none targets PDF/UA-2 only.

Expected result

Every method is applicable to PDF/UA-1 and versioned.

Failure observation

A required reference is missing, unlicensed for the responsible reviewer or applies to a different PDF/UA part.

Setup, evidence and decision guidance
Target
The assessment method and reviewer reference set.
Required state
PDF checksum fixed in S1.
Tool or command
Matterhorn Protocol 1.1 (April 2021), qualified checker documentation and authorised access to ISO 14289-1:2014.
Record
Protocol IDs/versions, access confirmation, checker/viewer versions and reviewer role.
Pass
The correct reference set is available.
Fail
The method set is incomplete or mismatched.
Not applicable
PDF/UA-1 assessment is outside the agreed plan.
Blocked
Required licensed standard access or qualified review authority is unavailable.
Repeat or recover
Mark blocked until authorised access exists; do not infer ISO requirements from summaries.
Limitations
Repository guidance does not reproduce or replace the licensed ISO standard.
If you are new to this test
Mark blocked until authorised access exists; do not infer ISO requirements from summaries.
Record this step

Step 3

Run the checker and preserve raw output

Purpose: Collect repeatable machine evidence without treating it as the complete decision.

User impact: Checker-only conclusions can miss human-judgement and functional failures.

Run the PDF/UA-1 profile once. Export the unedited report and record profile, timestamp and result counts.

Expected result

Machine-testable findings are bound to the file and preserved without reinterpretation.

Failure observation

The checker cannot parse the file, uses another profile or output is edited/lost.

Setup, evidence and decision guidance
Target
The checksum-frozen PDF.
Required state
Unmodified file; checker reset to default PDF/UA-1 profile.
Tool or command
Named qualified PDF/UA checker and exact version.
Record
Raw checker report, log, profile, timestamp, version and checksum.
Pass
A complete raw report is preserved; individual condition outcomes remain to be reconciled.
Fail
The machine run is invalid or unavailable; do not infer protocol outcomes.
Not applicable
No machine-testable condition applies only when the official protocol explicitly says so.
Blocked
Checker licence, execution or export is unavailable.
Repeat or recover
Repair the checker environment and rerun against the same checksum.
Limitations
A checker pass is supporting evidence and never a complete PDF/UA-1 decision.
If you are new to this test
Repair the checker environment and rerun against the same checksum.
Record this step

Step 4

Complete the 136-condition manifest

Purpose: Ensure every Matterhorn 1.1 condition has one traceable outcome and permitted method.

User impact: Missing conditions create silent gaps in the conformance record.

Record one passed, failed, inapplicable or cantTell outcome for each unique condition ID. Use the protocol method class; explain every inapplicable and cantTell outcome and preserve both no-specific-test conditions.

Expected result

The manifest has 136 unique IDs, valid methods and complete rationales.

Failure observation

Any ID is missing/duplicated, uses an unsupported method or lacks required rationale.

Setup, evidence and decision guidance
Target
All 136 unique Matterhorn 1.1 condition IDs.
Required state
Protocol/version fixed; raw checker output available for machine conditions.
Tool or command
Condition manifest, Matterhorn Protocol 1.1 and qualified inspection tools.
Record
Completed manifest, method per condition, evidence links and rationales.
Pass
All 136 conditions are accounted for and no failed/cantTell condition remains for a pass.
Fail
A failed condition prevents pass; a cantTell condition prevents a conclusive pass.
Not applicable
Only individual conditions explicitly inapplicable under the protocol may be marked so.
Blocked
A required manual judgement or reference cannot be obtained.
Repeat or recover
Resolve condition-level blockers individually; do not bulk-mark conditions passed or inapplicable.
Limitations
Condition completion demonstrates protocol coverage, not functional usability or WCAG conformance.
If you are new to this test
Resolve condition-level blockers individually; do not bulk-mark conditions passed or inapplicable.
Record this step

Step 5

Inspect structure and reading order

Purpose: Reconcile machine results with semantic tags and logical reading sequence.

User impact: Incorrect structure or order can make a document incoherent to assistive technology.

Inspect one structure type at a time. Compare tags, nesting, content association and logical order with the rendered page; record discrepancies against the relevant condition IDs.

Expected result

Structures and reading order convey the intended relationships without untagged meaningful content.

Failure observation

Tags are missing/misnested, content is associated incorrectly or logical order changes meaning.

Setup, evidence and decision guidance
Target
Each unique heading, list, table, figure and content-order pattern in the sample.
Required state
PDF open in a tagged-structure inspector at the same checksum.
Tool or command
Qualified PDF tag-tree inspector and content/reading-order views.
Record
Tag-tree extracts, page/content references, order comparison and condition links.
Pass
Every selected unique structure supports its intended semantics and order.
Fail
Any material structural or order failure is recorded against its condition.
Not applicable
A structure type is absent from the document.
Blocked
The tag tree cannot be inspected with the authorised tool.
Repeat or recover
Try a second qualified inspector for display problems; preserve discrepancies rather than choosing the favourable view.
Limitations
Sampling unique structures does not waive protocol conditions that require full-file checks.
If you are new to this test
Try a second qualified inspector for display problems; preserve discrepancies rather than choosing the favourable view.
Record this step

Step 6

Inspect alternate descriptions and metadata

Purpose: Check non-text alternatives, document language, title and other human-judgement metadata.

User impact: Missing or inaccurate descriptions and metadata remove meaning or orientation.

Review each unique figure's alternative or marked-artifact decision, then inspect title, language and relevant metadata. Record purpose-based judgements separately.

Expected result

Alternatives and metadata are present, accurate and appropriate to purpose.

Failure observation

Meaningful content lacks an equivalent, decorative content is exposed unnecessarily, or required metadata is absent/inaccurate.

Setup, evidence and decision guidance
Target
Every unique figure type plus document-level metadata.
Required state
Same immutable PDF; visual content and business purpose available to the reviewer.
Tool or command
Qualified PDF inspector plus content-owner context when purpose is ambiguous.
Record
Figure/page IDs, alternative text, purpose rationale, metadata extract and condition links.
Pass
Every inspected item meets its relevant condition.
Fail
Any inspected item produces the failure observation.
Not applicable
A specific content type is absent; document-level metadata checks still apply.
Blocked
Purpose cannot be determined from available product-owner information.
Repeat or recover
Use cantTell for the affected item and request content-owner clarification.
Limitations
This scenario does not establish equivalence for uninspected repeated content variants.
If you are new to this test
Use cantTell for the affected item and request content-owner clarification.
Record this step

Step 7

Test forms, links and keyboard operation

Purpose: Confirm interactive document elements can be identified and operated without a pointer.

User impact: Inoperable fields or links prevent task completion even when tags exist.

Tab through interactive elements, activate links safely, enter synthetic values and submit only to an authorised endpoint. Record names, roles, states, focus order and keyboard results.

Expected result

Interactive elements are perceivable, ordered and operable by keyboard.

Failure observation

An element is skipped, unnamed, misleading, out of order or cannot be operated without a pointer.

Setup, evidence and decision guidance
Target
Every unique form control, annotation and link behaviour.
Required state
Document open in the declared viewer; focus at document start.
Tool or command
Physical keyboard and recorded PDF viewer; screen-reader run is a separate real-platform evidence item.
Record
Key sequence, viewer/version, focus order, element properties and safe activation result.
Pass
All selected interactive elements meet the observation.
Fail
Any applicable element produces the failure observation.
Not applicable
The PDF contains no interactive elements.
Blocked
Security policy or endpoint restrictions prevent safe activation.
Repeat or recover
Use a non-destructive target or authorised staging copy; otherwise mark only activation blocked.
Limitations
Keyboard results do not replace a required real screen-reader execution.
If you are new to this test
Use a non-destructive target or authorised staging copy; otherwise mark only activation blocked.
Record this step

Step 8

Reconcile and issue the bounded decision

Purpose: Produce a reviewable PDF/UA-1 result without cross-standard inference.

User impact: Blended or overstated conclusions mislead clients and procurement reviewers.

Reconcile conflicts one condition at a time. Record PDF/UA-1, WCAG-related and functional observations separately; state that no PDF/UA-2 evidence or claim is produced.

Expected result

Every conclusion traces to checksum, condition or manual observation and unresolved items remain visible.

Failure observation

Evidence is missing, conclusions conflict silently, or the report converts functional success into an unsupported standards claim.

Setup, evidence and decision guidance
Target
Condition manifest, raw checker output and manual evidence for the frozen PDF.
Required state
All planned scenarios complete or explicitly blocked.
Tool or command
Evidence register and independent technical review worksheet.
Record
Final condition counts, conflict log, evidence map, bounded decision and limitations.
Pass
All conditions pass with complete evidence and no unresolved conflict for a PDF/UA-1 pass.
Fail
Any failed condition produces a non-conforming result; cantTell/blocked prevents a conclusive pass.
Not applicable
The assessment was legitimately removed from scope before execution; report the scope limitation.
Blocked
Required qualified review or licensed reference is unavailable.
Repeat or recover
Return unresolved conflicts to the relevant scenario and preserve the current decision state.
Limitations
This decision applies only to the checksum-frozen file and PDF/UA-1; it is not a legal opinion or proof of universal usability.
If you are new to this test
Return unresolved conflicts to the relevant scenario and preserve the current decision state.
Record this step

Decide

How to decide

Passed

All 136 Matterhorn Protocol 1.1 conditions are accounted for with allowed outcomes and methods, no condition is failed or cantTell, required manual PDF/UA-1 checks support the conclusion, and the result is tied to the exact PDF checksum.

Failed

At least one applicable PDF/UA-1 condition fails, or manual evidence identifies a PDF/UA-1 failure for the checksum-identified file.

Not applicable
The subject is not PDF/UA-1; PDF/UA-2 is specifically inapplicable to this procedure and requires a different assessment.
Cannot tell
A required interpretive condition, licensed-standard interpretation or checker/manual discrepancy cannot be resolved.
Not tested
The target is applicable, but a required state, environment, action or evidence item was not completed.
Aggregation and reporting boundaries

Aggregation: All 136 condition outcomes and manual findings remain visible. Any failed or cantTell condition prevents a passed aggregate; untested conditions make the execution incomplete.

WCAG decision: PDF/UA-1, WCAG and functional-accessibility decisions remain separate. No PDF/UA-2 decision may be inferred from this procedure.

Automation: A passed checker report does not prove that all interpretive conditions, functional behaviour or WCAG requirements pass.

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

WCAG report decisions

These report-level decisions are separate from the target outcome and require complete declared-scope evidence.

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 Run the PDF/UA-1 Matterhorn 1.1 protocol 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 Run the PDF/UA-1 Matterhorn 1.1 protocol 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 Run the PDF/UA-1 Matterhorn 1.1 protocol 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 Run the PDF/UA-1 Matterhorn 1.1 protocol 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 Run the PDF/UA-1 Matterhorn 1.1 protocol 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 public catalogue cannot reproduce the licensed ISO text. Matterhorn 1.1 and checker evidence support but do not alone establish complete PDF/UA-1 conformance.

Supporting and advisory guidance

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

Required external protocol

Use PDFASSOC-MATTERHORN-1.1 version 1.1 and record all 136 required condition results.

Attach 136 unique condition results identified by the official Matterhorn index. Inapplicable and cantTell require rationale; any failed or cantTell condition prevents a pass.

Evidence specification
  • Immutable file identity

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

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Protocol manifest

    All 136 Matterhorn 1.1 condition IDs, methods, outcomes, rationales and evidence references.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Checker export

    Qualified checker/version, configuration and unedited exported report.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Manual pdf review

    Tag-tree, content/reading order, semantics, forms, annotations and metadata evidence.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

  • Functional pdf review

    Viewer, keyboard, reflow and exact real assistive-technology output for unique structures and processes.

    Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.

Worked example and outcome calibration

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

Context: Synthetic two-page procurement decision PDF, checksum `example-sha256-4b83…`, represented as a training fixture rather than a certified document.

Inspected: PDF/UA-1 identification, checker report, 136-condition manifest, heading/list/table tags, reading order, figure alternative and keyboard link operation.

Observed output: The example checker passed machine conditions, but manual inspection found table header cells tagged as data cells and one meaningful chart marked as an artifact.

Evidence:

  • EVD-REF-013 fixture checksum and metadata
  • EVD-REF-014 representative checker report
  • EVD-REF-015 condition manifest
  • EVD-REF-016 tag-tree extracts

Tester reasoning: Machine success cannot override human-judgement failures. The two structural failures prevent a PDF/UA-1 pass for the represented checksum.

Decision: failed

Finding: FND-REF-004 — Procurement table headers and chart semantics are incorrect. Screen-reader users may lose table relationships and the chart's decision context.

Remediation: Retag column/row headers with correct scope/associations, expose the chart as a Figure with an equivalent concise description, regenerate the PDF and create a new checksum-bound execution.

Reviewer feedback: Reviewer separated the table and figure condition references, retained one combined remediation release because both arise from the export template, and removed a WCAG conformance claim.

Final client wording: The represented PDF does not meet the sampled PDF/UA-1 conditions: table headers are not identified programmatically and a meaningful chart is marked as an artifact. Correct the source template, regenerate the PDF and repeat the complete checksum-bound protocol.

Retest: RT-REF-005: representative remediated fixture received a new checksum; the affected manual conditions pass, but no certified PDF/UA claim is made.

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
The immutable PDF has 136 reconciled Matterhorn 1.1 condition results with no failed or cantTell outcome, and required manual checks support the PDF/UA-1 conclusion.

This supports a competently reviewed PDF/UA-1 procedure result for the recorded file and environment only; organisational approval and any WCAG claim remain separate.

Failed
The checker passes its covered conditions, but manual tag-tree inspection finds an applicable heading condition is violated.

Manual evidence identifies a failure; the checker does not override it.

Not applicable
The file identifies PDF/UA-2 and PDF 2.0, not PDF/UA-1.

This PDF/UA-1 procedure is inapplicable; its evidence cannot be reused for PDF/UA-2.

Cannot tell
An interpretive condition conflicts with the checker output and a competent review cannot resolve it from the licensed-standard evidence.

The unresolved material dispute prevents a passed result.

Not tested
Only machine-testable checker conditions were run; interpretive and functional checks are incomplete.

A partial checker run is untested for the complete procedure.

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 — Replaced migrated boilerplate with a case-specific reference implementation and completed generated-file integrity review.
  5. 2026.08.27-rc.9 — Rewritten as an atomic professional-delivery flagship with component effort guidance and a complete representative worked example.
  6. 2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.

Review decision: pending. Open issues: Execution requires authorised access to ISO 14289-1:2014, a qualified PDF/UA checker, the declared PDF applications and real assistive technology where required. A distinct competent review must retain unresolved interpretation as cantTell.; No checker report, PDF checksum or real PDF execution is claimed by this catalogue entry.

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