From: "Paul Novitski" <[EMAIL PROTECTED]>
Hmm. The text-toggling examples folks have posted on this topic
use {display: none} to hide text. I'm under the impression that
some screen readers will not speak text that's been hidden with
{display: none}.
At 05:04 AM 1/30/2006, Al Sparber wrote:
JAWS presents the onClick event. But if supporting older, or more
poorly written readers, you would need to use positioning trick, I imagine :-)
Sorry, but aren't these apples & oranges? The triggering event is
one thing, the disappearing technique another. What I'm reading (or
perhaps misreading) is that even screen readers that respond to the
onclick method might not present text that's previously been hidden
with {display: none}.
Not having a screen reader to test on, I'd appreciate hearing from
someone who does:
When the styling for a block of text is changed from {display: none}
to {display: block} or {display: inline}, does your reader begin
reading it immediately? Or does it simply add that text into the
body of the page for eventual reading?
The reason I'm asking is that I've seen many cases in which the text
that's toggled doesn't immediately follow the link that triggers the
toggle, e.g.:
<a href="#">Toggle switch</a>
<h3>Some intervening text or heading.</h3>
<div>The text that suddenly appears.</div>
...or even where the trigger follows the text:
<div>The text that suddenly appears.</div>
<a href="#">Toggle switch</a>
If the user's reading point in the page is suddenly moved to the
toggled text block, an obvious inclusion in best practices would be
to mark up the toggled text immediately following the trigger without
any intervening content.
Paul
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
