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

Accessibility and quality issues found in automatic tests for designsystemet.no #2501

Open
15 tasks
Camulos opened this issue Sep 24, 2024 · 9 comments
Open
15 tasks
Labels
♿️ accessibility Issues related to accessibility 🐛 bug Something isn't working ☂️ epic Issues ready 🖥️ storefront designsystemet.no

Comments

@Camulos
Copy link
Contributor

Camulos commented Sep 24, 2024

Description of the bug

Automatic testing of designsystemet.no, tools used:

  • Siteimprove
  • Sortsite

Findings in categories:

  • Accessibility
  • Errors
  • Usability
  • Standards / Web
  • Compatibility

Accessibility findings in WCAG categories A and AA should be prioritized.

Images from Sortsite (20. september 2024)
Skjermbilde 2024-09-20 kl  10 09 12
Skjermbilde 2024-09-20 kl  10 08 40
Skjermbilde 2024-09-20 kl  10 06 27

Steps To Reproduce

Scan using automatic tools.

Additional Information

No response

Tasks

Preview Give feedback
@Camulos Camulos added the 🐛 bug Something isn't working label Sep 24, 2024
@Camulos
Copy link
Contributor Author

Camulos commented Sep 24, 2024

Level A finding in Sortsite: "A video plays longer than 5 seconds, without a way to pause it." and "Avoid animated images over 5 seconds long that can't be paused or stopped."
Relates to WCAG 2.2.2 Pause, stop, hide
Found 2 times, animations on front-page
Skjermbilde 2024-09-24 kl  12 24 24
Respects user setting for reduced animations? Yes!
As the animations is looped, and the content is not related to real-time updates/events it may be necessary to also give the user means to stop the animation by interacting with it. However as it respects the user preferences it could be that this issue is not critical. (For discussion)

@Camulos
Copy link
Contributor Author

Camulos commented Sep 24, 2024

Level A finding in Sortsite:

  • "Document title must not be blank."
  • "PDFs must be tagged to be accessible by screen readers."
  • "Use the lang attribute to identify the language of the page."

Relates to WCAG success criterion

  • 2.4.2 Page titled.
  • 1.3.1 Info and relationships
  • 3.1.1 Language of page

Found 3 times in PDFs uploaded to the site:
Skjermbilde 2024-09-24 kl  12 38 15
The first two documents is generated from Confluence using the save as PDF feature, the documents should have been adjusted in Acrobat Pro before uploading here.
The third document seem to be related to "Dødsfall og arv", based on the link-text.

The PDFs is used in this page: https://www.designsystemet.no/grunnleggende/introduksjon/designprinsipper (found from the footer urls on the frontpage)

Adding title and language-tag is fairly simple for PDFs, but if this is something we want to do, there may be other issues as well that the accessibility scan in Acrobat would find. The tagging for accessibility may be more of a challenge to amend after the documents have been created.

It is possible that the content of these documents is easiest made available and recreated as web-pages?

@Camulos
Copy link
Contributor Author

Camulos commented Sep 25, 2024

Level A finding in Sortsite:
"SVG elements with graphic role attributes must have an accessible name." (SVG elements with role=img, role=graphics-document or role=graphics-symbol need an accessible name provided by the SVG title element or an ARIA label.)
Relates to WCAG success criterion: 1.1.1 Non-text content

Found on 28 pages, multiple times on some pages
Skjermbilde 2024-09-25 kl  08 22 27

It looks like this is a problem almost everywhere there is any SVG-files, for example the three icons used to illustrate the 3 main call to action cards from the front page.

Many of these SVGs could be hidden with aria hidden, but even if hidden they should most likely be given an labelled by and their first child should be an title?

@mimarz mimarz added 🖥️ storefront designsystemet.no ♿️ accessibility Issues related to accessibility ☂️ epic Issues ready labels Sep 25, 2024
@mimarz mimarz moved this from 🔵 Inbox to ☂ Epics in Team Design System Sep 25, 2024
@mimarz
Copy link
Collaborator

mimarz commented Sep 25, 2024

Moving this to an epic as we'll have different sub-tasks to fix this.

@mimarz mimarz added this to the V1 - Helhetlig dokumentasjon milestone Sep 25, 2024
@Camulos
Copy link
Contributor Author

Camulos commented Sep 25, 2024

Level A finding in Sortsite:
"Document title must not be blank."
Relates to WCAG success criterion 4.1.2 Name, Role, Value

Found 2 places and it looks like it is when we embed video from Vimeo:

The frames/iframes need to have the title-attribute set to avoid SR read the filename (urls?) instead.

@Camulos
Copy link
Contributor Author

Camulos commented Sep 25, 2024

Level A finding in Sortsite:
"Element li not allowed as child element in this context."
Relates to WCAG success criterion 1.3.1 Info and Relationships

Found on this page:
https://www.designsystemet.no/grunnleggende/designelementer/farger
In selections for brand or mode here:
Skjermbilde 2024-09-25 kl  12 39 27

There are li-elements that are not set inside either ol or ul in these dropdowns.

@Camulos
Copy link
Contributor Author

Camulos commented Sep 25, 2024

Level A finding in Sortsite:
"alt text should not contain placeholders like 'picture' or 'spacer'."
Relates to success criterion 1.1.1 Non-text Content

In this page: https://www.designsystemet.no/grunnleggende/designelementer/ikoner there is an image that uses the alt text "image" here:
Skjermbilde 2024-09-25 kl  12 44 49

@Camulos
Copy link
Contributor Author

Camulos commented Sep 25, 2024

Level AA finding in Sortsite:
"Phrases in a different language should be in a span or div with a lang attribute."
Relates to success criterion 3.1.2 Language of parts

Found in this page: https://www.designsystemet.no/grunnleggende/for-utviklere/komposisjon
Every time an code-example is inserted in the text, the SR will try to read them in Norwegian, however the codes should be read in english? Add span for each and add lang="en" for each such span?

@Camulos
Copy link
Contributor Author

Camulos commented Oct 1, 2024

Level AAA finding
"Several links on a page share the same link text, but go to different destinations."
Relates to WCAG success criterion 2.4.9 Link purpose (Link Only) NB: AAA!

Found on 4 pages:
https://www.designsystemet.no/bloggen/2024/v1rc1
https://www.designsystemet.no/monstre/feilmeldinger
https://www.designsystemet.no/monstre/systemvarsler
Link text: "Github" is used for 2 different urls in each of the pages above.

https://www.designsystemet.no/grunnleggende/introduksjon/designprinsipper
Link text "Design principles" is used for 3 different urls.

Amend by writing unique link texts for each url, reflecting the topic on the linked-to-page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
♿️ accessibility Issues related to accessibility 🐛 bug Something isn't working ☂️ epic Issues ready 🖥️ storefront designsystemet.no
Projects
Status: ☂ Todo Epics
Development

No branches or pull requests

2 participants