Skip to content

April price changes and accessibility statement fixes#99

Merged
jakecosgrove merged 5 commits intomainfrom
pricing-and-accessibility-statement-fixes
Apr 1, 2025
Merged

April price changes and accessibility statement fixes#99
jakecosgrove merged 5 commits intomainfrom
pricing-and-accessibility-statement-fixes

Conversation

@jakecosgrove
Copy link
Copy Markdown
Contributor

@jakecosgrove jakecosgrove commented Mar 24, 2025

Description

In this PR:

  • removed warning of price increase on Tuesday 1 April 2025 in all places
  • changed letter prices for 1st and 2nd class in /pricing/letters
  • changed pricing of letters and text messages on landing page and /pricing
  • changed pricing of text messages to 2.33p in /pricing/text-messages
  • fixed /sitemap permalink
  • removed items from accessibility statement that have been fixed and merged

Context

NHS Notify's prices are changing on Tuesday 1 April 2025. We need to have up to date pricing on the day that our prices change so new or existing users do not query any discrepancies.

Non-accessible content in the accessibility statement is being prioritised and fixed over time. Once these items are fixed, we can remove them from the accessibility statement. Some items have been fixed, so need removing.

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

- changed pricing of text messages to 2.33p
- fixed sitemap permalink
- removed items from accessibility statement that have been fixed and merged
@jakecosgrove jakecosgrove requested a review from a team as a code owner March 24, 2025 15:54
Comment thread docs/pages/sitemap.html
@emmagifford
Copy link
Copy Markdown
Contributor

2i checks complete:

  • holding text about price increases removed from 3 pages -compared letter price changes for 1st and 2nd class in /pricing/letters against the pricing updates email - all correct
  • compared text message price change in /pricing/text-messages against price update email - correct
  • can see letter and text message pricing has been correctly updated on /pricing
  • can see the letter and text message pricing cards on the landing page have been correctly updated
  • the 2 issues removed from accessibility statement are currently in the devs' approval column and Mark commented that they're ready to be merged so this should be accurate by Monday
  • asked Jake to change '1 text messages' to '1 text message' in the tables on /pricing/text-messages to remove unnecessary plurals - this looks fine now
  • the updated sitemap permalink works fine

Happy to approve but just adding this as a comment rather than an approval as the content isn't ready to go live yet.

This is now ready to be approved by Alex or any other web CMS approver on Monday 31 March, ready for the price changes on 1 April. (Jake and I are both on leave that day.)

@alexcolbeck1 alexcolbeck1 self-requested a review March 25, 2025 15:37
@jakecosgrove jakecosgrove merged commit 67fda8f into main Apr 1, 2025
25 checks passed
@jakecosgrove jakecosgrove deleted the pricing-and-accessibility-statement-fixes branch April 1, 2025 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants