We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Meet with the accessibility team to understand the requirements of an accessibility statement.
So we publish the right thing.
Amy
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.
The text was updated successfully, but these errors were encountered:
@amyhupe @NickColley as we may not be writing the statement straight away, it might be worth breaking this down into smaller stories
Sorry, something went wrong.
@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
amyhupe
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: