w3c/svg-aam Issues

Last updated May 17, 2024, 5:56:54 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

16 out-of-SLO untriaged issues

Untriaged

Try to triage issues within 7 days. [ More Info ]

Issue	Title	Within SLO	On maintainers' plates for	Time past SLO
#7	Harmonize use-element behavior with other shadow DOM behavior	❌	6.2 years	6.2 years
#8	Exposing SVG view behavior and viewTarget to accessibility APIs	❌	6.2 years	6.2 years
#10	Fix issues with mapping script	❌	6.1 years	6.1 years
#11	SVG with ARIA roles	❌	4.7 years	4.7 years
#14	update respec, reference terms	❌	3.1 years	3 years
#15	Remove references to and mappings for mesh (and related elements)	❌	2.7 years	2.7 years
#19	Consider removing normative statement regarding "no accessible object created"	❌	2.6 years	2.5 years
#21	SVG-AAM should address which elements should map to ARIA `generic` role	❌	2.1 years	2.1 years
#23	Broken references in SVG Accessibility API Mappings	❌	1.3 years	1.3 years
#24	Define computedrole for the SVG roles table	❌	1.1 years	1.1 years
#28	SVG-AAM includes a broken "tree inclusion" anchor in Core-AAM that may have moved to ARIA	❌	6.1 months	5.8 months
#29	Does "no role may be applied" mean "UAs MUST NOT apply a role even if an author supplies one and gets the element rendered"?	❌	6.1 months	5.8 months
#30	Should concrete shape/object roles like `circle` have a more specific role description?	❌	6.1 months	5.8 months
#31	SVG-AAM Section 8.1 Name and Description needs rewrite	❌	6.1 months	5.8 months
#33	spec says text element should map to "group j/k paragraph"	❌	6 months	5.8 months
#34	Remove deprecated xlink:href from the SVG-AAM name computation steps	❌	5.9 months	5.7 months