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] Print style sheets

On 6/7/07, Lucien Stals <[EMAIL PROTECTED]> wrote: Hi all, I'd written a print style sheet for a site I'd done ( http://www.swin.edu.au/ads/ltshowcase/inspire/presentations.html ), but the feedback I got was that nobody knew it was there (unless they printed the page). So I hit google for so

[WSG] Paul Chandley/HeadOffice/DHS is out of the office.

I will be out of the office starting 09/06/2007 and will not return until 13/06/2007. I will respond to your message when I return. For RRHACS web publishing requests, please contact the Web Services Team - (9096 2879, [EMAIL PROTECTED]).

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,

[WSG] Out of Office AutoReply: digest for wsg@webstandardsgroup.org

Hello, Thank you for emailing me. I am currently out of the office on a team building activity and will return on Tuesday, June 12th. Please note that emails sent to my mail box will not be actioned until this date. If you require urgent assistance or action, please contact me on 040 442

Re: [WSG] Use of PDFs - Accessibility issues

[EMAIL PROTECTED] wrote on 06/07/2007 08:04:01 AM: > Anyway, to get to the point, the customer has now been advised by a > marketing agency that the site should be reduced in size to approx 45 > key pages, and that the majority of content for things such as > conference room specification and r

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] layout/font site test - please

On 2007/06/05 19:15 (GMT+0100) Designer apparently typed: > To me, the zoom feature of IE7 (or firefox, or Opera) means that you > can resize a page constructed in pixels without hurting anyone. Doesn't it? Those with narrow windows will inevitably get a horizontal scroll as a result of IE7 p

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

[WSG] JAWS Screen Reader Demo - Monday 25 June 2007

We are doing another free JAWS screen reader demo on the afternoon of Monday 25 June 2007. A couple of the places are already booked but there are still six left. We limit the demo to 8 people so book early. The demo starts at 1:30pm and a free light buffet is available from 12:30 for those who wa

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] Use of PDFs - Accessibility issues

I thing PDF may be delivery as a complement for save the doc to our computer. And should not be the single format for a web document, only if theres no other better way to display it. I thing there is no format to the web more complaint than a html web page. I like PDF when i want to save the d

Re: [WSG] Use of PDFs - Accessibility issues

Many thanks to everyone for posts and personal replies on this thread. I appreciate you all taking the time to respond. The opinions that most people have kindly put forward are very similar to my own, but I guess that I wanted to make sure that I wasn't about to give an inappropriate 'knee-je

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] Use of PDFs - Accessibility issues

On Jun 7, 2007, at 6:16 PM, Nick Gleitzman wrote: Nick Roper wrote: Just to confirm, the recommendation from the agency is to replace existing html content with PDF version, not to provide PDFs as an additional alternative. Nick, you've made it fairly clear that your question is about

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] Print style sheets

Generally speaking, my advice would be to use print styles as part of the main stylesheet setup (possibly but not necessarily a separate CSS file) By tying your print-friendly styles to a script of any kind, you are forcing the user to find that link and be able to use it, in order to gain the bene

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

Thanks Jason, That's what I'm looking for. Also, I think Gez Lemon's comment about letting a user set their own access keys makes a lot of sense to me. Kind regards, Frank -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Turnbull Sent: Friday, 08 J

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] Use of PDFs - Accessibility issues

Hi, Have you tried RiverDocs: http://www.riverdocs.com/index.htm. You can sign up for a free evaluation licence for 14 days (no restrictions): http://www.riverdocs.com/product/download/index.html. The price is £399. If you are a member of GAWDS the cost is £299 until 22 June. Regards, Elaine W

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

Hi Matthew, Thanks for your comments. /* So what would happen on a page with 15 links above the form? Presumably a keyboard user would tab through the first 10, then just down to the form, through that, and then back to the last 5, then move onto any links after the form. Not exactly expect

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