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

Re: Thinking aloud...Definitions (pre-Guideline 1.1 summary)

From: Lisa Seeman <lisa@ubaccess.com>
Date: Thu, 21 Apr 2005 16:04:26 +0200
Message-ID: <4267B2EA.2030904@ubaccess.com>
To: wendy@w3.org
CC: wai-gl <w3c-wai-gl@w3.org>

My overall comments to the definitions is that this is great work. 
However, along with a technical normative definition, could we have a 
simple language non-normative definition?

other comments inline  with "lisa:" before them...

>   2. Proposed definitions for text, unicode seem fairly
>      uncontroversial, need to discuss/close [see below]

lisa: Unicode could do with a simple language definition

>   3. Definition of "functionality" includes "convey information" and we
>      separate "provide function" from "convey information" in Guideline
>      1.1 Level 1 Success Criteria 1 and 2.  Therefore, either the SC
>      need to change or the definition of functionality needs to change.

lisa: Interesting, what about the space between conveying information 
and conveying a feeling or other form of  message
Such as large  Red format implying  important information

>
>    * text - A sequence of characters. Characters are those included in
>      the Unicode character set. Refer to Characters (in Extensible
>      Markup Language (XML) 1.1) for more information about the accepted
>      character range.


lisa: Simpler non normative explanation: Text - the standard  character 
set that can be  read and processes  by the browser. 

>
>    * Unicode - Unicode is a universal character set that defines all
>      the characters needed for writing the majority of living languages
>      in use on computers. 


lisa: this is nice. Add a paragraph brake before you get complicated...

> For more information refer to the Unicode
>      Consortium or to Tutorial: Character sets & encodings in XHTML,
>      HTML and CSS produced by the W3C Internationalization Working
>      Group.  [Additional clarification that gets a bit "success
>      criteria-ish": This does not mean that all documents should be
>      encoded in Unicode. It means that documents should only contain
>      characters defined by Unicode. Any encoding may be used for your
>      document as long as it is properly declared and is a subset of the
>      Unicode repertoire.]
>    * content -  Information that forms Web sites and Web applications:
>      the code and markup that define the structure, presentation, and
>      interaction, as well as text, images, and sounds that convey
>      information to the end-user.  based on definition in "Essential
>      Components of Web Accessibility"      
> <http://www.w3.org/WAI/intro/components>

lisa: What about the implicit stuff? Red format implies important etc..

>    * functional - performing or able to perform an action in response
>      to user input. [based on Merriam Webster's Medical Dictionary entry]

lisa: ! We said it included conveying information (and messages etc)
Is that included?

>
>   1. "widgets" that are created by attaching an event handler to an image
>   2. groups of widgets that form a Web application or a flash 
> application.

lisa: This brings us to an interesting discussion - that of a task
Tasks are a primary concept that we need to explore before we can move 
on to roles and what needs an equivalent.
We need  tasks to be  available in an accessible form.


All the best
Lisa
Received on Thursday, 21 April 2005 13:04:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC