[Accessibility_sig] Tables vs CSS elements, content, & accessibility

[Mary Salome]

Benjamin,

 

Thank you for taking the time to point out my cut and paste error. The correct URL is below with the original question and additional details.

 

Thanks,

Mary

 

---

 

We're in the process of making our tables compliant, and in some cases we'll be converting literal tables (<table> through </table>) to CSS-based elements. We've come across a situation where we're not sure what is best for people using screen reader software.

 

The situation involves elements that are not a true data tables, but are referred to as tables in the text due to internal editorial guidelines. Typically, these have a title and one cell with information in it, sometimes with multiple rows, but not more than one column.

 

Would it confuse a person using a screen reader if the title (an <h3> tag) had a value of "Table 1." when there would be no <table> found, but instead a CSS-driven "box treatment" using <div> tags? In these cases, are we better off using a <table> with the <caption> tag encapsulated in it to make it obvious where the content belongs, despite the fact that these aren't true data tables?

 

The words "Table 1" have to be there because of internal editorial style guidelines. We need to have a border and sometimes a background color, which is why we would use divs. One of our goals is to use CSS-based elements instead of tables when possible. The question is whether it would be confusing on some level for screen readers to have the words Table 1 precede something besides the table tag set.

 

http://hepatitis.va.gov/vahep?page=prtop04-gd-2006-t02

 

* I am out of the office on Mondays and Thursdays

 

Mary Salome, MA

Production Manager

UCSF Center for HIV Information

http://chi.ucsf.edu

415-221-4810 x3740

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://knowbility.org/pipermail/accessibility_sig_knowbility.org/attachments/20090310/076c66a0/attachment.html>