Laura Stewart wrote: ... > For us to claim that the documentation is accessible, the graphic > files need to contain hidden text that screen readers can read. The > appearance of the text when the mouse hovers over the graphic is > irrelevant from an accessibility standpoint. So if the line feed > characters cause the text to appear disjointed in the textbox that is > not important. It doen't look very good for those of us who can see > the text, but we are not the target audience for this "alternative" > text.
I really like the goals description on the w3c guidelines site [1]: > The primary goal of these guidelines is to promote accessibility. However, > following them will also make Web content more available to all users, > whatever user agent they are using (e.g., desktop browser, voice browser, > mobile phone, automobile-based personal computer, etc.) or constraints they > may be operating under (e.g., noisy surroundings, under- or over-illuminated > rooms, in a hands-free environment, etc.). Following these guidelines will > also help people find information on the Web more quickly. These guidelines > do not discourage content developers from using images, video, etc., but > rather explain how to make multimedia content more accessible to a wide > audience. I'm already thinking how I can improve the Derby Tutorial at http://db.apache.org/derby/papers/DerbyTut since I have to update it anyhow for 10.2.2.0. I don't think there's anything wrong with trying to make the text look good as long as we understand why we're doing that -- sort of separate the "must have" (we want screen readers to be able to read it) from the "nice to have" (it'd be nice if the text were visible in an environment in which the picture doesn't render well, or whatever). -jean [1] http://www.w3.org/TR/WAI-WEBCONTENT/ > BTW - thanks for the links :-) > > Laura > > On 1/24/07, Jean T. Anderson <[EMAIL PROTECTED]> wrote: > >> Jean T. Anderson wrote: >> > Hi, Laura, >> > >> > I'm trying to understand the accessibility issues that DERBY-1842 wants >> > to address. After a quick search I found the "Section 508" web site >> for >> > the U.S. govt, which looks like it has great links to all sorts of >> > resources: >> > >> > http://www.section508.gov/ >> > >> >> browsing links from the section508 site, I found the w3c Content >> Accessibility Guidelines: >> >> http://www.w3.org/TR/WAI-WEBCONTENT/ >> >> this may have already been mentioned on derby-dev. If so, my apologies, >> >> -jean >> > >
