Repeated links and accessibility

[Gonzalo Silverio]

Hi,

Nothing in the SG about this. Usual practice is to make the focal  
string a header, and structure the table correctly. These  
contextualizing strategies should take care of the issue, they tell  
me.  In Sean's example: "f2 1 (sean),"  "SOE Proficiencies-Row:  
Proficiency 1; Column: Stage 1-f2 1", etc. would be h4, and h5  
respectively.

  But I defer screen reader questions to people that use them.

Am concerned with the possible verbosity of the title attribute  
(specially the default OSP Matrix titles) doing more harm than good.

	-Gonzalo

On Jul 30, 2007, at 4:17 PM, Michael S Elledge wrote:

> Hi Sean--
>
> I think that having that information in the title tag makes sense.  
> Users can set JAWS to read title tags by default, but if they  
> don't, they can still understand the context of edit, etc. since it  
> will be read immediately after the document. It may be helpful to  
> add a column labeled "Actions" under which the edit, etc. items  
> fall to provide added context, since I'm assuming this is setup in  
> a table.
>
> I don't recall if this was covered in the original style guide.  
> Perhaps Gonzalo can shed some light there.
>
> Mike
>
> Sean Keesler wrote:
>> Is there a recommendation from anyone on the best Sakai way to   
>> display repeated links (ie: add-edit-delete) in a tool that meets   
>> accessibility guidelines?
>>
>> I noticed the following table in OSP:
>> http://alpha.lsb.syr.edu/~smkeesle/osp/viewCell.osp.html
>>
>> Which has repeated links for every item attached to a matrix  
>> cell.  The easiest way to handle it (which would be ridiculous)  
>> would be to  have links like: "Edit SOE Proficiencies-Row:  
>> Proficiency 1; Column:  Stage 1-f2 1".
>>
>> I've read that some folks use title attributes in their anchor  
>> tags  to designate a difference between instances of similar links:
>>
>> ie:
>> <a href="someplace" title="Edit SOE Proficiencies-Row: Proficiency  
>> 1;  Column: Stage 1-f2 1">Edit</a>
>>
>> I didn't wander across a Design Pattern for this...is there one?  
>> It  would seem to be a common enough issue to warrant a  
>> recommendation.
>>
>> ------------------------------
>> Sean Keesler
>> Project Manager
>> The Living SchoolBook
>> 030 Huntington Hall
>> Syracuse University
>> 315-443-3450
>>
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work
>>
>>
>>
>> <elledge.vcf>



  - Gonzalo

---------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20070730/c26edb53/attachment.htm>