Re: [WSG] WCAG Samurai Errata

Tee G.Peng wrote: Hi, I finally got a chance to read the WCAG Samurai Errata. Maybe something to do with my understanding in English, I see there is autority tone in there. Guideline 11, bullet point 3, point 4: "I really mean this..." Not so convincing, perhaps? Lars Gunther *

Re: [WSG] WCAG Samurai Errata

Oops, Joe's just posted the comments email address: samurai at the domain wcagsamurai.org Apologies, -Alastair *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/

Re: [WSG] WCAG Samurai Errata

Steve Green wrote: The process for commenting is a bit shambolic, and it is not clear that comments are particularly welcome. There is no stated process, so people have been commenting in various places in the blogs If you check the various blogs, you'll see Joe has been following them closely

RE: [WSG] WCAG Samurai Errata

rom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tee G.Peng Sent: 11 June 2007 07:12 To: wsg@webstandardsgroup.org Subject: Re: [WSG] WCAG Samurai Errata On Jun 7, 2007, at 10:22 PM, Kane Tapping wrote: > > I have been reading with interest the WCAG Samurai Errata ( http:// >

Re: [WSG] WCAG Samurai Errata

On Jun 11, 2007, at 3:12 PM, Tee G.Peng wrote: Lastly, I did not aware we can do this ? Did a brief reading in CSS 3 spec and I tried testing it in Safari, Firefox and Opera (thought one of the browsers has already supported some of CSS3 elements) but none of them work. " If images must

Re: [WSG] WCAG Samurai Errata

On Jun 7, 2007, at 10:22 PM, Kane Tapping wrote: I have been reading with interest the WCAG Samurai Errata ( http:// wcagsamurai.org/errata/intro.html ) and am suprised to have not found it discussed on WSG as of yet. Hi, I finally got a chance to read the WCAG Samurai Errata. Maybe so

Re: Accessible auto-submit dropdowns [WAS: Re: [WSG] WCAG Samurai Errata]

PROTECTED] *On Behalf Of *Sander Aarts *Sent:* 09 June 2007 05:30 *To:* wsg@webstandardsgroup.org *Subject:* Accessible auto-submit dropdowns [WAS: Re: [WSG] WCAG Samurai Errata] Matthew Pennell schreef: On 08/06/07, Lea de Groot <[EMAIL PROTECTED]> wrote: > > On Fri, 8 Jun 2007 07:27:46 +0

RE: Accessible auto-submit dropdowns [WAS: Re: [WSG] WCAG Samurai Errata]

auto-submit dropdowns [WAS: Re: [WSG] WCAG Samurai Errata] Matthew Pennell schreef: On 08/06/07, Lea de Groot <[EMAIL PROTECTED]> wrote: On Fri, 8 Jun 2007 07:27:46 +0100, Matthew Pennell wrote: > Auto-submitting dropdowns are not usable by keyboard users. More informatio

Accessible auto-submit dropdowns [WAS: Re: [WSG] WCAG Samurai Errata]

Matthew Pennell schreef: On 08/06/07, *Lea de Groot* <[EMAIL PROTECTED] > wrote: On Fri, 8 Jun 2007 07:27:46 +0100, Matthew Pennell wrote: > Auto-submitting dropdowns are not usable by keyboard users. More information, please? :) Auto-submit dropdowns m

Re: [WSG] WCAG Samurai Errata

From: "Thierry Koblentz" <[EMAIL PROTECTED]> uments". > As a side note, it also says: > "Earlier versions of this script did not use document.write(), I was using > the DOM to plug the stylesheets in the HEAD element. Unfortunately, setting > the rel attribute of the LINK element makes Safari "go

RE: [WSG] WCAG Samurai Errata

> On Behalf Of David Dorward > > http://www.tjkdesign.com/articles/toggle_elements.asp > > Despite the claims of the article, using document.write() will not > work in XHTML[1] documents. Browsers don't support it in XHTML mode. You mean served with an application/xhtml+xml MIME type, but AFAIK,

Re: [WSG] WCAG Samurai Errata

On 8 Jun 2007, at 16:22, Thierry Koblentz wrote: The idea is not to parse the tree looking for an element to hide, but rather use document.write() to write CSS declaration(s) that'll hide that element right from the start. http://www.tjkdesign.com/articles/toggle_elements.asp Despite th

RE: [WSG] WCAG Samurai Errata

> On Behalf Of [EMAIL PROTECTED] > > If you use JS to write specific styles to the document, there > > should be > > nothing "popping in and out". > > How do you work that one out? Javascript cannot run until the page has > (mostly) loaded, so I can vouch for getting a 'flash of extra content' >

Re: [WSG] WCAG Samurai Errata

On 08/06/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: How do you work that one out? Javascript cannot run until the page has (mostly) loaded, so I can vouch for getting a 'flash of extra content' on many of my pages. Since the hidden content cannot be re-enabled without JS on, I have to make

RE: [WSG] WCAG Samurai Errata

> If you use JS to write specific styles to the document, there > should be > nothing "popping in and out". > > --- > Regards, > Thierry | www.TJKDesign.com How do you work that one out? Javascript cannot run until the page has (mostly) loaded, so I can vouch for getting a 'flash of extra conte

RE: [WSG] WCAG Samurai Errata

> On Behalf Of Lea de Groot > Having elements pop in and out on a slow connection is very confusing > for Joe Public, and if its a page or site that will take their money > its important Not to make them feel in anyway insecure on what is > happening. > Because of this, I've made a specific decisio

Re: [WSG] WCAG Samurai Errata

On 08/06/07, Stuart Foulstone <[EMAIL PROTECTED]> wrote: I think the "as with" here means "as example". The point is the use of CSS to avoid using an img tag in the HTML. The fact that they give the most sensible way of doing this as an example does not preclude you using other CSS to acheve t

Re: [WSG] WCAG Samurai Errata

Hi, I think the "as with" here means "as example". The point is the use of CSS to avoid using an img tag in the HTML. The fact that they give the most sensible way of doing this as an example does not preclude you using other CSS to acheve the same result. Stuart. On Fri, June 8, 2007 9:21 am

Re: [WSG] WCAG Samurai Errata

Hi, I think you may be misunderstanding what is meant by "distiguishing" information. If you have a number of headers (or whatever) concerning "Californian Fires", say, Californian Forest Fires - introduction. Californian Forest Fires - more information. The bit that distinguishes the headin

Re: [WSG] WCAG Samurai Errata

Another interesting one, under Guideline 12 (although it actually relates to WCAG 13.8): "Do not place distinguishing information at the beginning of headings, paragraphs, lists, etc. unless document semantics warrant it." I'd always interpreted that guideline as being a nod to both usability an

RE: [WSG] WCAG Samurai Errata

ent: Friday, 08 June, 2007 9:53 AM To: wsg@webstandardsgroup.org Subject: RE: [WSG] WCAG Samurai Errata Matthew Pennell wrote: >> I think it's been shown that just about all keys interfere with someone's shortcuts, >> whether it's a browser, screenreader, foreign char

Re: [WSG] WCAG Samurai Errata

This is an interesting one: "If images must be used for list bullets, do so only using CSS, as with ul { list-style: url("arrow.gif") disc }" Like a lot of people, I use CSS background-image to place a graphic at the top left of LI items, with a bit of left padding so the text makes space. What

Re: [WSG] WCAG Samurai Errata

On 08/06/07, Lea de Groot <[EMAIL PROTECTED]> wrote: On Fri, 8 Jun 2007 07:27:46 +0100, Matthew Pennell wrote: > Auto-submitting dropdowns are not usable by keyboard users. More information, please? :) Auto-submit dropdowns mostly work by triggering the onchange event of the SELECT element.

RE: [WSG] WCAG Samurai Errata

Matthew Pennell wrote: >> I think it's been shown that just about all keys interfere with someone's shortcuts, >> whether it's a browser, screenreader, foreign characters, or whatever. Frank Palinkas wrote: > Interesting. Please tell me where this info is shown? I'd like to know more. Some Info:

Re: [WSG] WCAG Samurai Errata

On Fri, 8 Jun 2007 16:49:00 +1000, Kane Tapping wrote: > I took this one to mean that you should be writing your form in a > accessible and non-js way first then use JS to HIJAX ( > http://ajaxian.com/archives/hijax-graceful-degration) that version to > provide enhanced useability.This way you ge

RE: [WSG] WCAG Samurai Errata

Matthew Pennell Sent: Friday, 08 June, 2007 8:26 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] WCAG Samurai Errata On 08/06/07, Frank Palinkas <[EMAIL PROTECTED]> wrote: /* Guideline 9.4: Do not attempt to create your own tab order. That is a job for a browser and adaptive te

Re: [WSG] WCAG Samurai Errata

Hi , > - no noscript? > I still use it to add a submit button to dropdowns which are otherwise > javascript driven - I thought I was doing a good thing! (Wah! :( ) > Hmm.. its in the introduction, but not in the document. Thats not > right, surely? I took this one to mean that you should be wri

Re: [WSG] WCAG Samurai Errata

On Fri, 8 Jun 2007 07:27:46 +0100, Matthew Pennell wrote: > Auto-submitting dropdowns are not usable by keyboard users. More information, please? :) warmly, Lea -- Lea de Groot Elysian Systems Brisbane, Australia *** List Guidelin

Re: [WSG] WCAG Samurai Errata

I like the way that the footer links rollover to black text on dark blue background - very accessible... ;) Matthew. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/jo

Re: [WSG] WCAG Samurai Errata

On 08/06/07, Lea de Groot <[EMAIL PROTECTED]> wrote: - no noscript? I still use it to add a submit button to dropdowns which are otherwise javascript driven - I thought I was doing a good thing! Auto-submitting dropdowns are not usable by keyboard users. Matthew. **

Re: [WSG] WCAG Samurai Errata

On 08/06/07, Frank Palinkas <[EMAIL PROTECTED]> wrote: /* Guideline 9.4: Do not attempt to create your own tab order. That is a job for a browser and adaptive technology. */ When and where needed (in web forms for instance), I create a tabindex order starting with the number 11 and proceed fro

Re: [WSG] WCAG Samurai Errata

On Fri, 8 Jun 2007 15:22:36 +1000, Kane Tapping wrote: > I have been reading with interest the WCAG Samurai Errata ( > http://wcagsamurai.org/errata/intro.html ) and am suprised to have not > found it discussed on WSG as of yet. Thank you! I missed this announcement, somehow. What a refreshing r

Re: [WSG] WCAG Samurai Errata

What is your opinion on the errata ? It's an excellent read. Certainly therapeutic, particularly with Joe Clarke's wonderfully acerbic wit showing in places. I think what it truly does is define the Best Practice accessibility which has evolved under WCAG 1.0, which made some assumptions which

RE: [WSG] WCAG Samurai Errata

Hi Kane, If it’s of help: /* Guideline 9.4: Do not attempt to create your own tab order. That is a job for a browser and adaptive technology. */ When and where needed (in web forms for instance), I create a tabindex order starting with the number 11 and proceed from there. This usually byp