You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The colour combination of #D8DDE0 background and #4C6272 foreground fails AAA at small font sizes (Based on https://webaim.org/resources/contrastchecker/). This is in violation of the guidance set out in the NHS service manual.
We should consider picking a darker colour to meet the AAA requirements.
The text was updated successfully, but these errors were encountered:
NHS.UK's Information Architecture team have recently updated the footer to contain links in the same style as the rest of the site. We have also grouped the links logically, making the footer more compliant to the AA standard.
However, this week, we are also iterating the footer to make the links a darker blue (#003087 - still an NHS brand guideline colour), the Crown copyright notice a black (#231F20), all with a background of pale grey (#D8DDDF).
In turn, we will feed these colour alterations into relevant components on the frontend and service manual backlogs. But, seeing as the previous footer had different colour treatments for the links, I see no objections to the colour iterations being a permanent fixture of the new footer.
Using the dark blue gives the footer a colour contrast ratio of 8.6, making it AAA compliant.
There is ongoing work to update the header and footer in the frontend library, and part of this will involve updating the footer to the 2nd iteration mentioned above by Brie. I have linked the relevant branch and the current timeline for the corresponding release is the end of August 2023.
The colour combination of #D8DDE0 background and #4C6272 foreground fails AAA at small font sizes (Based on https://webaim.org/resources/contrastchecker/). This is in violation of the guidance set out in the NHS service manual.
We should consider picking a darker colour to meet the AAA requirements.
The text was updated successfully, but these errors were encountered: