Re: [WSG] WCAG Samurai Errata

2007-06-12 Thread Keryx Web
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

2007-06-11 Thread Steve Green
:[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:// wcagsamurai.org/errata/intro.html ) and am

Re: [WSG] WCAG Samurai Errata

2007-06-11 Thread Alastair Campbell
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

2007-06-11 Thread Alastair Campbell
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:

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

2007-06-09 Thread Steve Green
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

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

2007-06-09 Thread Darren West
this even if they routinely use keyboard navigation. Steve -- *From:* [EMAIL PROTECTED] [mailto:[EMAIL 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

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Ben Buchanan
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

2007-06-08 Thread Lea de Groot
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

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Matthew Pennell
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 from

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Matthew Pennell
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

2007-06-08 Thread Matthew Pennell
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:

RE: [WSG] WCAG Samurai Errata

2007-06-08 Thread Frank Palinkas
: 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 technology. */ When

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Kane Tapping
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 writing

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Lea de Groot
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

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Lea de Groot
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 get a

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Matthew Pennell
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 is

RE: [WSG] WCAG Samurai Errata

2007-06-08 Thread Jason Turnbull
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

2007-06-08 Thread Matthew Pennell
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

2007-06-08 Thread Frank Palinkas
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 characters, or whatever. Frank Palinkas wrote

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Matthew Pennell
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 and

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Stuart Foulstone
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

2007-06-08 Thread Matthew Pennell
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 the

RE: [WSG] WCAG Samurai Errata

2007-06-08 Thread michael.brockington
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 content' on

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Matthew Pennell
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

2007-06-08 Thread Thierry Koblentz
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, the

Re: [WSG] WCAG Samurai Errata

2007-06-08 Thread Al Sparber
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 blank and

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

2007-06-08 Thread Sander Aarts
Matthew Pennell schreef: On 08/06/07, *Lea de Groot* [EMAIL PROTECTED] mailto:[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

RE: [WSG] WCAG Samurai Errata

2007-06-07 Thread Frank Palinkas
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