RE: [WSG] a WCAG 2.0 question

2009-03-13 Thread Jens-Uwe Korff
I'm also bruised by new windows I didn't want and links which apparently didn't work because they refreshed an existing window below the current one. I second the line of argumentation against new windows. Even if screen readers can deal with them better now, I'd like to keep the user in control

RE: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Foskett, Mike
An excellent tool. I'm intrigued as to why this code would flag an error: titleWelcome to siteName - blah blah blah/title ... h1a href=/siteName/a/h1 ... h1Welcome yada yada yada/h1 Live page: http://websemantics.co.uk/ Test result page report:

Re: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Kay in t Veen - Gmail
double h1 tags are never good! chechout http://slipper-shop.nl 1 h1 1 h2 multiple h3 On Mar 13, 2009, at 11:33 AM, Foskett, Mike wrote: An excellent tool. I'm intrigued as to why this code would flag an error: titleWelcome to siteName - blah blah blah/title ... h1a

RE: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread michael.brockington
-Original Message- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Kay in t Veen - Gmail Sent: 13 March 2009 10:59 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released! double h1 tags are never

RE: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Foskett, Mike
Hey Kay, I'll have to respectively disagree about h1 tags. The Illinois FAE has it about right: max 2 h1's, content in h1's replicated in the title. It's just the test appears to fail correct detection on that criteria. http://slipper-shop.nl/ I don't think we're looking at the same page?

Re: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Jon Gunderson
Mike, I just wanted to thank you for your feedback. Also the Firefox Accessibility Extension can be found at: http://firefox.cita.uiuc.edu Jon On Fri, Mar 13, 2009 at 5:33 AM, Foskett, Mike mike.fosk...@uk.tesco.com wrote: An excellent tool. I'm intrigued as to why this code would flag an

RE: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Stuart Foulstone
possibly something to do with: #websemantics a {display:none} producing an empty h1/h1 ? On Fri, March 13, 2009 10:33 am, Foskett, Mike wrote: An excellent tool. I'm intrigued as to why this code would flag an error: titleWelcome to siteName - blah blah blah/title ... h1a

RE: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Stuart Foulstone
Err... sorry about my initial confusion - I've had a long day. Perhaps, The text content of each h1 element should match all or part of the title content. means that ALL the h1 text content, Welcome - work, you're welcome to it should match PART of the title content - which of course it

RE: [WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-13 Thread Stuart Foulstone
but then you wouldn't have, # Each h1 element must have text content. # Pass Perhaps its the other h1 and The text content of each h1 element should match all or part of the title content. means that ALL it's text content, Welcome - work, you're welcome to it should match part of the

Re: [WSG] a WCAG 2.0 question

2009-03-13 Thread Peter Dolkens
Ideally they should warn or give some indication that they're going to open in a new window. I know the way i personally browse sites means I hate it when they open things in new windows. If i want new windows, I hold control down as I click, or middle click, or whatever. It's default