[Wsuug] Updated/new site

Fri Feb 1 11:01:49 EST 2008

Well, that gets you into the situation of choosing between "standards" and
"usability" ... standards say to do it that way... usability may be an
issue...

On Feb 1, 2008 11:00 AM, Christopher Jones <chrismjones at gmail.com> wrote:

> I like the idea of hiding the h2 with media type aural, but does it work?
> As far as I know, no browser except Opera and Safari even attempts to handle
> the aural media type.  And no screen reader except EMACspeak does either.
>
> ~ Christopher
>
> On 2/1/08, Joshua McDonald <josh at thisisgrow.com> wrote:
> >
> > Some do and some don't...I always thought they didn't, then I downloaded
> > a trial of one at one time...and it did...i read up on it and it seems that
> > some do it, while others don't.
> >
> > One thing you can do, is hide the abbr (or the h2...whichever) from the
> > media type "aural".  That will make screen readers not read them...
> >
> > As with everything else...there are 50 ways to do this...and 50 opinions
> > to go with each of those ways...
> >
> >
> > On Feb 1, 2008 10:19 AM, Andrew Jaswa <ajaswa at gmail.com> wrote:
> >
> > > On Jan 27, 2008 6:31 PM, Andrew Jaswa <ajaswa at gmail.com> wrote:
> > > > <div id="Header">
> > > >                <h1><abbr title="Web Standards and Usability Users
> > > Group">WSUUG</abbr></h1>
> > > >                <h2>Web Standards and Usability User Group</h2>
> > > > </div>
> > >
> > > When I first wrote this I noticed there is one problem with the above
> > > solution. That is that some people/screen readers will read this as
> > > "Web Standards and Usability Users Group Web Standards and Usability
> > > Users Group". After mulling over this for a little bit more I'd like
> > > to propose another solution (which might fix the issue at hand) and
> > > get feedback on it.
> > >
> > > <head>
> > > <script>
> > > function fixHeader() {
> > >        var heading = document.createElement("h2");
> > >        var text = document.getElementById("name").title;
> > >        document.getElementById("Header").appendChild(heading);
> > >        heading.innerHTML = text;
> > > }
> > > </script>
> > > </head>
> > > <body onload="fixHeader();">
> > >                <div id="Header">
> > >                        <h1><abbr id="name" title="Web Standards and
> > > Usability Users
> > > Group">WSUUG</abbr></h1>
> > >                </div>
> > > </body>
> > >
> > > Will generate:
> > >
> > > <div id="Header">
> > >                <h1><abbr id="name" title="Web Standards and Usability
> > > Users
> > > Group">WSUUG</abbr></h1>
> > >                <h2>Web Standards and Usability Users Group</h2>
> > > </div>
> > >
> > > I guess the question then is will screen readers read generated markup
> > > and how well do they do it?
> > >
> > > Andrew
> > > _______________________________________________
> > > Wsuug mailing list
> > > Wsuug at list.wsuug.org
> > > http://www.thelinuxlink.net/mailman/listinfo/wsuug
> > >
> >
> >
> >
> > --
> > Joshua McDonald
> > Grow Interactive
> > www.thisisgrow.com
> > 757-248-5274
> > 757-248-5275 (f)
> >
> > _______________________________________________
> > Wsuug mailing list
> > Wsuug at list.wsuug.org
> > http://www.thelinuxlink.net/mailman/listinfo/wsuug
> >
> >
>
> _______________________________________________
> Wsuug mailing list
> Wsuug at list.wsuug.org
> http://www.thelinuxlink.net/mailman/listinfo/wsuug
>
>

-- 
Joshua McDonald
Grow Interactive
www.thisisgrow.com
757-248-5274
757-248-5275 (f)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.thelinuxlink.net/pipermail/wsuug/attachments/20080201/df583b25/attachment.html