- From: C.Bottelier <c.bottelier@ITsec.nl>
- Date: Tue, 04 Feb 2003 17:06:36 +0100
- To: Michael Cooper <michaelc@watchfire.com>
- CC: W3c-Wai-Ig <w3c-wai-ig@w3.org>
> ...... and just have the question - are > non-whitespace separators just important for links on the same "line" or is > it also important for links on different lines? I realize the definition of > "line" might depend on the user agent and there might be my answer, that you > can't count on a <br> element as creating the needed separation. When testing a site I was authoring (http://test.iradis.org/) using various screen-readers I had the problem with the links on the left size which are stacked under each other by means of using CSS to make them display:block and hiding the comma's between them for the CSS capable browsers. At least IBM HPR rambles the links as one (to fast read) sentence. I haven't got into a solution yet. The links (without CSS) render as a link lint like: Title: Link 1, link 2, link 3, link 4 Usng CSS this becomes +--------+ | Title | +--------+ | link 1 | | link 2 | | link 3 | | link 4 | +--------+ By hiding rhe comma's and making the links block. Since HRP reads out the contents after the CSS processing, and doesn't regard the link with pauses (only changes voice to female), and doesn't pause at line breaks or containing blocks. Christian
Received on Tuesday, 4 February 2003 11:06:46 UTC