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

Re: RE: How to describe Flowcharts, Schematics, etc

From: Steven McCaffrey <smccaffr@MAIL.NYSED.GOV>
Date: Tue, 07 Sep 1999 08:30:32 -0400
Message-Id: <s7d4cd5b.099@MAIL.NYSED.GOV>
To: asgilman@iamdigex.net, charles@w3.org
Cc: w3c-wai-ig@w3.org
Indeed, not only is it completely incomprehensible with Lynx, but also with Internet Explorer 4.01.  (Caveat: At leastt, with my screen reader JFW 3.2).  In fact, this is such a good example of what not to do in termes of accessible design, perhaps I'll use it in one of my presentations.
When I use Lynx, I hear many many occurrences of "left bracket link right bracket" and "left bracket INLINE right bracket".  Apparently these are image map links with no alt text and images of some kind.
When I use Internet Explorer, my screen reader says many many  times just "link".  

I find it ironic (at first humorously so) that more and more articles are being written about accessible design (a  good thing of course) that are not accessible themselves, or are placed on a site in such a way that, although the article itself may be accessible, the path to get to it is not.

Steven McCaffrey
Information Technology Services

>>> Charles McCathieNevile <charles@w3.org> 09/04 8:44 PM >>>
But through Lynx the site is incomprehensible. I'll try it with something
else at work tomorrow.


On Fri, 3 Sep 1999, Al Gilman wrote:

  An interesting set of ideas are the ones Geoffrey Fox presented at the XML
  Implementers' Conference
  <http://www.npac.syr.edu/users/gcf/montrealxmlaug99/>.  He sees some of the
  same requirements for an articulable ontology arising out of
  telecollaboration as we want for accessibility.
  At 11:48 PM 8/29/99 -0400, Charles McCathieNevile wrote:
  >What we are trying to do is create the "science" that can provide as much
  >support as possible to the "art".
  >I have taken an example from SVG - scalable vector graphics. For people who
  >are interested in seeing the effect there are several open-source renderers
  >available already - see http://www.w3.org/Graphics/SVG for more information.
  >What I have done is to use metadata to describe the fact that two of the
  >objects in the image are connectors, and say what they connect.
  >The hope is that it is possible to use a metadata reader to generate the
  >description of the image, by finding descriptions of the different things
  >which are connected, and being able to say "a typical desktop PC
  >is connected by a twisted-pair cable (CableA) to another object (hub)".
  >The idea is that there are objects identified by names (CableA), (ComputerA),
  >(hub) with descriptive text (in the case of ComputerA and CableA) in the SVG
  >source. There is metadata - stuff that machines can read, which says that the
  >thing called CableA is a connection between ComputerA and hub, just as there
  >is metadata that an RDF-aware search engine can use to discover that there
  >are three creators of this document.
  >The example is at http://www.w3.org/1999/08/29-network.svg 
  >Charles McCN
  >On Fri, 27 Aug 1999, Bruce Bailey wrote:
  >  David, et al.,
  >  Audio description is art as much as science. 
  >[and some more]

--Charles McCathieNevile            mailto:charles@w3.org 
phone: +1 617 258 0992   http://www.w3.org/People/Charles 
W3C Web Accessibility Initiative    http://www.w3.org/WAI 
MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA
Received on Tuesday, 7 September 1999 08:35:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:05 UTC