W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2002

RE: Frontpage 2002

From: Robert Neff <robert.neff@uaccessit.com>
Date: Sat, 16 Mar 2002 09:37:31 -0600
To: <kathleen.anderson@po.state.ct.us>, <w3c-wai-ig@w3.org>
Message-ID: <000001c1cd00$8012bbd0$6500000a@uac1>
Hi Kathleen, you are up early this Saturday morning. Oops you are on
eastern time <smile>.

Interesting point and I will relook at that. The issues I am seeing are
how novice people set up and use frontpage to work for them, more
specifically the web components.  I can point uou to church sites that
allow lay people to drop documents into the folder and it gets posted.
Unfortunately these methods do not get rendered properly and fail
validation miserably.  These methods are allowed under frontpage. I
would think these things would be seemless.  These are the web sites
that are being highly used by a large cottage population.

I have another personal beef with frontpage.  On the box it states asp
is supported, however, in the preview the content for the active server
page includes are not rendered.  Unless someone know different, here is
the code for the include:

<!-- #include file="includes/L0/L0_masthead-2.asp" -->

I have to go to take another step to make see this by going to the web
server if you have XP or Windows 2000 Pro where it may not render
properly or ftp to the test server.

These may be issues for the authoring group so my apologies if I have
over stayed my welcome here. Plus I think its how the authoring tools
view the rendered code - not sure.

Would like to hear how other tools like macromedia and adobe handle
includes and special functionality.


Remember, Frontpage does provide great functionality if you use the
server  extensions and I really like this.  This is a great way for the
web to be used by more people at home and small businesses.  I do not
like the problems with rendered code or the lack of viewing.  So I am
being negative on a good product because it falls short in two areas -
otherwise it's a great tool for someone in a small business who cannot
afford all the development tools and THEIR constant upgrades and the
configuration management tools to manage file corrections.

-----Original Message-----
From: Kathleen Anderson [mailto:kathleen.anderson@po.state.ct.us] 
Sent: Saturday, March 16, 2002 8:31 AM
To: w3c-wai-ig@w3.org; robert.neff@uaccessit.com
Subject: Re: Frontpage 2002

Hi Robert:
We use the FrontPage Include Component on just about every page on this
site: http://www.cmac.state.ct.us/access/   and have no problem getting
it to validate against the HTML 4.01 transitional spec.

Kathleen




---------- Original Message ----------------------------------
From: "Robert Neff" <robert.neff@uaccessit.com>
Reply-To: <robert.neff@uaccessit.com>
Date:  Sat, 16 Mar 2002 07:27:55 -0600

>I have been assessing FrontPage 2002 in regards to accessibility and
>have found when its functionality such as the wbe components and
>FrontPage includes are used, the rendered code is not HTML compliant.
>
>Here is a web authoring tool that is a market leader and easily usable
>by mom and pop or small operations to build slick websites with great
>functionality.  I have run across many churches that use this and
>professional organizations because it works well in a shared
>environment.
>
>Unfortunately, the rendered code is not even closely complaint.
>
>Cheers, rob
>
>
>
Received on Saturday, 16 March 2002 10:38:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:01 GMT