diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html
index 706fb89a6..36191949b 100644
--- a/app/templates/views/accessibility_statement.html
+++ b/app/templates/views/accessibility_statement.html
@@ -99,18 +99,18 @@
Non compliance with the accessibility regulations
- The following content on the Notify website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard:
+ The following content on the Notify website is not compliant with the WCAG version 2.1 AA standard:
-
- The (before HTML) code for the ‘upload a file’ button may cause issues for assistive technology users. This fails success criterion 1.3.1: info and relationships. We plan to fix this by [TODO date].
+ The (before HTML) code for the ‘upload a file’ button may cause issues for assistive technology users. This fails success criterion 1.3.1: info and relationships. We plan to fix this by the end of October 2021.
-
- The JAWS and NVDA screen readers do not announce the ‘copy text to clipboard’ component. This fails success criterion 4.1.3: status messages. We plan to fix this by [TODO date].
+ The JAWS and NVDA screen readers do not announce the ‘copy to clipboard’ button. This fails success criterion 4.1.3: status messages. We plan to fix this by the end of October 2021.
-
- Some icons do not appear when using high contrast mode on Windows. This fails success criterion 1.4.8: visual presentation. We plan to fix this by [TODO date].
+ Some icons do not appear when using high contrast mode on Windows. This fails success criterion 1.4.8: visual presentation. We plan to fix this by the end of October 2021.
@@ -122,19 +122,19 @@
-
- The JAWS screen reader announces template folder page headings as multiple sentences. We plan to fix this by [TODO date].
+ The JAWS screen reader announces template folder page headings as multiple sentences. We hope to be able to fix this by the end of 2021.
-
- Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We plan to fix this by [TODO date].
+ Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We hope to be able to fix this by the end of 2021.
-
- The way we label the different regions of our pages is confusing for screen reader users. We plan to fix this by [TODO date].
+ The way we label the different regions of our pages is confusing for screen reader users. We plan to fix this by the end of October 2021.
-
- Choosing the date and time you want to send a message using a screen reader can be confusing. We plan to fix this by [TODO date].
+ Choosing the date and time you want to send a message using a screen reader can be confusing. We hope to be able to fix this by the end of 2021.
-
- Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We plan to fix this by [TODO date].
+ Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We hope to be able to fix this by the end of 2021.
@@ -158,7 +158,7 @@
- We’ll continue to investigate the cause of this issue and, if possible, fix it by [TODO date].
+ We’ll continue to investigate the cause of this issue and, if possible, fix it by the end of 2021.