minutekey / ez-access-web

Automatically exported from code.google.com/p/ez-access-web
0 stars 0 forks source link

Parsing for <label>s #28

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
In general, an author should use explicit labels (where the label has a for 
attribute), but may use implicit labels. In these cases, the labels should not 
generally by navigable, but the contents should be read when the associated 
control is highlighted.

If there are "orphaned" label tags that are not associated with any controls, 
then that <label> should be navigable as an end/leaf node. In this way the user 
probably won't lose too much information.

In the parsing engine, you can look for a for="" attribute (I don't think you 
need to verify the existance of a matching ID--that is the designer's problem) 
or navigable/interactive children of the <label> and then determine that the 
label is non-navigable. If there are no navigable children to the <label> and 
no for="" attribute, then the <label> should be navigable.

Original issue reported on code.google.com by jbjor...@gmail.com on 15 May 2013 at 2:14

GoogleCodeExporter commented 8 years ago
This issue was closed by revision r151.

Original comment by aeharding on 5 Jun 2013 at 7:34

GoogleCodeExporter commented 8 years ago
Just fixed this in r151. I used the following test code to make sure it worked 
as intended:

Original comment by aeharding on 5 Jun 2013 at 7:35

Attachments: