diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html
index 79bde0626..2f9270307 100644
--- a/app/templates/views/accessibility_statement.html
+++ b/app/templates/views/accessibility_statement.html
@@ -42,7 +42,7 @@
     <li>keyboard-only and voice activation users cannot focus on the table we use to show CSV data</li>
     <li>screen reader users may find the process of moving templates and folders confusing</li>
     <li>some pages have links to PDF documents, and these PDFs are not fully accessible</li>
-    <li>Screenreader users may find it confusing that a specific part of some pages is focused when they load.</li>
+    <li>screen readers users may be disorientated when pages load with the focus on a specific area</li>
     <li>Status page thing</li>
   </ul>
 
@@ -111,7 +111,11 @@
   </p>
 
   <p class="govuk-body">
-    Screenreader users may find it confusing that a specific part of some pages is focused when they load. This fails <a class="govuk-link" href="https://www.w3.org/TR/WCAG21/#focus-order">WCAG 2.4.3 success criteria (Focus Order)</a>. We plan to fix this by October 2020.
+    Screen reader users may find it confusing that a specific part of some pages is focused when they load. This fails <a class="govuk-link" href="https://www.w3.org/TR/WCAG21/#focus-order">WCAG 2.4.3 success criteria (Focus Order)</a>. We plan to fix this by October 2020.
+  </p>
+
+  <p class="govuk-body">
+    We plan to address these issues by March 2021.
   </p>
 
   <h3 class="heading-small">
@@ -119,19 +123,10 @@
   </h3>
 
   <p class="govuk-body">
-    Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion. We provide the information contained in these PDFs in an accessible HTML format.
-  </p>
+    Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion.</p>
 
   <p class="govuk-body">
-    Some of our PDFs are essential to providing our services. For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative.
-  </p>
-
-  <p class="govuk-body">
-    The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix [example of non-essential document].
-  </p>
-
-  <p class="govuk-body">
-    Any new PDFs or Word documents we publish will meet accessibility standards.
+    For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative.
   </p>
 
   <h3 class="heading-small">
@@ -146,6 +141,34 @@
     The JAWS and NVDA screen readers announce extra spaces in emails when viewed in Microsoft Outlook.
   </p>
 
+  <p class="govuk-body">
+    We plan to work with screen reader and email client suppliers to fix the email issues in 2021.
+  </p>
+
+  <h3 class="heading-small">
+    Status page
+  </h3>
+
+  <p class="govuk-body">
+    The following content on the Notify status page is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard:
+  </p>
+    
+  <ul class="govuk-list govuk-list--bullet">
+    <li>an incorrect heading hierarchy which fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
+    <li>missing level 1 headings (users may not be able to accurately determine the structure of content on the page)</li>
+    <li>our status incident page is missing the main heading and the status home page has an incorrect heading hierarchy – this fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
+    <li>our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – tThis fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
+    <li>our status page subscribe to updates form fields do not contain an explicit label – this fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
+    <li>our status page subscribe to updates forms do not indicate to users that they are expandable or collapsible – this fails WCAG 2.1A 4.1.2 success criterion (Name, Role, Value)</li>
+    <li>our status page subscribe to updates forms contain some text that does not meet the minimum colour contrast requirements – this fails WCAG 2.1AA 1.4.3 success criterion (Contrast, Minimum)</li>
+    <li>our status page subscribe to updates form close link (x) is not descriptive enough for some users to determine its function or purpose – this fails WCAG 2.1A 2.4.4 success criterion (Link Purpose, In Context)</li>
+    <li>our status page subscribe to updates forms, when submitted with incorrect data, do not inform screen reader users of the error message when it becomes available – this fails WCAG 2.1AA 4.1.3 success criterion (Status Messages)</li>
+  </ul>
+
+  <p class="govuk-body">
+    We plan to have the status page issues addressed by the current supplier or move to an alternative supplier in 2021.
+  </p>
+
   <h2 class="heading-medium">
     How we tested this service
   </h2>