- From: Charles McCathieNevile <charles@w3.org>
- Date: Sat, 29 Jun 2002 13:07:35 -0400 (EDT)
- To: David Poehlman <poehlman1@comcast.net>
- cc: Jon Hanna <jon@spin.ie>, wai-ig list <w3c-wai-ig@w3.org>
The point is that if I have difficulties reading, I cna concentrate on reading the content, and not the markup. (This is not just people who are identified as cognitively impaired. It really genuinely does apply to me, and to many people I know, and the lack of WYSIWYG authoring tools that can easily be used to produce accessible content is a genuine and significant problem in making the web more accessible. One of the big problems with the tools that do exist is that very few are designed for working with structured content - they produce visualy formatted contetn which has a structure implied in the presentation. Unfortunately, that structure is lost when someone uses a presentation that suits them. In the case of translating printed work to a different (fixed) print format this is hard to avoid, but in the case of the web it simply represents a failure to understand and use the medium. The good news is that the situation is improving. Cheers Charles On Sat, 29 Jun 2002, David Poehlman wrote: let's see, If I am cognatively impaired and need to use pictures, I don't think either are what I would call accessible but a case can be made that you can view images in fp. ----- Original Message ----- From: "Charles McCathieNevile" <charles@w3.org> To: "David Poehlman" <poehlman1@comcast.net> Cc: "Jon Hanna" <jon@spin.ie>; "wai-ig list" <w3c-wai-ig@w3.org> Sent: Saturday, June 29, 2002 8:01 AM Subject: Re: Accessible _content_ management I guess it is a trick question. Notepad might be more accessible to Dave Poehlman, and it is in fact more accessible to me as an editing tool. But then, that's because I happen to already know HTML, XML, CSS, WCAG, ATAG, SVG, 4TF, and many other acronyms important or otherwise. In fact, even then it depeds on the use case. If I am building a plain web page that includes a lot of text based content they are about even. If I am doing something that uses a lot of basic HTML features then frontpage (it saves me typing too many tags, and then fixing the, which is important because I have problems typing too much. etc. (Well, in my case the brand names are not important - I don't have a copy of either piece of software, but the arguments apply to the various tools I do use - chiefly Amaya, and occasionally any of a whole range of others. Cheers Chaals On Fri, 28 Jun 2002, David Poehlman wrote: notepad. Why? because I can use all of its functions or is this a trick question. ----- Original Message ----- From: "Jon Hanna" <jon@spin.ie> To: "wai-ig list" <w3c-wai-ig@w3.org> Sent: Friday, June 28, 2002 12:01 PM Subject: RE: Accessible _content_ management Thought for today: Which is more accessible; Notepad or FrontPage? -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +33 4 92 38 78 22 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France) -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +33 4 92 38 78 22 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Saturday, 29 June 2002 13:07:37 UTC