W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2000

a FrontPage FAQ

From: Al Gilman <asgilman@iamdigex.net>
Date: Mon, 31 Jul 2000 17:17:42 -0400
Message-Id: <200007312114.RAA2330187@smtp1.mail.iamworld.net>
To: w3c-wai-eo@w3.org
>Resent-Date: Mon, 31 Jul 2000 15:43:50 -0400 (EDT)
>Reply-To: "Kathleen Anderson" <kathleen.anderson@po.state.ct.us>
>From: "Kathleen Anderson" <kathleen.anderson@po.state.ct.us>
>To: "Dave  J Woolley" <DJW@bts.co.uk>, <w3c-wai-ig@w3c.org>
>Date: Mon, 31 Jul 2000 15:43:13 -0400
>Organization: State Comptroller's Office
>X-Mailer: Microsoft Outlook Express 5.00.2314.1300
>Subject: Re: Front Page again
>Resent-From: w3c-wai-ig@w3.org
>X-Mailing-List: <w3c-wai-ig@w3.org> archive/latest/6307
>X-Loop: w3c-wai-ig@w3.org
>Sender: w3c-wai-ig-request@w3.org
>Resent-Sender: w3c-wai-ig-request@w3.org
>
>One of the ways you can 'fix' pages created by FrontPage is to modify the
>template used to create all your new pages, and add the DOCTYPE to the
>template.
>Please see:  http://www.spiderwebwoman.com/tutorials/doctypesolution.asp
>
>Kathleen Anderson, Webmaster
>State of Connecticut, Office of the State Comptroller
>55 Elm Street, Room 101, Hartford, Connecticut  06106
>voice: (860) 702-3355  fax: (860) 702-3634
>email: kathleen.anderson@po.state.ct.us
>URL: http://www.osc.state.ct.us
>CMAC Access: http://www.cmac.state.ct.us/access
>AWARE: http://aware.hwg.org/
>
>
>
>
>----- Original Message -----
>From: Dave J Woolley <DJW@bts.co.uk>
>To: <w3c-wai-ig@w3c.org>
>Sent: Monday, July 31, 2000 3:28 PM
>Subject: RE: Front Page again
>
>
>> > From: Michael W Baker [SMTP:bakerm@zin-tech.com]
>> >
>> > I am developing accessibility standards for my company. We do government
>> > sub contracting and a lot of government sites use Front Page for design.
>I
>> > need to explore accessibility solutions (or have definitive reasons why
>it
>> > can't be done)for this product.
>> > Are there ways of designing accessibly with Front Page?
>> [DJW:]
>> I'm pretty sure that if you know how to write HTML
>> you can write good HTML in Front Page.  The problem
>> is that the user interface encourages bad habits, and
>> it seems that it is fairly easy to generate invalid
>> HTML as well.  Early versions generate a document type
>> that only permits HTML 2.0, which will need fixing for
>> most pages!
>>
>> The sorts of ways that it encourages problems are by
>> making presentational features easy to use, by putting
>> them on the tool bar, but hiding the proper structural
>> ones; I think that is consistent with the target WYSISWYG
>> market.
>>
>> Obviously it also encourages the use of canned formats,
>> automation etc.
>>
>> > Is it possible to fix a page designed on Front Page?
>> [DJW:]
>> Dave Raggett's Tidy program was designed to try to
>> create valid HTML from it.  Accessibility requires
>> human intervention though.
>>
>> > Are there any resources addressing this issue?
>> > (Personally I would never use this product, but I need to deal with a
>lot
>> > of Front Page sites and Front Page users.)
>> >
>> >
>> [DJW:]  There's actually an accessibility thread running
>> on the lynx-dev mailing list in which two different sites
>> (I think Ohio State is the problem one and a newspaper the
>> good one) are producing pages with a Front Page meta tag
>> (possibly hand retouched) and one is virtually unnavigable

>> text only, whereas the other is no problem.
>>
>> The fundamental problem is almost certainly that the people
>> who like using Front Page don't like to think about information
>> (as against specified browser graphic) design.
>>
>> --
>> --------------------------- DISCLAIMER ---------------------------------
>> Any views expressed in this message are those of the individual sender,
>> except where the sender specifically states them to be the views of BTS.
>>
>>
>>
> 
Received on Monday, 31 July 2000 17:10:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:47 UTC