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

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

From: <Becky_Gibson@notesdev.ibm.com>
Date: Thu, 28 Apr 2005 12:51:10 -0400
To: w3c-wai-gl@w3.org
Message-ID: <OF5A6FB336.6B95A7A4-ON85256FF1.00597824-85256FF1.005CD9D6@notesdev.ibm.com>

Wendy responded to my questions about how to define non-text content. 
<wendy>
Do you feel that covers the issues you raised?  If not, can you think of 
another way to define non-text content that would cover them? Or, do you 
think we should leave widgets out of Guideline 1.1 all together?  If so, 
can you propose an alternative criterion?
</wendy>

I think that part of my problem is still understanding "non-text" content. 
 I gave three examples, google suggests, a calendar popup widget and form 
that hides and show additional form fields based on a previous user 
selection.  While all of these examples use JavaScript and might be 
defined as widgets, I think only the calendar widget might be classified 
as non- text.  But, it does use unicode to display the calendar so 
technically it could be thought of as text content. 

So, I think we should leave widgets out of guideline 1.1.  Because I don't 
think you can always provide a textual alternative. For example, I don't 
think that including a label that identifies the google suggests widget is 
providing a text alternative - it is just properly labeling the control. I 
think that would be covered under the spirit of Principle 3 - Content and 
controls must be understandable, but I can't map it directly to a 
particular guideline or success  criteria.  With many JavaScript widgets, 
if your baseline does not include JavaScript then you will likely have to 
provide more than just a text alternative.  It is possible the site will 
have to have additional links and pages that are invoked when JavaScript 
is not present.   I think that goes beyond providing a text alternative. 
I'm sorry, I don't have a new proposal - I am just thinking out loud. 
Hopefully someone can clear up my confusion!

-becky


Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com
Received on Thursday, 28 April 2005 16:51:29 UTC

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