- From: Alan Chuter <achuter@technosite.es>
- Date: Thu, 29 Nov 2007 12:36:04 +0100
- To: "MWI BPWG Public" <public-bpwg@w3.org>
[CHARACTER_ENCODING_SUPPORT] > If the content encoding is not supported by the browser the text could > be renderer with rubbish (it depends on the language) making it harder > to understand. If a user has a reading disability then garbled text would be more of a problem, but is that really a sufficient benefit to motivate including it in this document? All users will have difficulty reading garbled text. We are saying "If your content is WCAG compliant, you may be sufficiently concerned to implement this BP on accessibility grounds." Maybe we can discuss this on the call today. Alan On 28/11/2007, Charles McCathieNevile <chaals@opera.com> wrote: > > On Wed, 28 Nov 2007 12:49:07 +0100, Miguel Garcia > <miguel.garcia@fundacionctic.org> wrote: > > > [SCROLLING] > > Limit scrolling to one direction particularly in the vertical axis, will > > also help people with cognitive limitations as some won't notice or will > > be disoriented by the horizontal scroll. > > > > [CHARACTER_ENCODING_SUPPORT] > > If the content encoding is not supported by the browser the text could > > be renderer with rubbish (it depends on the language) making it harder > > to understand. > > I agree with both of these statements. > > cheers > > Chaals > > -- > Charles McCathieNevile Opera Software, Standards Group > je parle français -- hablo español -- jeg lærer norsk > http://my.opera.com/chaals Try the Kestrel - Opera 9.5 alpha > > > -- Email: achuter@technosite.es Blogs http://www.blogger.com/profile/09119760634682340619
Received on Thursday, 29 November 2007 11:36:18 UTC