- From: Loretta Guarino Reid <lguarino@adobe.com>
- Date: Sun, 26 Feb 2006 14:42:16 -0800
- To: "public-wcag-teamb@w3.org" <public-wcag-teamb@w3.org>
------ Forwarded Message > From: <Sofia.Celic@nils.org.au> > Date: Mon, 27 Feb 2006 09:32:37 +1100 > To: <lguarino@adobe.com> > Subject: Re: Plain text techniques: have your comments been addressed? > > > Hi Loretta, > >> Re: >> Technique: Using standard text formatting conventions for headings >> http://tinyurl.com/lhgxa >> Comments: >> http://www.w3.org/2002/09/wbs/35422/131techniques/results#xtexthead >> Headers can occur at the end of content if they are defining sections that >> happen to be empty. Does the additional explanation make this clearer? And >> the Text Email Newsletter Standard may also provide sufficient techniques >> for plain text documents; these lists are by no means exhaustive. > > I still don't believe a heading can be at the end of content. If the > section is empty then either the heading shouldn't be there or it should > contain a statement under the heading such as "This section does not apply > under these circumstances". It is poor usability to start with and many > users would believe the page didn't load properly. > > I don't believe the SC "how to meet" doc or this technique suggests there > are other plain text conventions for headings (or any other structure). > > > The other techniques look fine to me in regard to the comments I made in > the surveys. > > Thank you > Sofia > > ____________________________ > Dr Sofia Celic > Senior Web Accessibility Consultant > Vision Australia - Accessible Information Solutions > 454 Glenferrie Road > Kooyong, Victoria, 3144 > Ph: +61 (0)3 9864 9284 > Fax: +61 (0)3 9864 9370 > E-mail: Sofia.Celic@visionaustralia.org.au > www.visionaustralia.org.au > > Vision Australia was formed through the merger of > Royal Blind Society, the Royal Victorian Institute for the Blind, > Vision Australia Foundation and the National Information and Library > Service. > ABN: 67 108 391 831. ACN: 108 391 831 > > > > |---------+----------------------------> > | | Loretta Guarino | > | | Reid | > | | <lguarino@adobe.c| > | | om> | > | | | > | | 26/02/2006 08:13 | > | | AM | > | | | > |---------+----------------------------> >> ----------------------------------------------------------------------------- >> -------------------------------------------------| > | > | > | To: Sofia Celic <Sofia.Celic@nils.org.au> > | > | cc: > | > | Subject: Plain text techniques: have your comments been addressed? > | >> ----------------------------------------------------------------------------- >> -------------------------------------------------| > > > > > > Team B is trying to determine whether your comments have been properly > addressed for the following SC 1.3.1 techniques and failures. Could you > please let us know by noon EST pm on Tuesday, Feb 28? > > If you have trouble with the tinyurl links, you should also be able to get > to the technique from the survey item description. > > Thanks, Loretta > > > Technique: Using standard text formatting conventions for paragraphs > http://tinyurl.com/lhgxa > Comments: > http://www.w3.org/2002/09/wbs/35422/131techniques/results#xtextpara > > > Technique: Using standard text formatting conventions for headings > http://tinyurl.com/lhgxa > Comments: > http://www.w3.org/2002/09/wbs/35422/131techniques/results#xtexthead > Headers can occur at the end of content if they are defining sections that > happen to be empty. Does the additional explanation make this clearer? And > the Text Email Newsletter Standard may also provide sufficient techniques > for plain text documents; these lists are by no means exhaustive. > > Failure: Failure due to using white space characters to format tables in > plain text content > http://tinyurl.com/ovz5z > Comments: http://www.w3.org/2002/09/wbs/35422/gl13feb8/results#x131fail1 > > Technique: Failure due to using white space characters to create multiple > columns in plain text content > http://tinyurl.com/pd4k2 > Comments: http://www.w3.org/2002/09/wbs/35422/gl13feb8/results#x131fail2 > > > > > > ------ End of Forwarded Message
Received on Sunday, 26 February 2006 22:42:27 UTC