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

Editorial: For better accessibility, name all hyperlinks #3301

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

gibson042
Copy link
Contributor

As discussed at tc39/ecmarkup#588 (comment)

...but if there is desire to keep any visible URLs in screen presentation, I would like to mark such hyperlinks with a "print-ready" class and update ecmarkup to accommodate them with pure CSS as suggested at tc39/ecmarkup#588 (comment) :

+/* Render non-mailto external link targets, cf. https://url.spec.whatwg.org/#special-scheme */
-a[data-print-href]::after {
+a:not(.print-ready):is([href^='ftp:' i], [href^='sftp:' i], [href^='http:' i], [href^='https:' i], [href^='ws:' i], [href^='wss:' i])::after {
   content: ' <' attr(href) '>';
   color: initial;
 }

@ljharb
Copy link
Member

ljharb commented Mar 26, 2024

Some of these links are better named, but in all media, i think most of them are better with visible URLs.

@michaelficarra michaelficarra added the editor call to be discussed in the next editor call label Mar 26, 2024
@michaelficarra
Copy link
Member

@gibson042 If you want to talk about this with us on the editor call tomorrow, you're welcome to attend.

@michaelficarra
Copy link
Member

At editor call today, we agreed that it is a non-goal to remove all links that display as the URL from the document. We will, however, review each replacement in this PR and determine their suitability individually.

@michaelficarra michaelficarra removed the editor call to be discussed in the next editor call label Mar 27, 2024
@gibson042
Copy link
Contributor Author

We will, however, review each replacement in this PR and determine their suitability individually.

Reviewing the commits individually should support that plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants