Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document assistive tech support in FE Readme #800

Merged
merged 2 commits into from
Jun 15, 2018

Conversation

hannalaakso
Copy link
Member

This sets out the assistive technology that GOV.UK Frontend supports.

In the future, we would like to add guidance about writing accessibility acceptance criteria.

https://trello.com/c/hZD483RS/1030-document-assistive-tech-support-in-fe-readme

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-800 June 15, 2018 13:01 Inactive
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-800 June 15, 2018 13:02 Inactive
Copy link
Member

@36degrees 36degrees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good stuff!

README.md Outdated

In addition, we test that all content is accessible with keyboard only.

We also aim to support high contrast mode for those users who need to adjust browser colours to increase readability. We have in the past tested this by setting custom colours in Firefox (under Preferences), and with the [High Contrast][high-contrast] plugin. Read more about [how users change colours on websites][how-users-change-colours-on-websites].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of minor things with this paragraph…

  • I don't think it's just high contrast mode we support
  • We mention high contrast mode but don't talk about testing with it
  • I think there's reasons that users would override that don't relate to readability (e.g. high constrast gives them migraines).

How about something like…

We aim to support users who adjust or override the colours of websites they visit. We test this by changing colours in Firefox, by enabling 'High Contrast' mode in Windows and by using the High Contrast plugin for Chrome.

README.md Outdated
@@ -77,6 +77,31 @@ include a separate stylesheet in order to support Internet Explorer

[service-manual-browsers]: https://www.gov.uk/service-manual/technology/designing-for-different-browsers-and-devices#browsers-to-test-in

## Support for assistive technology
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given we have a heading called 'Browser support' can we follow form and go with 'Assistive technology support'?

README.md Outdated
GOV.UK Frontend will allow you to build services that comply with the [guidance
in the Service Manual][service-manual-assistive-technologies].

Currently, GOV.UK Frontend officially supports the following assistive technology:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should probably be 'technologies'

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-800 June 15, 2018 13:44 Inactive
Copy link
Member

@36degrees 36degrees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ace 👏

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-800 June 15, 2018 13:50 Inactive
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-800 June 15, 2018 13:53 Inactive
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-800 June 15, 2018 13:55 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants