Iframes in HTML output need @titles (Accessibility WCAG 2.1)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- html, xml
- Domain
- accessibility, web-dev
Research direction
Search the XSLT sources for iframe output paths and identify each template or mode that emits one. Check whether an existing @title value can be derived from surrounding content; otherwise determine where an author-supplied title should be required. Done means every generated iframe has a meaningful @title, verified by inspecting representative HTML output.
Written by the indexing model from the issue text.
Description
Triggered by issue brought up by John Hammond here:
We need to check the paths that emit iframe elements. For each one, we either need to be able to compute a quality @title from existing info or require the author to provide one.
- Dominant language
- XSLT
- Stars
- 466
- Forks
- 251
- Avg merge
- 4m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 PreTeXtBook/pretext
-
The print preview leaves writing space short by the margins of hidden headers, footers and solutionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3329 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
PreTeXtBook/pretext#3305 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3297 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PreTeXtBook/pretext#3285 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PreTeXtBook/pretext#3283 ·
Maintainers usually reply within 1 day
All issues in PreTeXtBook/pretext
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vigetlabs/wordpress-site-starter#331 ·
Maintainers usually reply within 17 days
-
accessibility area:react bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
accessibility good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
styling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Fchat-Horizon/Horizon#1059 ·
Maintainers usually reply within 2 days
-
accessibility admin ux audit
Difficulty 2/5 Half a day Newbie friendliness 78/100
endora-commerce/endora-commerce#1541 ·
Maintainers usually reply within 1 day