Ramblings, meanderings, rants and discoveries.

Showing posts with label W3 compliance. Show all posts
Showing posts with label W3 compliance. Show all posts

Wednesday, May 25, 2011

Learning CSS

I was asked to assist in redoing a website and ensuring it was completely accessible. This meant learning CSS, something I have avoided for a while.  Friends who started doing CSS complained constantly. Then there is the fact that every time I went to look at the simplest technique, there was always an exception for I.E. (WHY does Microsoft do that?)

Well first let me say CSS is not difficult nor is it the bear that many lead me to believe. HOWEVER, many sites that purport to be pure CSS are not. They have .js or worse flash. They run  server side applications and even loud music and sound that cannot be turned off. Some have only 1 page and no variations on it for mobile or other media. Yes they are using a CSS but why bother?

However as usual there are some roses in the weeds for learning CSS and finding templates and examples in the wild as it were.  First is the obvious one W3 Schools the tutorial covers all of the basic concepts and commands and explains very well why CSS is a good idea.  Standards for accessibility are covered as well as techniques to make the site look better. But honestly, what you build in the tutorial, looks like a middle school or grade school site. Once you understand the techniques and commands, it is time to move on to see what you can do DO with it.

I learn by doing and observing so off I went to find blogs, templates and sites I could view to see how they did something. There are a LOT out there, so let me list the ones I found the most useful.

Veerle's Blog  This is the designer's old site, by all means check out the new one, too. But this has invaluable techniques for using Photoshop (or any graphic editor really) and basic information on CSS.

Free Website Templates - this site has a lot of templates of varying types, complexity and price.  Most techniques can be gleaned from studying the CSS of many of the templates. Not all are accessible, pure CSS or even free - but it well worth a look to see what people can do.

CSS Zen Garden  - This site is a perfect example of why to use CSS. All it is is the same page in several designs. The only difference is the CSS.

So, that should be enough to get anyone started. And my own design I hope you will see soon, I am down to tweaking and will post the links here when they are done.  From what I learned I managed to come up with 5 very different looking designs for the site. So if the vote is tied among the owners I can just change them in a few months and swap out the design without changing the content pages. And THAT is the beauty of it.

Friday, May 20, 2011

CSS, W3, and accessabilty

I have been working on redesigning a web site. It needs to be brought up to more modern standards.  It needs to be accessible and most of all it needs to impart the information that it is meant to in a way the users can find it. This should not be difficult. EXCEPT it is.

This is my first real venture into the world of CSS and accessibility, you see a large percentage of our users are visually impaired. Some are low vision, this means that the test must be in a font that is readable and contrast must be good. Some use speech clients that means alt text must be there, no server side java script and of course no music. Also table can be a pain as can frames.

But the definition of accessibility does not stop there. It includes people with slower or older browsers.  Odd browsers, text only browsers and hearing impaired. So basically to make a truly accessible page, it should not run flash or any of the fancy stuff. Which is no big deal, right? Yeah about that.

So I go off to gather some templates to look at and learn from. EXCEPT a year ago when something was marked as an accessible CSS it was.  Now a lot of it is marked so but uses .js server side to make the hover work properly. Use flash as a graphic display device or use jquery which is really just another form of .js to some speech clients.

I found a few with none of the above and started studying them. I loaded first in Opera 11.01 but Opera upgraded so loaded in 11.10 they load differently spans and alt text sometimes overlap other text, I get a lot of extra space on the left side. In Firefox, they display differently, in Chrome they look ok on the one version I have. In Internet Explorer the hover does not work quite right it is out of alignment.  So the solution of a year or so ago is no longer a solution. We must again test and build with conditions for every conceivable browser and instance.  When will they stop making the internet unaccessible through developing products that do not respond to the  most basic html?

Tuesday, November 27, 2007

Criticism is needed

For those of you who do not know in a previous life I was a professional writer/editor. Ok, perhaps it was this life, but it was long time ago. I have to say that while I was not working in a top publishing house, nor was I writing the Great American Novel, we were professionals. As such we always looked to improve our writing. The same was true when I began coding, we looked to others to assist us in writing more efficient code. Perhaps the entire program design was beautiful, but we always looked for ways to improve speed.

About ten years ago I noticed a slight change among new coders. When a suggestion was made for efficiency’s sake, they argued. I do not mean they said, hmm I’ll think about it and keep the code as it was – we all did that if we thought someone was wrong. Or maybe we would test it off on the side quietly . If the suggestion was a significant improvement the app changed, if not no more would be said. But each coder took pride in their work and strove to produce the best they could. I mean the new coders would argue the point as if the person making the suggestion had not actually reviewed the code. (Code reviews were mandatory by the way) “But I HAVE to use a nested IF instead of a CASE here.” And twenty minutes later they would walk off either having decided the coder with 15 years experience was out to get them, had antiquated views or did not know anything about the new world of code, leaving the senior coder scratching his or her head and returning to their project. But as a boss once told me a great coder is like a racehorse and some have a bit of an ego. We would shrug and continue.

I now see this attitude permeate every aspect of work. It seems no one can take criticism or even suggestions for improvement. It was a sad day when this became apparent in the writing community. Yes,I still keep my hand in. I always have. I am a member of several writers’ groups. I edit for a few sites. I have written online doco for a few. I am sad to say that it has finally become the case that writers no longer seek constructive criticism. Rather they seek to be stroked told how great their piece is and perhaps have a couple of grammatical errors pointed out. I have been in groups where if someone suggests that a paragraph is unclear to them the writer argues rather than asks for further input or for suggestions f how to make it clearer.

It has become the norm to ridicule the critique and its writer rather than thank the person for taking the time to go through the piece and offer suggestions. Nothing says you HAVE take them. One site on which I am an editor offers an award for top sites. We have certain criteria we must check and once that is done it becomes a matter of personal opinion. A petitioner for the award failed some of the base criteria, which includes things like: onsite links must terminate to a page with relevent content, HTML must pass W3 compliance, music must be by request, etc. I informed him his site was not ready for an in depth critique and moved on. The idea is not to critique the contents of the site until the mechanics are completed. Being the best of the best means all code works, the site looks good, is accessable to everyone and contributes uniquely in some way to the RPG community. The site designer/owner argued that the minimum requirements for consideration were unfair. He wanted the prize with out the work. When it was pointed out to him some was merely HTML choices for basic formatting (non W3 compliance) He replied he was not a coder, just a designer. I curbed my tongue and did not state, "Then when you are good enough to try for the award do so otherwise do not waste my time." Sorry but the point of the award is that it is the best of the best overall. If you are not capable of making the site so, do not whine. Go learn how to do it and try.

Which brings me back to the old days in writing. I functioned as both an editor and writer. None of us felt we were writing a great novel. We wrote user manuals for commercial and proprietary software packages and accompanying training materials. Her is how it would work. The author would write a guide. A first level (copy) editor would go through the guide looking for obvious errors in grammar and ensure it complied with the house style.and A tech editor would run through the guide step by step, check the veracity of the information and perhaps catch some errors the copy editor missed. The manuscript would be marked up and sent back to the writer to make changes. The writer would make them or not.

The editors would go over the new manuscript when it arrived, test and make further suggestions and send it back. The writer would do what he or she wanted and send it back. IF an editor noticed a common error they might mention it to the writer: watch tense, avoid to be, use active voice. That was all part of the editor’s job. If a paragraph or more really needed a rewrite it would be noted. The manuscript was sent back again to the editors after changes were made. It was in the best interest of the writer to make the suggested changes. Why? Because the editors had the manuscript last. Many were the times I rewrote a manual that was wrong technically, too long (there are page limits set), or was just poorly written. We called that a heavy edit. Yes, the author’s name went on the work. And we usually never re-contracted with that writer again. Why? Because there are a lot of writers out there who are willing and able to comply with a house style.

What saddens me is the lack of desire by writers to improve their craft. I give some of my worst writing to those groups of which I am a member to critique. Why? Because I know the good stuff is good. I can work with that. It is the parts I need help with that I present. The portions I KNOW are not working. I have received 0 critiques. Why? I request specifically for people to pull them apart. Grammar, I do not worry about too much that is what grammar checkers are for. But tense, tone, action, am I clear? Have I missed stating something does the dialog seem contrived? Does the action seem contrived? Is too much time spent on something? Not enough? Does the piece convey the feeling I want it to through the language used? If I am lucky I will be told “I got confused here who had what.” Most of the time I get, “it’s good, you have a typo here and that’s it now onto the next piece.”

I know I am not that good. Is it that I am such bad writer that they cannot say anything about it to improve it other than throw it out? Is it that they are afraid they will hurt my feelings? I suspect it is more that they are afraid I will argue and take up too much time or that they want to get to their pieces as soon as possible to hear exactly the same “It’s good, maybe change the tense here, now on to the next piece.” It is sad people have lost interest in improvement and rather hear praise than suggestions. But then that would be why so many computer applications are released with bugs. It takes less time money and energy to write a patch than to argue with a Prima Dona.

Wednesday, June 27, 2007

Test Almost Over

As some of you may or may not know I have been 'playing' with the site building tool for the ZEN site for RPGs. My evaluation is that it is OK. Now what does that mean? That means NOTHING made me say "wow that is neat!" but on the other hand nothing made me curse for hours at it either - well maybe one thing but I am getting used to that issue.

The Tool
Trellix SiteBuilder-

First I ran a generated page through the w3 compliance checker. It failed on 23 counts. All failures are Trellix generated code, not webgems as they call them for my html.

Line 1 column 0: no document type declaration; implying "!DOCTYPE HTML SYSTEM".
Warning Line 7 column 211: cannot generate system identifier for general entity "sUrl".
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 7 column 211: general entity "sUrl" not defined and no default entity.
Info Line 7 column 210: entity was defined here.
Warning Line 7 column 254: cannot generate system identifier for general entity "Command".
Error Line 7 column 254: general entity "Command" not defined and no default entity.
Error Line 7 column 261: reference to entity "Command" for which no system identifier could be generated.
Info Line 7 column 253: entity was defined here.
Warning Line 7 column 271: cannot generate system identifier for general entity "FileName".
Error Line 7 column 271: general entity "FileName" not defined and no default entity.
Error Line 7 column 279: reference to entity "FileName" for which no system identifier could be generated.
Info Line 7 column 270: entity was defined here.
Error Line 10 column 47: required attribute "TYPE" not specified.
Error Line 14 column 20: there is no attribute "LEFTMARGIN".
Error Line 14 column 34: there is no attribute "TOPMARGIN".
Error Line 14 column 50: there is no attribute "RIGHTMARGIN".
Error Line 14 column 66: there is no attribute "MARGINWIDTH".
Error Line 14 column 83: there is no attribute "MARGINHEIGHT".
Error Line 21 column 39: there is no attribute "BACKGROUND".
Error Line 71 column 62: there is no attribute "BACKGROUND".
Error Line 71 column 139: required attribute "TYPE" not specified.
Error Line 71 column 139: document type does not allow element "STYLE" here.
Error Line 118 column 112: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
Error Line 125 column 110: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
Error Line 139 column 112: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag.
Error Line 178 column 45: end tag for element "P" which is not open.
Error Line 205 column 154: required attribute "TYPE" not specified.
The W3C Validator Team


The document Failed W3 compliance.

Now that having been said, I IMMed a friend who uses JAWS 8 speech client and had them check the page. JAWs handled it fine, so the product does create code that is accessible.

The builder is very simplistic, it is designed to work ONLY with Netscape and I.E products. This of course cause a bit of cursing on my part, since I use Opera as my main browser. It would not allow me to start my site creations using Opera. However, I easily performed site maintenance and added additional pages using Opera.

The page file naming conventions leave much to be desired. They do not draw from the title nor do they prompt the user for a name upon creation. As a result they are named cryptically with such titles as ID1, ID2, etc.

The backgrounds supplied with the product are fairly boring in my opinion, but that is better than bad. A fair amount of editing is possible on the editable templates, from color to columns. It is easy to pick up and figure out.

I saw no archive or generation storage to allow for a rollback.

The manual and tool assume the user is not at all sophisticated and as such lacks information on advanced topics such as RSS feeds, frames, and tables. Although if you use the tool as is and are not trying to do anything too fancy, it functions well.

Overall I would recommend this tool for a small business who wishes to have a web presence or as a personal website builder. It could be used as a pure site maintenance tool or as a quickstart on a site. They did make changes over the period of the two weeks or so I used the tool, so the tool is trying to be improved. I will give it one or two more days of playing, then will rebuild as I wish. For the record, my styles tend to be a bit darker.