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

RE: [techs] Gateway Techniques suggestion

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Wed, 10 Dec 2003 13:23:20 -0600
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A798D9D@MAIL02.austin.utexas.edu>
To: <david.donovan@hrdc-drhc.gc.ca>, <w3c-wai-gl@w3.org>

The Accessibility Institute Web site's How-to section includes scenarios like these.  For example, our Graphics section includes short tutorials about the following items:

Alt Text for a Logo
* Alt Text for Decorative Images and Spacers
* AltText for a Link that contains both Graphics and Text
* Including a Graph and Its Description on the Same Page
* A Graph with a Description in a Separate, Linked File
* Associating a Graph and its Description with the longdesc Attribute
list end
If anyone has a chance to look at these, I'd be glad of any feedback.  Each tutorial includes a working example, a brief description of the example, a slightly longer rationale/explanation of the technique employed, a link to source code for the example, an audio recording of JAWS reading the example (and a text transcript ofwhat it says), plus a link to the relevant WCAG 1.0 checkpoints and Section 508 (US) requirements.  The source code and applicable standards links open in new browser windows, as per the preference of our users.

http://www.utexas.edu/research/accessibility/resource/how_to/index.html

John



"Good design is accessible design." 
Please note our new name and URL!
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 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 david.donovan@hrdc-drhc.gc.ca
Sent: Wednesday, December 10, 2003 1:06 pm
To: w3c-wai-gl@w3.org
Subject: RE: [techs] Gateway Techniques suggestion



...
For example gateway techniques could separately consider scenarios such as  an image in a link : in this case a text equivalent should let the user know were the page links to 
An image in in a link that contains extra information: in this case a text equivalent include were the page links to, and any extra information in the image

My 2 cents...

In this example I suggest one common scenario we might want to look at is the standard practice of using logos as links to home pages. This practice involves using the image for at least two functions (organizational identifier and navigational function). In this scenario would it not be best to recommend both placing the alt text for the organizational identifier within the img alt tag and including the navigational text information within the title attribute of the address element? This could also apply to other instances where images in links are used to attempted to provide context to the linked page (i.e. an image of a computer that links to a store's computer sales page. In this case "computer" would be placed within the img alt tag and "Link to Computer Sales page" within the title attribute of the address element). Let the img alt tag describe the image and the let the address title describe the link.

Cheers,

David Donovan
INET Consultant
Persons with Disabilities Online
http://www.pwdonline.ca/
Phone: 204-983-4094
Received on Wednesday, 10 December 2003 14:23:21 GMT

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