search

alphagov / govuk-design-system

One place for service teams to find styles, components and patterns for designing government services.
https://www.gov.uk/design-system
MIT License
512 stars 232 forks source link

WCAG 2.2: Contact a department or service team ‖ Consistent Help #2882

Closed querkmachine closed 1 year ago

querkmachine commented 1 year ago

What

Update our guidance on how to contact departments and service teams to emphasise that if contact information is present on multiple pages, the types of contact information should be listed in a consistent order across all of those pages.

This is largely a usability suggestion and may not be necessary for WCAG compliance.

Resources

Why

The new WCAG 2.2 Level A criterion 'Consistent Help' says:

If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user:

  • Human contact details;
  • Human contact mechanism;
  • Self-help option;
  • A fully automated contact mechanism.

Although the intent of the criterion is that the contact information itself is consistently ordered with respect to the rest of the page (i.e. a help link is always in the same place in the footer, as described in #2871) we can go beyond this by advising that teams provide this information in a consistent order every time it appears.

For example, if a service has three contact mechanisms—phone, email address, post—these should be listed in the same order and format on all pages where it appears, such as the service start page, support pages, contact page, etc.

Who needs to work on this

Who needs to review this

Done when

dav-idc commented 1 year ago

This issue appears to already be covered by the existing planned guidance updates in the WCAG 2.2 content updates main guidance doc.

Here's the existing section that covers 'Contact a department or service team' and consistent help: https://docs.google.com/document/d/1nIxIKgVUheC8zvVdqWIcqtVPCl7oTN4hv11R9rDwdvM/edit#heading=h.arawptfmd6cg

As a result I'm closing this issue as a duplicate of the main WCAG 2.2 guidance issue: