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.
Bugs/Escalating a Bug to an Issue
According to the HTML Working Group Decision Policy, bugs that are not satisfactory resolved can be escalated to the HTML WG Issue Tracker. Tracker Issues "record that an editor's resolution was not satisfactory, and so the full Working Group must address the issue."
Recourse For a Dissatisfied Bug Reporter
If a bug reporter is dissatisfied with the bug resolution and does not believe it is productive to ask the editor to reconsider, he or she may ask to escalate the issue to the issue tracker. Don't reopen the bug. Leave it at WONTFIX or INVALID, etc and then:
1. Raise a HTML Working Group Tracker Issue
A dissatisfied bug reporter:
- With Tracker access can raise a Tracker Issue directly.
- Without Tracker access should:
- Add the keyword "TrackerRequest" to the bug.
- Suggest an issue title.
- Suggest an issue description.
- As previously explained in the process to submit HTML accessibility Bugzilla bugs, if it is an accessibility bug make sure you have:
- Added the Keyword "a11y" .
- Added the address "firstname.lastname@example.org" to the cc field.
2. Write a Change Proposal
If you want to have an issue addressed after escalation, you should expect that you will have to write a Change Proposal, or convince someone else to do so.