- From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
- Date: Thu, 18 Jan 2001 16:32:54 -0800
- To: Anne Pemberton <apembert@crosslink.net>
- Cc: Davey Leslie <davey@inx-jp.org>, "Charles F. Munat" <chas@munat.com>, "'Bailey, Bruce'" <Bruce_Bailey@ed.gov>, <w3c-wai-ig@w3.org>
At 04:06 PM 1/18/2001 , Anne Pemberton wrote: >At 10:26 PM 1/18/01 +0900, Davey Leslie wrote: > >What it looks like to me is that when folks haven't grasped the fundamental > >differences between a Word document and an html page, what usually comes out > >a WYSIWYG is far from useable on, say, text-browsers like Lynx. >I've made pages in Front Page that did just fine in lynx when I tested them >(a few years ago, when VA.PEN still supported lynx) ... What specifically >makes them unusable? Anne, it may be worthwhile to note here that he's saying "usually" -- which is true. It's certainly likely that someone who is careless can create WYWIWYG pages which don't make any sense in Lynx. I've had similar experiences myself with hand- coding pages in which tables, when "linearized", made little sense. Careless use of tables is one of the easiest mistakes to make with a WYSIWYG editor. That said, I do agree with you that in most cases there shouldn't necessarily be anything in the program which absolutely PREVENTS the creation of accessible web pages. Having played with FP a long time ago and not having a copy handy (I never install it when I install Office), I can't say for certain, but I don't believe that there are features which prevent an informed and careful user from making a workable web page. So I think you are both right. --Kynn -- Kynn Bartlett <kynn@idyllmtn.com> http://kynn.com/ Technical Developer Relations, Reef http://www.reef.com/ Chief Technologist, Idyll Mountain Internet http://idyllmtn.com/ Contributor, Special Ed. Using XHTML http://kynn.com/+seuxhtml Unofficial Section 508 Checklist http://kynn.com/+section508
Received on Thursday, 18 January 2001 19:36:30 UTC