- From: Al Gilman <asgilman@access.digex.net>
- Date: Mon, 26 Oct 1998 00:31:27 -0500 (EST)
- To: chisholm@trace.wisc.edu (Wendy A Chisholm)
- Cc: w3c-wai-gl@w3.org
Seems more logical the new way. Al to follow up on what Wendy A Chisholm said: > From w3c-wai-gl-request@w3.org Fri Oct 23 13:55:01 1998 > Resent-Date: Fri, 23 Oct 1998 13:48:49 -0400 (EDT) > Resent-Message-Id: <199810231748.NAA24036@www19.w3.org> > Message-Id: <199810231748.MAA29889@trace.wisc.edu> > X-Sender: chisholm@trace.wisc.edu > X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 > Date: Fri, 23 Oct 1998 12:41:45 -0500 > To: w3c-wai-gl@w3.org > From: Wendy A Chisholm <chisholm@trace.wisc.edu> > Subject: combining techniques > Resent-From: w3c-wai-gl@w3.org > X-Mailing-List: <w3c-wai-gl@w3.org> archive/latest/905 > X-Loop: w3c-wai-gl@w3.org > Sender: w3c-wai-gl-request@w3.org > Resent-Sender: w3c-wai-gl-request@w3.org > Precedence: list > Hi, > > In the current public draft of the guidelines (19980918) in the section on > alternative text (A.1), there is a technique devoted to OBJECT. In the > proposed rewording that follows, the information about OBJECT has been > incorporated into the discussions on how to provide text for images and > applets > (techniques 1 and 2). This was done to make the techniques more > long-lasting. Note also that the HTML specific stuff is an EXAMPLE of how to > satisfy the technique rather than part of the technique wording. > > thoughts? > --the editors > > A.1. Provide alternative text for all images, applets, and image maps. > [Priority 1] > This includes images used as submit buttons, bullets in lists, and all of the > links within an image map as well as invisible images used to layout a page. > Alternative text does not describe the visual appearance of an image, > applet, or > image map. Rather, it is used to represent the function that the image, > applet, > or image map performs whether it be decorative, informative, or for > purposes of > layout. If alternative text is not provided, users who are blind, have low > vision, or any user who cannot or has chosen not to view graphics will not > know > the purpose of the visual components on the page. Since "bare" ASCII art > (characters that form images) does not allow alt-text, it must be marked up > specially for this purpose. > > Techniques: > Provide alternative text for all images (e.g., via the "alt" attribute of IMG, > or via "title" or within the content of OBJECT). [Priority 1] Note. This > includes images used as image maps, spacers, bullets in lists, and links. > > Provide alternative text for all applets and other programatic > objects(e.g., via > the "alt" attribute or within the content of APPLET, or via the "title" > attribute or within the content of OBJECT). [Priority 1] (see also A.10) > > For all image map links > * Provide alternative text (e.g., via the "alt" attribute of AREA). [Priority > 1] > * Provide redundant textual links. [Priority 2 if client-side image maps are > used, Priority 1 for server-side] > Provide alternative text for graphical buttons (e.g., via the "alt" attribute > for INPUT type="image") [Priority 1] > > Do not use an image map to create a set of buttons in a form. Instead, use > separate buttons or images (accompanied by alternative text). [Priority 2] > > Replace ASCII art with an image and alternative text. [Priority 1 or 2 > depending > on the importance of the information (e.g., an important chart)] Note. If the > description of (important) ASCII art is long, provide a description in > addition > to alternative text (see A.2). >
Received on Monday, 26 October 1998 00:31:29 UTC