The problem is that the headings are styled as display: none. Many screenreaders (Jaws among them) only read the screen-rendered content, and so ignore any element with display: none. One solution might be to shrink the headings down to pixel size: h1 {height: 0; width: 0; overflow: hidden;} and then use absolute positioning to move them somewhere inconspicuous. Chris On 10/26/06, Geoff Stephens <GeoffsLists@geoffandwen.com> wrote: > > And did you test with assistive technology? Some of the headings aren't > showing up for my screen reader. I do not know whether this is the > result of something defined in a style somewhere, a bug in the way the > screen reader handles the content, or something else. > > The use of a list here is a good example of the trend to use lists as a > catch-all solution. This is made more unclear because, as I said, the > headings are not displayed as part of the content by my screen reader. > > <div id="breadcrumbs"> > <h1>You are in …</h1> > <ul> > <li class="home"><a title="Transport for London" href=" > http://www.tfl.gov.uk">Transport for London</a></li> > <li class="current"><span>Current section</span></li> > </ul> > </div> > One of the definitions of list is: > The property possessed by a line or surface that departs from the vertical > > > the following heading is the only heading I can recognize in the rendered > version: > <h1>Please select from the options below before proceeding.</h1> > > Maybe I'm out of the loop on the current practices with regard to Title > and Alt atributes, but is there any reason why you use both? Unless you > know how assistive technologies handle these attributes you run the risk of > possibly conveying an unintended meaning. This is further complicated by > the fact that assistive technology is apparently electing to handle Alt and > Title in whatever way they think best. >Received on Thursday, 26 October 2006 18:10:46 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:25 GMT