W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

RE: Reopened issues - week of 19 April 2004

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Wed, 28 Apr 2004 14:03:35 -0500
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A1E3117@MAIL02.austin.utexas.edu>
To: <jasonw@ariel.ucs.unimelb.edu.au>
Cc: "Wendy A Chisholm" <wendy@w3.org>, <w3c-wai-gl@w3.org>

Thanks, Jason.

I've just been looking at 1.3 after reading Lisa's message, and it
occurs to me that the language there may be useful with respect to issue
#330 and difficult phrases like "programmatically located" and
"programmatically identified."  Would it work to say "... Available
through context, markup, or a data model"?

Or perhaps we should go in the other direction first: we need
plain-language equivalents for "programmatically identified" and
"programmatically located."  Everything I've tried ends up sounding like
either a use case or an aspect of user agent functionality; I'm having
trouble getting at what the content provider should do.


"Good design is accessible design." 
Please note our new name and URL!
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 512-495-4524
email jslatin@mail.utexas.edu
web http://www.utexas.edu/research/accessibility/


-----Original Message-----
From: Jason White [mailto:jasonw@ariel.ucs.unimelb.edu.au] 
Sent: Wednesday, April 28, 2004 4:07 am
To: John M Slatin
Cc: Wendy A Chisholm; w3c-wai-gl@w3.org
Subject: RE: Reopened issues - week of 19 April 2004

John M Slatin writes:
 > Re: Issue #330: On 25 March I sent a proposal to the list to reword
> success criteria under 3.1 [1]. The idea was to replace phrases such
as  > "programmatically located" in 3.1 Success Criteria with "available
> through context or markup," as follows:

One of the main reasons for using expressions such as "programmatically
identified" and "programmatically located" was to cover the case where
the content is not written in a markup language, but is provided in
another format that allows structural distinctions to be preserved.
Examples include XML information sets, API's, and data structures such
as the structure trees used in tagged PDF.

If we want these to be included, we need to say something more precise
than "context", and something more general than "markup".

Received on Wednesday, 28 April 2004 15:03:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:49 UTC