As a citizen with special access needs, I'd like to be able to submit an FOI

[garethrees]

No description provided.

[wrightmartin]

Here's the finding from the accessibility review - I understand some of these are related to the template, or even the gov.uk framework so we might decide not to address these here, but to push them upstream

General

• The green (#0aa44c) used for links fails colour contrast check (3.27:1) on a white background. If you darken it slightly (#08863e) it will pass this is part of the Hackney template gem so we can't fix it here Link and Focus colour accessibility #151

• The focus colour (#ffbf47) used for links fails colour contrast when used with the link green (#099846) - suggest we change the focus colour to black and keep the background colour as is this is part of the Hackney template gem so we can't fix it here Link and Focus colour accessibility #151

• There is no landmark role for the page content, suggest adding role=“main” to <div id=“content”> if this is appropriate to address this

Header

• The logo has no alt text this is part of the Hackney template gem so we can't fix it here The logo has no alt text #144

• The breadcrumb trail uses an invalid aria role of ‘breadcrumbs’. This should instead be a label aria-label=“breadcrumb” with a role of role=“navigation"

Footer

• The link colour (#a9cd75) used in the footer fails contrast check on the footer background colour. Lightening it a few steps (#c4dca3) fixes this this is part of the Hackney template gem so we can't fix it here Link and Focus colour accessibility #151

• The focus colour used for links in the footer, combined with the background fails contrast check this is part of the Hackney template gem so we can't fix it here Link and Focus colour accessibility #151

Homepage

• ‘By email’ and ‘by post’ should be h4 elements to maintain document structure

• The focus colour of the ‘start your request’ buttons fails a contrast check Can't reproduce

New request process /foi/request/new

• The sole textfield on the page has a description underneath it, accessibility of this could be enhanced by using the aria-describedby (https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/forms/Basic_form_hints#Describing_with_ARIA) attribute to associate this description with the form element

• The ‘full name’ field uses a descriptive <span> which could also use the aria-describedby attribute Can't do this as the fields are provided by https://github.com/ministryofjustice/govuk_elements_form_builder, I have opened an issue Full Name field should include an aria-describedby attribute #145

• Having the ‘check request’ data inside a table felt clunky when using a screenreader - it’s a stylistic choice but it could be marked up differently, perhaps a definition list or headings and paragraph tags?

• The loading icon would benefit from some accessibility features, most likely role="alertdialog" aria-busy="true" aria-live=“assertive” - then when the loading process has been completed, changing aria-busy to “false” (https://stackoverflow.com/questions/38704467/how-to-label-a-loading-animation-for-wai-aria)

Admin

• On the 'add a curated link' interface the label element for the tag field isn't connected to the actual field This is part of the Taggly plugin, so can't be addressed here On the 'add a curated link' interface the label element for the tag field isn't connected to the actual field #146

[garethrees]

Problems that we can't fix have been extracted out in to independent issues.