Revise accessibility statement for Planning Data Platform

[markrowen]

Updated the accessibility statement to reflect changes in compliance status, audit details, and contact information. Enhanced clarity and specificity regarding accessibility issues and improvements.

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Updated the accessibility statement to reflect changes in compliance status, audit details, and contact information. Enhanced clarity and specificity regarding accessibility issues and improvements.

Related Tickets & Documents

• Ticket Link
• Related Issue #
• Closes #625

QA Instructions, Screenshots, Recordings

Content change only – no testing required.

Added/updated tests?

We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.

• Yes
• No, and this is why: Content review only, no functional change
• I need help with writing tests

[optional] Are there any post deployment tasks we need to perform?

[optional] Are there any dependencies on other PRs or Work?

Summary by CodeRabbit

• Documentation
  • Rewrote and refreshed the Planning Data Platform accessibility statement.
  • Updated the document to reflect WCAG 2.2 AA positioning and specified known accessibility difficulties.
  • Simplified feedback and accessible-format request guidance, including a five-business-day response expectation.
  • Expanded information on ongoing improvements, independent auditing/testing activities, and the latest review dates.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a380c14e-912f-49ef-bece-615818afcc99

📥 Commits

Reviewing files that changed from the base of the PR and between 6b0682c and 86085fb.

📒 Files selected for processing (1)

• application/templates/pages/accessibility-statement.md

🚧 Files skipped from review as they are similar to previous changes (1)

• application/templates/pages/accessibility-statement.md

---

Walkthrough

The accessibility statement is substantially rewritten for the Planning Data Platform, updating WCAG 2.2 AA compliance information, known issues, contact and enforcement guidance, improvement plans, and audit and testing dates.

Changes

Accessibility statement

Layer / File(s)	Summary
Statement scope and accessibility status application/templates/pages/accessibility-statement.md	Updates the introduction, accessibility capabilities, WCAG 2.2 AA compliance framing, and known accessibility limitations.
Non-compliance criteria and scope application/templates/pages/accessibility-statement.md	Replaces the previous criterion details with updated WCAG issues covering structure, controls, maps, contrast, announcements, and reflow.
Contact, improvement, and review information application/templates/pages/accessibility-statement.md	Refreshes contact, reporting, enforcement, improvement programme, independent audit, testing, and statement preparation details.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: revising the Planning Data Platform accessibility statement.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch markrowen-accessibility-statement-update-2026

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@application/templates/pages/accessibility-statement.md`:
- Line 14: Remove the leading whitespace inside the Markdown link in the
accessibility statement so the link label begins immediately with “AbilityNet,”
while preserving the existing URL and surrounding sentence.
- Line 67: Change the “Information, structure and relationships (WCAG 1.3.1)”
heading in the accessibility statement to h3 so it follows the preceding h2
without skipping a heading level.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6a8fa78f-bc51-408d-8a77-348648b9c39c

📥 Commits

Reviewing files that changed from the base of the PR and between 5efb201 and 6b0682c.

📒 Files selected for processing (1)

• application/templates/pages/accessibility-statement.md

[jpherr]

👍