Bugs for TF discussion

Chaals, Steve & Janina,

 

Happy new year!

 

We’re continuing to work through the a11y bugs that have been marked as
resolved and either NeedsInfo/Won’tFix. There are a number that we need the
TF to review, because we don’t have the expertise within the bug triage team
to process them.

 

10873 https://www.w3.org/Bugs/Public/show_bug.cgi?id=10873

 

8875 https://www.w3.org/Bugs/Public/show_bug.cgi?id=8885

 

10709 https://www.w3.org/Bugs/Public/show_bug.cgi?id=10709

 

13390 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13390



13460 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13460



13549 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13549

13350 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13350

13553 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13553

13566 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13566

13572 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13572

13541 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13541

Would it be possible to find time during the next TF call (or couple of TF
calls) to review them? In each case we need to decide whether the bug can be
closed, or who will take it on if it’s to be re-opened and pursued under
either HTML5 or HTML5.1.

 

Léonie.