-
Notifications
You must be signed in to change notification settings - Fork 45
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
Update govuk_tech_docs to the latest version #632
Conversation
The accessibility statement is currently out of date. As of v2.4.0 of the govuk_tech_docs gem (alphagov/tech-docs-gem#247) there is one outstanding accessibility which prevents the site being fully compliant with WCAG AA.
I don't really do much ruby so might be wrong here but shouldn't the first commit include the |
Nope, the Gemfile just says |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes to the statement look good. I assume this will just pull in version 2.4.2
of govuk_tech_docs
? it didn't for me locally running bundle install
but testing with that version looked good.
The only change I'd like is for the Gemfile
to lock ffi
to 1.12
, (like alphagov/datagovuk-tech-docs#60), to stop it blowing up for users on OSX :)
Are you sure you were on the correct branch? I just did a fresh clone and
Is this a common thing? The GDS Way repo has been using a version greater than |
I am sure about the branch. I just tried again and got
There are a few GDS'ers on that issue reporting experiencing it and I know of a few others doing the same on Slack a while ago. From reading the issue, it looks like it might effect people on Mohave only:
Makes sense. I'll open an issue on that repo instead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 👍🏻
This includes a number of accessibility fixes, but one a11y issue remains, so the accessibility statement has been updated to reflect this.