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

Understand the requirements of publishing an accessibility statement #800

Closed
2 tasks done
NickColley opened this issue Feb 20, 2019 · 2 comments
Closed
2 tasks done
Assignees
Labels
accessibility ⚠️ high priority Used by the team when triaging

Comments

@NickColley
Copy link
Contributor

NickColley commented Feb 20, 2019

What

Meet with the accessibility team to understand the requirements of an accessibility statement.

Why

So we publish the right thing.

Who needs to know about this

Amy

Further detail

There may be some strict requirements for the content that is required in a statement which should be considered.

There also is work being done elsewhere in GDS to make a format that can be used by services which we should consider finding out about.

This would be part of the Make sure that the Design System meets WCAG 2.1 epic.

Done when

  • we have understood what the accessibility team recommends services do
  • we understand the requirements of the statement
@NickColley NickColley added the awaiting triage Needs triaging by team label Feb 20, 2019
@timpaul timpaul added accessibility Effort: days ⚠️ high priority Used by the team when triaging and removed awaiting triage Needs triaging by team labels Feb 20, 2019
@kellylee-gds
Copy link
Contributor

@amyhupe @NickColley as we may not be writing the statement straight away, it might be worth breaking this down into smaller stories

@kellylee-gds kellylee-gds changed the title Publish an accessibility statement Understand the requirements of publishing an accessibility statement Mar 12, 2019
@kellylee-gds
Copy link
Contributor

@amyhupe I have broken this down into 2 separate stories. Story to publish the statement can be found here #824. Moving this issue to done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility ⚠️ high priority Used by the team when triaging
Projects
Development

No branches or pull requests

5 participants