Making lists 508-compliant

Hi Colleagues!

A subject each day more interest due to government at all levels, and even private organizations allocating more time and effort to make their content accessible to all potential users/clients.

I will try to compile info I learn about (mostly by surfing the Web) and on different aspects of 508 compliance (or WACG 2.0 as it is also known).

This time, let me paste this link to practical guidelines from the VA Dept, and specifically talking about how to prepare an accessible list. https://www.section508.va.gov/suppor...df/7list_1.asp.

Cheers, Gentle

One important thing is to keep the tag structure list items that are part of the original list and not break it when you change pages.

Quote:

---

Originally Posted by RodrigoDG

One important thing is to keep the tag structure list items that are part of the original list and not break it when you change pages.

---

That's true! The "tree" structure of a list and its sub-lists should flow to the following page (what matters is the structure itself, so that any AT used can go with the natural flow). In fact, if there happens to be a footer, we should usually tag it as an artifact, because the flow of the list matters more to the user than a repeated footer.

I've found the site of the Government Accesibility Program.
Section508.gov | GSA Government-wide Section 508 Accessibility Program

I believe that should be the right place to consult about this regulation.

yes, and an important part to see is this:Create Accessible Electronic Documents | Section508.gov

Quote:

---

Originally Posted by santiagop

I've found the site of the Government Accesibility Program.
Section508.gov | GSA Government-wide Section 508 Accessibility Program

I believe that should be the right place to consult about this regulation.

---

Please, spare me the effort of reading all that! :p Is there anything in particular you can add about managing lists for accessibility? I would like to see something like a wazzup-like txt message. (That summarized! Lol)

Hi Gentle

I suppose you should think about the document as if you were creating xml code or even html.
Therefore, in the case of a list, you must have each item with bullets and you must define when the list begins and ends.
If you do not define it as a list, it will be recognized as independent lines without any connection between them.

Here is a simple example of how to create a list in HTML. It is very similar to how it should look when you work with 508:

<p>This is paragraph text.</p>
<p>Here starts a list:</p>
<ul>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
<li>Item 4</li>
</ul>
<p>Here starts another paragraph</p>

i think the correct list for 508 would be this structure:

<L>
<LI>
<Lbl>
<LBody>

Hi Rodrigo,
Do you know what the <Lbl> tag does?

Quote:

---

Originally Posted by santiagop

Hi Rodrigo,
Do you know what the <Lbl> tag does?

---

Hi Santiago, that's the bullet for the list. :)

Hi,
I would like to know how to make compliant abbreviations like No. for number. Should it be spelled?
And what happens with underscore (_)? Should it be spelled as "underscore" as well?