The basic idea for this particular form is to generate code from a
html form.
I think you mean "for" rather than "from". At the page you mentioned,
http://websolutions.comli.com/formgenerator.php
a visitor can use a graphic user interface to create an HTML form and
see both the form (in some rendering) and the HTML code for it. As I
wrote, the idea as such is OK.
The first problem with using the page is that when the page is entered,
a large ad appears, apparently an ad of a "free" or "cheap" hosting
provider. This alone is sufficient to many people to go elsewhere.
You have rightly mentioned the colors are very vintage
and that is a flaw i am working on.
If you don't know which colors to use, use black on white - more
exactly, let them be defaulted. People who use a page to create an HTML
form should not expect an impressive visual experience but simply
something that works. However, for the element that shows generated
code, some distinctive background is probably good for usability. Make
it something light so that the contrast between text and color is
sufficient. And make the font size reasonable. A size of 10px is simply
too small even for code that will mostly just by copied and pasted - it
should still be *possible* to read it without zooming. The basic rule
for setting font size is "Don't".
Regarding usability, the basic
purpose is that people having limited knowledge of programming need
to create their own custom form and be able to send that to data
collection centres to fillout and submit it to main website for
further analysis and action.
The design of a form is just one part of that. You also need the
server-side form handler, and normally the form has to be designed
according to the requirements of the handler or together with it.
i have intentionally left the name and
method values blank for the form because they would be
programatically decided inside the feature for which i am planning to
use it.
Programmatically? How? The method=... and action=... attributes should
be selected by the designer of the form, to match the form handler. The
method=... attribute is optional, so there is little point in having
method="" in the generated code. And the name=... attribute in <form> is
outdated and never needed, though sometimes still used out of a habit.
The page is slow. And I mean slow. It sends an HTTP request when the
user adds a field to the form. Normally, generators like this work with
client-side JavaScript. Interaction with server might be used to save
the work on a server or to retrieve a saved work.
For usability, the buttons
(Tyhjennä) (Add Field) (New Form) (Cancel)
are just too much. There is too big a risk for clicking on a wrong
button, destroying the entered data. (Add field) should be enough.
Starting a new form should be placed elsewhere, and the other are not
needed.
As I mentioned, labels and controls should be associated using <label>
markup. This is a basic accessibility requirement