E-mail List Archives
Re: Hiding Legends
From: Dean Hamack
Date: Oct 16, 2008 10:50AM
- Next message: Dean Hamack: "Re: Hiding Legends"
- Previous message: Tim Beadle: "Re: Hiding Legends"
- Next message in Thread: Dean Hamack: "Re: Hiding Legends"
- Previous message in Thread: Tim Beadle: "Re: Hiding Legends"
- View all messages in this Thread
On 10/16/08 2:24 AM, "Tim Beadle" < <EMAIL REMOVED> > wrote:
> (We had this discussion re. asterisks to
> indicate "required field" only last week, and I posted a link to
> Natalie Downe's presentation-plus-notes from BarCampLondon5:
I remember the discussion and failed to see a compelling argument as to why
images needed to be used instead of some of the other methods that were
suggested. For example, even though I don't consider "*" to be an acronym or
an abbr, if the screenreader will speak "required field" for the title, I
think it's the lesser of two evils.
> It might seem offensive to purist sensibilities, but I've got to the
> point where theory doesn't matter *as much as* what works for the
The method I'm suggesting in this case would work fine for all users while
still following best practices. In the case of using an image for required
fields, it works great for completely blind users. But what happens when
someone with bad vision who has their their font size turned up can't see
your little ten pixel tall asterisk?
I've got to run off for a meeting, but since people are having a hard time
envisioning what I'm talking about here, I'll post a sample when I get back.
The negative margin idea suggested worked fine for hiding the legend. So as
long as the screenreader can still pick it up, I see no problem with it