These forums are now Read Only. If you have an Acrobat question, ask questions and get help from one of our experts.

Do you use the List Label <Lbl> tag?

Forum Index > Accessibility > Do you use the List Label <Lbl> tag?
2011-09-12 07:38:16
pfendrick
Registered: Dec 2 2009
Posts: 3
Answered

I'm wondering if others use the List Label tag when creating lists. It seems to be an optional tag. When I listen in JAWS, I hear no difference in lists with the label tags and those without.
 
The only difference I've come across in JAWS is when using the down arrow, which causes JAWS to read a document line by line. In lists with the label tags, the bullet will be read with the first "down arrow" and then the rest of the line will be read with the second "down arrow." In lists without the label tags, the whole line will be read at once, including the bullet.
 
Since it takes extra time to add label tags to lists, I'm wondering if there are any other benefit to adding label tags. Are other people using them?

Peter

My Product Information:
Acrobat Pro 9.4.3, Windows
Top
2011-09-13 20:29:49
#1
daka630
Expert
Registered: Mar 1 2007
Posts: 1420
If you are presenting an ordered list then use the label tag.


Be well...

Top
2011-09-15 10:46:26
#2
pfendrick
Registered: Dec 2 2009
Posts: 3
daka630,

Thanks for your response. I guess I'm wondering if there is some benefit in using the label tag in lists. It takes extra time to add the label tags, especially in documents with a lot of lists. And I have people asking me why do they have to add the label tags since there seems to be so little difference in JAWS, when reading lists with and without the label tags.

Peter

Top
2011-09-20 08:30:51
#3
daka630
Expert
Registered: Mar 1 2007
Posts: 1420
Accepted Answer
Peter,

If those who "own" the content intended to depict information in an order list then the obligation, in terms of accessibility, is to provide the same semantic structure in the provide PDF.
Such equivalency is at the heart of accessible digital content.
Inadequacies / limitations associated with AT applications is exactly why these applications do *not* establish accessibilty criteria.
In context of Accessible PDF this will be reinforced with the release of ISO 14289-1 (the PDF/UA (Universal Accessiblity) in 2012.

I apologize if this sounds harsh but one has a choice; do it properly or seek the "2.5 to survive" path.
It has been my experience that the latter inevitably incurs an unexpect cost somewhere down the timeline.



Be well...

Top
2011-09-22 13:35:03
#4
pfendrick
Registered: Dec 2 2009
Posts: 3
Hi Daka630,

Thanks for the explanation. It sounds reasonable enough!

Peter

Peter

Top