Expanding the web's potential for people with disabilities

Getting Started

Introduction to web accessibility

WebAIM Training

May 21-22
Training Details

From the Blog

Community

You are here: Home > TEITAC Archives > Mailing List Archives

Thread Subject: Re: Non-Coded Tactile Definition

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Whitney Quesenbery
Date: Mon, Mar 03 2008 9:20 PM

Return to this mailing list's archives
View all messages in this thread
Next message in thread: Sean Hayes: "Re: Non-Coded Tactile Definition"
Previous message in thread: Gregg Vanderheiden: "Re: Non-Coded Tactile Definition"
Messages sorted by: Author | Thread | Date

<html>
<body>
I have updated Version 2 and the definition accordingly. 
At 05:26 PM 3/3/2008, Gregg Vanderheiden wrote: 
<blockquote type=cite class=cite cite="">
 I agree with you Sean 
  
  
I think we should change  non-coded to ?simple? 
  
I also edited the ?Braille? note a bit since it was misread. 
  
Here is what we get 
  
  
  
  
  
 
<h3>Simple tactile form
</h3> 
Tactile form that does not require
the memorization of any non-trivial spatial or temporal tactile patterns.
 
 
Note 1: Simple
vibration or switch up/down positions are examples of simple tactile
forms. 
Note 2: Braille, tactile Morse code, and vibration patterns are
examples of more complex tactile forms that require memorization of
non-trivial spatial and tactile patterns respectively. 
Note 3: Different numbers of tactile buzzes, or different
frequency buzzes would be non-trivial patterns and would not be simple
tactile forms. 
  
 
<h3>1-E - Visual
Information (Partial recommendation, No quorum) </h3> 
All information that is needed for
operation and use that is provided in visual form must also be available
in at least one mode in audio form or in simple tactile form,
either directly or { whichever ending we decide
on}.     Visual content that includes text and that
is closed due to Digital Rights Management (DRM) such that it cannot be
rendered in audio form by AT and other players must include an audio form
that can be. 
 
Note 1: Braille is not excluded and
is in fact encouraged but cannot be the only non-visual way that
information is presented. 
 
Note 2: Section 255 and Section 508
treat AT solutions differently, so review section XX of this document
before implementing a solution. 
  
  
Gregg
 
 --
------------------------------ 
Gregg C Vanderheiden Ph.D. 
  

<dl>
<dl>
<dd>  
<hr>
<div align="center"></div>

<dd>From:
= EMAIL ADDRESS REMOVED =
[<a href="mailto: = EMAIL ADDRESS REMOVED = " eudora="autourl">
mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of
Sean Hayes 

<dd>Sent: Tuesday, February 19, 2008 4:35 PM 

<dd>To: TEITAC Committee 

<dd>Subject: Re: [teitac-committee] Add morse code 

<dd>I don?t like the term ?non-coded tactile
form? as its being used. An on-off switch is ?coded? - you need to know
the polarity of the switch (is up=off or up=on), even a vibration can be
considered coded depending on what the vibration ?means? (incoming phone
call, text message, appointment?) 

<dd>  

<dd>A truly non-coded tactile form would be one where the information
state of the item is directly determinable by tactile inspection alone
(e.g. a radiator being warm or cold). A vibration which is just ?give me
some attention? might be considered non-coded. 

<dd>  

<dd>I suggest perhaps: complex coded tactile form and simple coded
tactile form as the terms. Or move the on-off example into the coded
side. 

<dd>  

<dd>Sean
Hayes 

<dd>Incubation Lab 

<dd>Accessibility Business Unit 

<dd>Microsoft 

<dd>  

<dd>Office:  +44 118 909 5867, 
 

<dd>Mobile: +44 7875 091385 

<dd>  

<dd>From:
= EMAIL ADDRESS REMOVED =
[<a href="mailto: = EMAIL ADDRESS REMOVED = " eudora="autourl">
mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of
Gregg Vanderheiden 

<dd>Sent: 05 February 2008 19:32 

<dd>To: 'TEITAC Committee' 

<dd>Subject: [teitac-committee] Add morse code 

<dd>  

<dd>On the call Brad mentioned ?tactile Morse
code? as an example of coded tactile form. 

<dd>  

<dd>I would suggest that we add  ?tactile Mores code? in the list of
examples of ?coded-tactile form?. 

<dd>  
 

<dd>Gregg 
 

<dd>------------------------ 

<dd>Gregg C Vanderheiden Ph.D. 

<dd>Professor - Depts of Ind. Engr. &
BioMed Engr. 

<dd>Director - Trace R & D Center 

<dd>University of Wisconsin-Madison
 

<dd><
<a href="http://trace.wisc.edu/">

http://trace.wisc.edu/</a>
>
FAX 608/262-8848  

<dd>DSS Player at
<a href="http://tinyurl.com/dho6b">http://tinyurl.com/dho6b</a> 

<dd>If Attachement is a mail.dat try
<a href="http://www.kopf.com.br/winmail/">
http://www.kopf.com.br/winmail/</a> 
 

<dd>
<a href="http://trace.wisc.edu:8080/mailman/listinfo/"> </a> 

<dd>  

<dd>  
 

</dl>
</dl>

Next message in Thread: Sean Hayes: "Re: Non-Coded Tactile Definition"
Previous message in Thread: Gregg Vanderheiden: "Re: Non-Coded Tactile Definition"

WebAIM is an initiative of: