WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Table Screen Reader rendering.

for

Number of posts in this thread: 3 (In chronological order)

From: Annie Belanger
Date: Fri, Jun 17 2005 6:23AM
Subject: Table Screen Reader rendering.
No previous message | Next message →

I am working on print document that is meant to be the accessibility guidelines
to get our institutional sites Priority 2 compliant. The document is meant to
educate content developers. My team will be doing the user scenario testing,
but I want the examples to illustrate why this is necessary as there is
resistance to this process.

I adapted the accessible table from the W3 to a Canadian context. And had
assumed that it would 'render' properly with a screen reader (not a particular
one), but the markup seems to make no difference.

Here is the code, I would like some input as to what I'm doing wrong... (I've
put it in a notepad file, hence the doc header)

<!DOCTYPE HTML PUBLIC

From: Jan Eric Hellbusch
Date: Fri, Jun 17 2005 6:30AM
Subject: RE: Table Screen Reader rendering.
← Previous message | Next message →

> I adapted the accessible table from the W3 to a Canadian context. And had
> assumed that it would 'render' properly with a screen reader (not
> a particular
> one), but the markup seems to make no difference.

Have you tried the table mode on your screen reader? Depending what software
you are using, it is slightly different.

Using JAWS 5.1 (German) you would press T and then navigate with
CTRL+ALT+Arrowkeys. HPR also has a table mode (Alt
+T) and so on.

Regards
Jan


--
Jan Eric Hellbusch
Tel.: 06 41 / 9 31 21 54 oder 01 63 / 3 36 99 25

.biz: http://2bweb.de
.info: http://bf-w.de





From: ben morrison
Date: Fri, Jun 17 2005 6:35AM
Subject: Re: Table Screen Reader rendering.
← Previous message | No next message

> I adapted the accessible table from the W3 to a Canadian context. And had
> assumed that it would 'render' properly with a screen reader (not a particular
> one), but the markup seems to make no difference.

You seem to be mixing th's and td's, you should use <thead> for the
header section, <tbody> for the content and <tfoooter> which i
sometimes leave blank.

Some sections only have 4 <td>s others have 5, you need to use
colspan="2" appropriately to do this.

You seem to have the headers all mixed up.

Ive never come across axis before?

there is a great table tool on accessify.com whcih can be really
usefull, I use it when needed as its very rare that i use tables.

http://www.accessify.com/tools-and-wizards/accessible-table-builder_step1.asp

HTH
Ben