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

All changes labelled for version 4 + David H's commit #371

Closed
wants to merge 19 commits into from

Conversation

marcotranchino
Copy link
Contributor

This branch contains all the changes in the PRs that have been labelled for the release of version 4.

It also contains David H's unrelated commit that fixes a problem with the menu.

heathd and others added 19 commits October 21, 2024 15:43
try to avoid left menu jumping around
With this commit, we are just updating the ruby version for the example
project since the current version is old and no longer supported.
When we wrap images in hyperlinks, we make the
image's alt text their only content. If those
images have no alt text, they are effectively
empty links.

This means they have no accessible name if queried
by an accessibility API:

https://w3c.github.io/html-aam/#img-element-accessible-name-computation

...so it'll be up to the screen reader to guess.
In testing, this ends up being the file name,
which can't be relied on to explain the image. All
in all, this behaviour breaks the non-text content
success criterion from WCAG 2.2:

https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html

This issue is recorded here:

#355

This commit take the approach of introducing a
guard against images with no alt text and
choosing not to wrap them in hyperlinks when
found.

My Ruby is basic at best but I looked at the
method we're overwriting from the Red Carpet HTML
renderer and copied across its interface more
exactly, to make it clear where the alt_text
variable comes from.
Rewrite alt text guard to be more exact
govuk-frontend

As govuk-frontend encourages its use within
script type=module, we need to create a
separate entry for it as we do not want
any downstrema project to change the way they write
their own javascript.

This PR
- adds a new zgovuk_frontend.js` include to core layout
- removes `all.js` import from `govuk_tech_docs.js`
- creates a new `govuk_frontend_all.js` entry in
the lib that imports `all.bundle.js` from the
NPM package
- adds a new `govuk_frontend.js` entry point in
the example project that pulls in the
`govuk_frontend_all.js` from the lib
- adds new minifier - https://github.com/ahorek/terser-ruby
as the built-in one doesn't support ES6
To do: see if we can configure to silence warning

Built-in sassc compiler doesn't compile
stylesheet do to them, containing source maps

https://github.com/sass-contrib/sassc-embedded-shim-ruby
No longer needed with the upgrade to v5
This change adds checks to ensure that this.$sticky exists and it is visible
before trying to access its methods.

Further information at #368
Following a PR review[1], this commit changes the test on this.$sticky, in
order to verify if the object actually contains any elements.

Further details in the PR[2].

[1]
#368 (comment)

[2]
#368
With this change, we have defined a custom SassWarningSupressor module that
overrides the warn method so that we can ignore messages containing 'sass'
or 'dart-sass' only.

This is needed so that we can avoid sass warnings in downstream projects.
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.

4 participants