Content
View differences
Updated by Henriette Darge 11 months ago
### Steps to reproduce
1. Look at a link in a PageHeader description or a form description
### What is the buggy behavior?
From an accessibility perspective, the links are not distinguishable enough from the surrounding text.
### What is the expected behavior?
Links should be clearly distinguishable. Possibilities include:
* Whenever there is a link in a description of Increasing the PageHeader, the color contrast to at least 3:1 (contrast between link should have an text and surrounding text; **not** between text and background)
* Adding link styling (e.g. underline effect. We are therefore following Primer's [guidelines for links in text](https://primer.style/product/components/link/accessibility/#guidelines). links)
### Notes
Some automated checks for the problem have been silenced to make automated tests pass. These should be re-enabled.
I.e. when `expect(page).to be_axe_clean` is used, make sure this test is not disabled via `skipping("link-in-text-block")`.
###
### Screenshots and other files
Two occurences of the violation in the new SCIM Clients UI (the bottom of the two is even hard to distinguish for me):
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/707687/content">
Two occurences of the violation in the file storages UI:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/707698/content">
1. Look at a link in a PageHeader description or a form description
### What is the buggy behavior?
From an accessibility perspective, the links are not distinguishable enough from the surrounding text.
### What is the expected behavior?
Links should be clearly distinguishable. Possibilities include:
* Whenever there is a link in a description of
* Adding link styling (e.g.
### Notes
Some automated checks for the problem have been silenced to make automated tests pass. These should be re-enabled.
I.e. when `expect(page).to be_axe_clean` is used, make sure this test is not disabled via `skipping("link-in-text-block")`.
###
### Screenshots and other files
Two occurences of the violation in the new SCIM Clients UI (the bottom of the two is even hard to distinguish for me):
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/707687/content">
Two occurences of the violation in the file storages UI:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/707698/content">