I just checked out the first page anyway in Lynx and it displays just fine, although it sets a cookie. I don't know if it is blind-friendly or not, and am not sure even how to determine if it is or is not. It would be nice to be able to make the site available to the widest audience.
[same disclaimer as Tom]
-----Original Message----- From: Tom Bruno
I like this idea, have a <for blind> link at the top in the first few lines of the page, that is w3c compliant. Then we can write something for the blind pages that pulls the articles out of the sql database. Still dynamic, same content just different look (not violating seperate-content principle or whatever jason was talking about), and we still get the nice look. Sure it'll take a little work, but... what do we do.. sit around and argue in the IRC channel anyway.
Don't take that as me volunteering to do it. I don't have a clue. If it came to it though, i could probably learn.
Brian Densmore wrote:
I just checked out the first page anyway in Lynx and it displays just fine, although it sets a cookie. I don't know if it is blind-friendly or not, and am not sure even how to determine if it is or is not. It would be nice to be able to make the site available to the widest audience.
Repeated content (like navigation bars) needs to go at the end of the page or be /really/ short. It gets really annoying to hear about 2.5 minutes of information about logging in and navigating around read aloud every time you open a page.
Also, the tables present a problem to screen readers as it's hard to tell when you're jumping around what the signifigance of a table is.
Jumping between headings (h1,h2,h3,etc) which are used as an outlining mechanism, on the other hand, is very easy.
-
Brian Densmore -
Jason Clinton