On Tue, Jan 21, 2014 at 9:50 PM, Nancy K <nancythirt...@yahoo.com> wrote: > I don't know if any of these links will help - > > Invisible content just for screen reader users: > http://webaim.org/techniques/css/invisiblecontent/#techniques >
Hmmm.... that might be the way to do it. Have the <h1> as Marcus did it, but give it text that a screen reader will see, like "What do you want to do today?" or something that would make sense as the parent of the home page options. But then use CSS to hide the text from the design. That's probably better than having an empty <h1>. Thanks! -Rob > Cynthia Says for Section 508/WCAG2.0 (A thru AAA) accessibility (enter the > url online): > http://www.cynthiasays.com/? > > Colorblind tests (enter url online): > http://colorfilter.wickline.org/ > > html5 validator: > html5.validator.nu > > > Nancy > > Nancy Web Design > Free 24 hour pass to lynda.com. > Video courses on SEO, CMS, > Design and Software Courses > > > > > ________________________________ > From: Rob Weir <apa...@robweir.com> > To: "dev@openoffice.apache.org" <dev@openoffice.apache.org> > Sent: Tuesday, January 21, 2014 1:39 PM > Subject: Re: First look at www.openoffice.org accesibility > > > On Tue, Jan 21, 2014 at 4:09 PM, Marcus (OOo) <marcus.m...@wtnet.de> wrote: > >> >> >> In the meantime it's already online on www.oo.o. I've added a h1 tag and >> fixed the double-link problem. >> >> @Rob: >> Please can you test if this is now OK in the screen reader? >> >> Thanks >> >> > > Here's the tool I used to check: > > http://wave.webaim.org > > The duplicate links problem is gone. That's good news. > > The error about the missing <h1> is gone. But now it gives an error > for the <h1> with no content. > > I wonder whether the "real" solution here is to make those main > options into <h1>'s and update the CSS accordingly? If we use a > specific class for those headers we won't conflict with the <h1>'s on > other pages, which are styled differently. > > The only other error we have on the home page (and the other templated > pages) is the lack of the language identifier, and it sounds like Dave > had a good solution there. > > Regards, > > -RobboR > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
