Updates guidance or accessibility and end-date

[Jandums]

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

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

Description

Revised guidance for accessibility requirements and use of end-dates

Related Tickets & Documents

• Ticket Link Guidance updates: Add content on accessibility and PDFs and content around updating data config#2798
• Related Issue #
• Closes #

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.

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: please replace this line with details on why tests
  have not been included
• 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

• New Features
  • Added a “Meeting accessibility requirements” item to the guidance navigation.
  • Added guidance to publish planning data in open formats (e.g., CSV or GeoJSON) and supporting planning documents as PDFs.
  • Added instructions for maintaining record lifecycles, including updating end dates and requesting removal of incorrectly published records.
• Documentation
  • Clarified how publishing practices support accessibility requirements and compliance.

[coderabbitai]

Walkthrough

The guidance page now explains record maintenance and accessibility publishing requirements. Its secondary navigation includes a link to the new “Meeting accessibility requirements” section.

Changes

Guidance accessibility updates

Layer / File(s)	Summary
Guidance content updates application/templates/pages/guidance/index.md	Adds instructions for updating, ending, or requesting removal of records, plus requirements for publishing planning data and documents in accessible formats.
Guidance navigation entry application/templates/layouts/layout--guidance.html	Adds a secondary navigation link to the new accessibility requirements section.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• digital-land/digital-land.info#501: Updates the same guidance secondary navigation with additional preparation links.
• digital-land/digital-land.info#507: Updates the same guidance navigation and content templates.
• digital-land/digital-land.info#514: Reworks guidance navigation and index content in the same files.

Suggested reviewers: gibahjoe, paris-dp

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and clearly reflects the guidance, accessibility, and end-date updates in the pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2798-Acessibility-Guidance-and-updates

---

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/guidance/index.md`:
- Around line 157-160: Update the guidance’s “associated planning documents”
requirement to specify accessible PDF/A files, provide an open format alongside
them, and complete the required accessibility checks, while preserving the
existing emphasis on open formats and avoiding an unqualified “a PDF”
requirement.
- Around line 155-160: Correct the user-facing wording in the publishing
guidance: change “publish you” to “publish your,” add the missing space in
“format (for example,” and change “you website” to “your website.”

🪄 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: a868ef7a-bac1-43d4-a711-f9abc0f055b6

📥 Commits

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

📒 Files selected for processing (2)

• application/templates/layouts/layout--guidance.html
• application/templates/pages/guidance/index.md

[pooleycodes]

LGTM - Maybe just fix the indentation on the new nav object (the { is pushed way out compared to the others)