|
| |
|
|
Nicole
Posts: 2843
Joined: 9/15/2004
From: Nambucca / Kempsey, Australia
Status: offline
 |
Writing an Accessibility Statement... - 7/15/2006 2:32:49
I started writing a couple of accessibility statements today, boy it's easy to get carried away, mostly with how different browsers offer different accessibility features and how to go about it. I think I've decided to leave the browser things out of these statements, except perhaps to advise people who to resize text.
Anyway, here's a couple of links I found that give some good advice on how to write accessibility statements.
http://juicystudio.com/article/writing-a-good-accessibility-statement.php
http://www.dmag.org.uk/resources/design_articles/accessibilitystatement.asp
Nicole
_____________________________
|
|
|
|
davidrandall
Posts: 82
Joined: 7/28/2005
Status: offline
|
RE: Writing an Accessibility Statement... - 7/19/2006 9:32:41
Nice finds Nicole.
I've got a "stock" accessibility statement that I wrote a while back and just tweak for whatever site it's used on.
The latest version is at http://www.chloelou.co.uk/access.html
Dave
| |
|
|
|
Nicole
Posts: 2843
Joined: 9/15/2004
From: Nambucca / Kempsey, Australia
Status: offline
|
RE: Writing an Accessibility Statement... - 7/19/2006 9:57:15
Well it's really quite dependant on what measures you've undertaken with a particular site and why, as to what gets included in the accessibility statement.
For instance one of the statements I was writing included javascript tooltips for which I had to make mention of the site's glossary as an alternative, same with the javascript text-resizer which wouldn't work with javascript disabled. This is where I feel it's important to touch on how to resize text with each major browser, but in saying that, a user can change much more than just text size using their browser settings which is why i was saying it's easy to get carried away with an accessibility statement.
Best to stick to things you've implemented in the site and only the text size issue with each browser or you'll be writing forever.
David, that statement you've given is good, but I wonder why you've started by sayng what you have?
It's true, of course, but I'm wondering whether that kind of information is unnecessary to those who read accessibility statements to find what features a site has for them, and therefore if it should be stated at all, it possibly should be mentioned at the bottom of the statement instead?
Get what I mean? A person using the accessibility statement to find information for their ease of use isn't going to find the "reasons why accessibility is important" useful, but those who don't need to know why for personal reasons but are interested will read the whole thing anyway?
Just a thought anyway.
Nicole
_____________________________
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
Nice find Nicole!
is, kill the jargon and tell them what they need to know. They're really not interested in XHTML and CSS they just want to know if it'll work in Jaws and whether they need to do anything special.
