Hi, Does the ability for the user of a screenreader to customise "at leasst partially resolve the problem" or should we design for the default screenreader (which would mean Jaws presumably, since it seemms to be the most commonly used)?
If we then design to this "standard", we should then at least have a starting point for further constructive criticism. On Fri, May 25, 2007 5:54 pm, Steve Green wrote: > Certainly JAWS reads the content of the <legend> element before each > <label> > element as described previously, and I agree about keeping the legend > short. > My understanding is that other 'professional' screen readers also do, > although some of the free ones may not since they typically have greatly > reduced functionality. > > I would also agree with the statement that most users never change from > the > default settings. Whilst the ability to customise settings may appear to > be > a good idea, it causes difficulties when the user works on a different > machine that has the default settings or different customisation. I > understand that Freedom Scientific are working on a means of making the > customisation portable, which will at least partially resolve that > problem. > > Steve > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Nick Fitzsimons > Sent: 25 May 2007 14:01 > To: wsg@webstandardsgroup.org > Subject: Re: [WSG] screen readers & repeated legends (was "dl v table for > form layout") > > On 25 May 2007, at 01:08:49, Rebecca Cox wrote: > >> On 5/23/07, Nick Fitzsimons <[EMAIL PROTECTED]> wrote: >> >>> As an aside, note that screen readers will read the legend of a >>> fieldset before the label of every element in the fieldset, so >>> legends should be kept short and sweet >> This is interesting, just wondered if you had any other info about >> this, which screen readers in particular and how customisable is this >> behaviour to a user (eg is there an option to disable the repetition >> of this info). >> >> Cheers >> Rebecca > > Hi, > > I got this from Ann McMeekin's presentation "Accessibility: what not to > do" > at the WSG London meetup back in February <http:// > muffinresearch.co.uk/wsg/280207.php>. There's a podcast available at: > <http://muffinresearch.co.uk/wsg/audio/07/02/28/ann.mp3> > > I don't have an exhaustive knowledge of screen readers, but what I've > gathered from listening to those who do is that: > a) They tend to be highly configurable; > b) 99.9% of users never change from the default settings. > > Maybe somebody with more experience in this area can chip in with more > detailed info? > > Cheers, > > Nick. > -- > Nick Fitzsimons > http://www.nickfitz.co.uk/ > > > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > -- Stuart Foulstone. http://www.bigeasyweb.co.uk BigEasy Web Design 69 Flockton Court Rockingham Street Sheffield S1 4EB Tel. 07751 413451 ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
