ARIA page template doesn't document attribute page sections
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Read the ARIA page template at the MDN URL in the issue and compare its section list with the attribute pages described there. Decide whether to document “Values,” “Associated roles,” and “Associated interfaces,” or clarify that attribute pages use another template. Done when the template accurately explains the sections used by attribute pages.
Written by the indexing model from the issue text.
Description
MDN URL
What specific section or headline is this issue about?
ARIA attribute pages, and the ARIA page template's section list.
What information was incorrect, unhelpful, or incomplete?
The ARIA page template is also used for ARIA attribute pages, but attribute pages use sections the template doesn't list: "Values" (53 of 53 pages), "Associated roles" (53 of 53), and "Associated interfaces" (46 of 53). The template's "Accessibility concerns", "Best practices", and "Precedence order" don't appear on any attribute page.
What did you expect to see?
Either the template documents the sections attribute pages use, or it says that attribute pages have their own template.
Do you have any supporting links, references, or citations?
Related to https://github.com/mdn/content/pull/46488
Do you have anything more you want to share?
No response
- Dominant language
- Markdown
- Stars
- 11.1k
- Forks
- 23.3k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 165
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 mdn/content
-
Content:CSS needs triage
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Intl spec updatesOpenContent:JS goal: up-to-date needs BCD update
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
CSS Custom Highlight API: mention StaticRange for highlights that outlive DOM changesPossibly taken @abdul-karim-mia claimed this 1 day ago. OpenContent:WebAPI help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
WebGL texImage2D srcData: Clarify null is allowedPossibly taken @abdul-karim-mia claimed this 2 days ago. Openarea: WebGL Content:WebAPI
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Add new `runtime.MessageSender` `windowId propertyPossibly taken @xeenon claimed this 3 days ago. OpenContent:WebExt needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
BehiSecc/awesome-claude-skills#1354 ·
Maintainers usually reply within 7 days
-
customer report feature-request-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Codeinwp/optimole-wp#1239 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
agents nolte-linux security skills
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nolte/claude-shared#732 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 62/100
modelscope/ms-cookbook#35 ·
Maintainers usually reply within 1 day