- From: Marjolein Katsma <hgnje001@sneakemail.com>
- Date: Thu, 28 Oct 2004 12:47:34 +0200
- To: w3c-wai-ig@w3.org
At 12:22 2004-10-28, Martin Stehle wrote: >Hello Marjolein, > > > Feedback? > >Sorry for the stupid question, but did you read the useful articles >under http://www.google.com/search?q=accessible+tables ? Apart from the applicable standards I have read tons of articles about accessibility markup for tables. And I've been doing that for a number of years already. I can't claim to have read them all, of course - I'd probably still be reading instead of actually producing code. <grin> More to the point, perhaps - do you see any evidence that I have *missed* relevant information in such articles that I should have applied in marking up a calendar? >If you want to hear your markup try the demo version of JAWS at >http://www.freedomscientific.com/ I am fully aware that JAWS, just like various other screen readers and AT, has various modes and configuration options. What I do not know, however - and could not learn from using a demo version myself - is how a *user* of such software would in practice use the tool to navigate my site, or a calendar in particular. I'm asking for feedback precisely to find out the things that I could not easily discover myself. >And to safe work on code which is not supported by assistive >technologies have a look on >http://www.juicystudio.com/assistivedeviceschart.asp at "tables". I looked at that page but found that for none of the tools outlined is there any information on how 'scope', 'headings' and 'axis' attributes would be (or could be! depending on configuration) handled. A nice genera;l overview, but not helpful at all in this particular case. How would *you* mark up a calendar? Thanks, -- Marjolein Katsma Travel Blog: http://iamback.com/blog/ Spam Reporting Addresses: http://banspam.javawoman.com/report3.html
Received on Thursday, 28 October 2004 10:47:37 UTC