Membership Tool design meeting

[Marc Brierley]

Maybe. The markup/js in question is:
<div id="layer1"><span id="close"><a  
href="javascript:setVisible('layer1')" style="text-decoration:  
none"><strong>Close</strong></a></span>
             <p>This course offers a wide-ranging overview of the  
literatures of the Americas
               in comparative perspective, emphasizing continuities  
and crises
               that are common to North American, Central American,  
and South...
              </p>
</div>
<a href="#" onclick="setVisible('layer1');return false"  
target="_self">Show/Hide</a>

with css:
#layer1 {
	position: absolute;
	visibility: hidden;
	width: 400px;
	height: 300px;
	left: 300px;
	top: 100px;
	background-color: #fff;
	border: .5px solid #000;
	padding: 10px;
}

-mARC

On Nov 30, 2007, at 12:09 PM, Michael S Elledge wrote:

> Hi Marc--
>
> Are you asking if JAWS reads the specifications "popup"?  If so, it  
> doesn't. :-)  Although it did read across the page which was  
> strange, as it was on a single line.
>
> Mike
>
> Marc Brierley wrote:
>> Though I put in no labels for navigation purposes, I did put the  
>> content for the layer next to the Hide/Show controller remembering  
>> some accessibility advice about that awhile ago. Then the screen  
>> reader (I know, just one modality) would get the content inline,  
>> right?
>>
>> [adding accessibility list, for reference:
>>> The mockups are here:
>>> http://brierley.stanford.edu/membership/mysites.html
>>> http://brierley.stanford.edu/membership/allsites.html
>> ]
>>
>> -mARC
>>
>> On Nov 30, 2007, at 9:15 AM, Colin Clark wrote:
>>
>>> Adam,
>>>
>>> Adam Marshall wrote:
>>>> .... and ensure everything works when JavaScript has been disabled?
>>>
>>> Good point. While I think graceful degradation is a very useful  
>>> technique for backwards compatibility, the argument about turning  
>>> off JavaScript for accessibility reasons is dated and inaccurate  
>>> at this point.
>>>
>>> WCAG 1.0 was written back in the late '90s, when certain screen  
>>> readers had trouble with certain types of scripts. For years now,  
>>> this incompatibility has been resolved.
>>>
>>> If done right, and carefully marked up with additional semantics  
>>> such as those in the Accessible Rich Internet Applications spec, I  
>>> think DHTML will make Web applications more accessible than ever.  
>>> We have to be very careful to think of keyboard accessibility,  
>>> flexible layouts, high contrast styles, and live regions. But it's  
>>> very possible to make fully accessible JavaScript user interfaces.  
>>> In fact Fluid is specifically pursuing this approach, building  
>>> components and a framework that make it easier to build accessible  
>>> DHTML.
>>>
>>> We shouldn't let WCAG 1.0's dated requirements stop us from using  
>>> JavaScript. We just have to do it right. I've written a checklist  
>>> for developers, providing an overview of DHTML techniques:
>>>
>>> http://wiki.fluidproject.org/display/fluid/DHTML+Developer+Checklist
>>>
>>> Colin
>>>
>>> --Colin Clark
>>> Technical Lead, Fluid Project
>>> Adaptive Technology Resource Centre, University of Toronto
>>> http://fluidproject.org
>>>
>>> ----------------------
>>> This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal 
>>> ) from the DG: User Interaction site.
>>> You can modify how you receive notifications at My Workspace >  
>>> Preferences.
>>>
>>
>> ----------------------
>> This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal 
>> ) from the WG: Accessibility site.
>> You can modify how you receive notifications at My Workspace >  
>> Preferences.
>>
>>
>>
> [see attachment: "elledge.vcf", size: 326 bytes]
>
>
> Attachments:
>
> elledge.vcf
> https://collab.sakaiproject.org/access/content/attachment/5f4465cb-d630-4e95-801c-75316e51b4bf/elledge.vcf
>
> ----------------------
> This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal 
> ) from the DG: User Interaction site.
> You can modify how you receive notifications at My Workspace >  
> Preferences.
>