This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
=============================================== Tested Window title : HTTP Monitor - Cookies Tab =============================================== No Accessible description : Class: org.netbeans.modules.web.monitor.client.DisplayTable { Incoming Cookies Table | } Components with no LABEL_FOR pointing to it : Class: org.netbeans.modules.web.monitor.client.DisplayTable { Incoming Cookies Table | }
This is fixed. QA: please test this with more than one incoming cookie and more than one outgoing cookie. Will attach a JSP which adds two outgoing cookies; to add incoming cookies use Edit & Replay. Thanks, Ana
Created attachment 13171 [details] JSP that creates two cookies
Created attachment 13172 [details] Diffs for CookieDisplay.java
Accessible description is fixed, but LABEL_FOR issue is still there: Components with no LABEL_FOR pointing to it : Class: org.netbeans.modules.web.monitor.client.DisplayTable { Incoming Cookies Table | Incoming cookies table. } Class: org.netbeans.modules.web.monitor.client.DisplayTable { Incoming Cookies Table | Incoming cookies table. } Class: org.netbeans.modules.web.monitor.client.DisplayTable { Incoming Cookies Table | Incoming cookies table. } Class: org.netbeans.modules.web.monitor.client.DisplayTable { Outgoing Cookies Table | Outgoing cookies table. } Class: org.netbeans.modules.web.monitor.client.DisplayTable { Outgoing Cookies Table | Outgoing cookies table. }
The A11Y fix would require to create labels for all tables inside the Incomming Cookies/ Outgoing cookies section.
Hm, Milan, I'm not sure whether I understand your evaluation, but I think you are saying that I would need to create one JLabel for each table. I initially thought so too, but when I spoke to the A11y experts, they told me that it is not necessary, because the same JLabel can label more than one component. The only thing is, you can't set that from the JLabel, but you have to access the accessible relations for the table instead. That's what I attempted to do in the code above - if you check the diffs, you can see that I add a relation to each table that it is LABELLED_BY a JLabel. Libor, it would help me if you could do the following. The output of the test result indicates that there were three tables for incoming cookies and two tables for outgoing cookies that were not labelled. I can see two possibilities: either our A11y test is not able to pick up on the labelled_by relationship (1) or the implementation of the accessible relations set is done in such a way that it checks the relations for object equality before they're added (2). If the test you ran had exactly three incoming cookies and two outgoing cookies (the test page I sent had two outgoing cookies, so I suspect this is the case) then we have case (1). In this case, there is something wrong either with the A11y APIs, or with our A11y test. If the test you ran had four incoming cookies and three outgoing cookies, then we have case (2), and I need to create a new relationship object each time. Thanks, Ana
Duh - I assumed that there is no way that I can find out what the label for is without a screen reader. I assume there is. Can you help?
OK, I figured out how to view the labels. I can confirm that on Windows XP, I see "Outgoing cookies table." as a label on each table, so this bug was fixed. This is a bug in the A11y test.