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

Another de facto standard link style not visually distracting is needed in the case of a large number of links #4133

Open
hata6502 opened this issue Nov 2, 2024 · 4 comments · May be fixed by #4131

Comments

@hata6502
Copy link

hata6502 commented Nov 2, 2024

The standard link style is solid underline.
However, G183 says If there are not a large number of links in the block of text, underlines are recommended for links in blocks of text..
I think another link style not visually distracting is needed in the case of a large number of links such as wiki pages.

The various examples provided in G182 (blue bold text, red italic text) may not actually be recognized by users as links.
This is because website viewers do not have enough experience to recognize not solid lines as links.
So, I thought that providing another one new technique might have some hope of creating a de facto standard like solid lines.


I have a similar issue for WikiMedia.
Reading the link below may help you imagine about this issue.
⚓ T378208 Proposal to add minimal dotted lines to links for colorblind users

@hata6502 hata6502 linked a pull request Nov 2, 2024 that will close this issue
@hata6502 hata6502 changed the title A de facto standard link style is needed in the case of a large number of links Another de facto standard link style is needed in the case of a large number of links Nov 2, 2024
@hata6502 hata6502 changed the title Another de facto standard link style is needed in the case of a large number of links Another de facto standard link style not visually distracting is needed in the case of a large number of links Nov 2, 2024
@hata6502
Copy link
Author

hata6502 commented Nov 8, 2024

@patrickhlauke Is this issue likely to be commented on?

@patrickhlauke
Copy link
Member

not sure why you're singling me out here, but generally let me just say: this is unlikely to get any immediate traction for WCAG 2.x. it might be something you want to take to WCAG3 for consideration

@patrickhlauke
Copy link
Member

also ... i admire the idea that providing a technique in wcag might create a de-facto standard, but realistically since there's still problems in getting the actual normative standard followed consistently, and techniques are only informative suggestions, I don't share that kind of optimism...

@hata6502
Copy link
Author

hata6502 commented Nov 8, 2024

Thank you! I'll trying to open this issue after reading the WCAG 3 introduction document.
https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/

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 a pull request may close this issue.

2 participants