OATS reply/follow up:

Sorry, that is the problem with getting things second hand and not being able to look at a list archive.

That is a right pain.. Has anyone found any bugs with other readers?  The front page validates to strict XHTML on W3C... Though i've just noticed some CSS bugs. The only bug listed I can find for PLONE is here: http://dev.plone.org/plone/ticket/4764 - there looks like a semi fix.

Anyway,i'll check it out, thanks for the feedback. 

Cheers

Simon

PLONE users thread

• Reply RE the random CSS files

OATS second reply

Thanks.  Erm, could you send me your outlined suggestion - as far as I can see, this list has no archive (no comments RE usability!) so I can not refer to it.

RE accessibility standards - well, that page validates [1]. Obviously, this isn't everything  and the title was misleading (so i've changed it).

Also, yes, I agree we shouldn't hide the titles of the pages in link title properties - though I don't think this is inherently inaccessible, since there is a trade off between simplicity of page and 'hidden' content.  I've thus also quickly changed that page [2].  I'm still not quite happy about the added complexity, so will probably tweak some more (maybe concatenating the description to a single line).

I have also, I hoped, fixed the CSS validation errors we had encountered [3].  I'd be interested if this has fixed the JAWS errors reported (I will independently test too).

I'll feed the CSS issue and the sitemap code/suggestion back to PLONE - this is the power of open source.

I'm still interested about how, as a group, you feed back accessibility issues to website designers. 

Cheers

Simon

[1] http://validator.w3.org/check?uri=http://www.oatsoft.org/sitemap
[2] http://www.oatsoft.org/sitemap
[3] http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.oatsoft.org%2Fsitemap&usermedium=all