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

RE: Glossary "non-text content" Small Nit

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Thu, 13 Oct 2005 23:43:35 -0500
To: "'John M Slatin'" <john_slatin@austin.utexas.edu>, "'Johannes Koch'" <koch@w3development.de>, "'WAI WCAG List'" <w3c-wai-gl@w3.org>
Message-ID: <005701c5d079$d756fe30$ee8cfea9@NC6000BAK>

Yes

I think that is correct.  

The transport is irrelevant.  It is the form of the data when it is 'viewed'
or processed by the user agent. 
 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of John M Slatin
Sent: Thursday, October 13, 2005 9:44 AM
To: Johannes Koch; WAI WCAG List
Subject: RE: Glossary "non-text content" Small Nit


I think this thread began as a discussion about how to define non-text
content for the purposes of WCAG 2.0. I think there was an unspoken
assumption that the problem has to do with non-text content as it is
rendered for users, rather than with the form in which such content is
transmitted.

Does that distinction make sense? Can we focus on a glossary definition that
will help developers and other readers of WCAG 2.0 understand when something
qualifies as non-text content (and is thus within the scope of Guideline
1.1)?

Thanks,
John

"Good design is accessible design."

Dr. John M. Slatin, Director
Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, fax 512-495-4524
email jslatin@mail.utexas.edu
Web http://www.utexas.edu/research/accessibility 



-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Johannes Koch
Sent: Thursday, October 13, 2005 9:25 AM
To: 'WAI WCAG List'
Subject: Re: Glossary "non-text content" Small Nit



Richard Ishida wrote:
>> I cannot understand this.  Images and binary content are transferred 
>> as bytes, but not Unicode characters, surely.

Chris Ridpath wrote:
> Images and binary content are usually send as ASCII characters. Weird 
> eh?
> 
> Here's what Wikipedia has to say about the MIME standard: 
> http://en.wikipedia.org/wiki/MIME

In MIME, yes. But this is Web Content Accessibility, not Email
Accessibility. However, there may be situations when binary data are stored
as characters, Base64 encoded, e.g. when using the data URL scheme.
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
                             (Te Deum, 4th cent.)
Received on Friday, 14 October 2005 04:43:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:40 GMT