From fb112bd5f76c82a11558951091393b961571e905 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 23 Sep 2020 11:27:31 +0100 Subject: [PATCH] Fix typo in status page issue Co-authored-by: Chris Hill-Scott --- app/templates/views/accessibility_statement.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index cd867b5c0..781674de4 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -148,7 +148,7 @@
  • an incorrect heading hierarchy which fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)
  • missing level 1 headings (users may not be able to accurately determine the structure of content on the page)
  • 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)
    • -
  • 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)
    • +
  • our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)
  • 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)
  • 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)
  • 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)