From cd61479a4f0255c91dbf1686e4c4f653b329a2b2 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Tue, 22 Sep 2020 20:47:05 +0100 Subject: [PATCH] Update PDF information --- app/templates/views/accessibility_statement.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 87bf3016e..120cdddfe 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -41,7 +41,7 @@
  • low vision users cannot access the table we use to show CSV data when viewed at high zoom
  • keyboard-only and voice activation users cannot focus on the table we use to show CSV data
  • screen reader users may find the process of moving templates and folders confusing
    • -
  • some pages have links to PDF documents, and these PDFs are not fully accessible
    • +
  • one page links to a PDF document that is not fully accessible
  • screen readers users may be disorientated when pages load with the focus on a specific area
  • the Notify status page has several accessibility issues
    • @@ -123,10 +123,10 @@

    - 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.

    + One page links to a PDF documents that is not fully accessible. This is not a fail under any WCAG 2.1 success criterion.

    - 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. + We provide a written description of the information in the PDF on an HTML page as an accessible alternative.