Ideas for further SVG cleanup
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- html
- Domain
- accessibility, documentation
Research direction
Start with the SVG references in the HTML Standard and the linked discussion in whatwg/html#579. Review asyncdefer.svg, sample-url.svg, content-venn.svg, and parsing-model-overview.svg, including their object and img fallbacks and alt handling. Done means the cleanup and accessibility behavior are agreed and consistently applied.
Written by the indexing model from the issue text.
Description
@domenic in https://github.com/whatwg/html/pull/579#issuecomment-176609257:
- Use
<object>for asyncdefer.svg and sample-url.svg, to give the slightly better UX of selectable text and such.- But, what happens to the alt?
- Get rid of the png fallbacks for content-venn.svg and parsing-model-overview.svg. They seem redundant in this day and age.
- But, maybe we still want to support UAs that don't do
<object>? Like ATs, I assume. Then we would just nest a<img src="....svg">inside the<object data="....svg">?
- But, maybe we still want to support UAs that don't do
- Finally, we should presumably fix the mismatch between "setting an alt="" on this would be bogus (indeed, it would be non-conforming and bad for accessibility.)" and the presence of alt="" on the content-venn.svg fallback
<img>.
CC @doomdavve
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 38
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from whatwg/html
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
topic: media topic: rendering
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
clarification
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
compat topic: navigation topic: navigation API
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sugarlabs/musicblocks#8828 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
skiptools/skip-fuse-ui#147 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OneBusAway/onebusaway-ios#1438 · 1 reaction ·
-
accessibility area:tasks beginner friendly bug community contributions-welcome difficulty:beginner difficulty:easy good first issue hacktoberfest help wanted open-source up-for-grabs
Difficulty 2/5 Under an hour Newbie friendliness 92/100