This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.
Process to submit HTML spec bugs
From HTML accessibility task force Wiki
The HTML Accessibility Task Force expects to submit a number of Accessibility Issues to the HTML WG, some of which may also be formal comments from the Protocols and Formats Working Group (PFWG). The HTML Working Group Decision Policy states how bugs and issues should be submitted. This process extends the HTML WG process to allow tracking of accessibility-specific bugs, as issues now start as bugs.
- Enter a bug in Bugzilla following the guidance in the HTML Decision Policy. In particular, be sure the bug is well described and includes concrete suggestions for improvement.
- Add the email address "email@example.com" to the cc for the bug. The cc field is shortly before the description field and ensures that activity on the bug will be sent to that email list.
- Add the keyword "a11y" to the bug. The keywords list is towards the bottom of the issue entry screen. Keywords are space delimited and must match (case-sensitive) keywords known to the system. This tags the issue as an accessibility issue, allowing us to track it.
- If you have prior approval from the accessibility task force, add the "a11ytf" keyword. Please do this only if you have formal authorization from the task force. "A11yTF" Keyword Criteria is under discussion. We can always add this keyword later, so it is not crucial to declare it a formal task force bug immediately.
- If the bug is formal feedback from the PFWG, add the "PFWG" keyword in the same manner. Please do this only if you have formal authorization from the PFWG for the bug. PF can always add this keyword later, so it is not crucial to declare it formal PFWG feedback immediately.
If you do not see the keywords field, please contact a Staff Contact of the task force who can give you access.
- Bug Collection, Development, Status and Resolution
- Escalating a Bug to an Issue
- Weekly Resolved and Rejected Bugs Reports
- Accessibility Issues in the HTML5 Tracker. Listings by status (open, raised, closed, all plus actions). Some process info too.