W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2000

Re: Accessibility barrier?

From: Steven McCaffrey <smccaffr@MAIL.NYSED.GOV>
Date: Thu, 13 Jul 2000 13:55:56 -0400
Message-Id: <s96dca75.083@mail.nysed.gov>
To: <melinda@ink.org>, <charles@w3.org>
Cc: <w3c-wai-ig@w3.org>

As far as I know,    there has to be an alternative to a visual indication of change of statuss (as an extension of "don't use color alone".  
The form might have to be changed to do this.  I would assume that the advantage of xhtml is exactly this.
You could have tags like <current> or whatever the apporpriate semantic word is most descriptive of the changes.
If the form (xhtml DTD?)is already defined but accessibility is not incorporated, the form will have to be changed, so you will have to bring this to whomever is responsible I would think.  Exactly how these changes are made accessible is not written in stone, but what is written in stone I think  
is the fact that there has to be some way of obtaining this information.
Just to see what is available here, I checked out the NY Assembly legilsative search service and found, among other items an "actions" link.
For example, using the keyword search "information technology", then choosing one that was retrieved,
If you select the [actions] link,
a nice table (accessible due to context ) arranged chronologically with categories of changes like
"referred to .." and "amend and recommit".    
I don't know how this is done, but it is quite nice I think, although I don't know if the actions are updated in real time, say, minute by minute, and maybe that is far more complex.  
Hope this is useful for further discussion at least.

Steve McCaffrey
Senior Programmer/Analyst
Information Technology Services
New York State Department of Education
New York State Workgroup on Accessibility to Information Technology 
Web Design Subcommittee 
Received on Thursday, 13 July 2000 13:58:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:57 UTC