gtwebdev.com

gary.turner
avatar
rank Moderator

Moderator


Posts: 5645
Joined: 2004-06-25
Location: Dallas

http://gtwebdev.com/

This site isn't quite ready for prime time, but it is at a crossroads. Of concern is the

  1. site architecture, is it constructed in a user friendly form;
  2. do the document architectures, including location and intuitiveness of menus, make each page easy to scan and use;
  3. is the vocabulary of the menus consistent and clear;
  4. are there any huh? moments when trying to find something.

Note that very little is done in the way of graphic design. I only gave my graphics consultant the site earlier this week, and don't expect a fast response, as she has a large print project going right now, and this is a freebie. Layouts are based on information issues and are only loosely a graphic concern. If you want to contribute graphic ideas, that's good, too.

Please comment on usability, accessibility and errors. Concerning the last, I think some of my demos may be broken. I was converting old demos to the new templates, and think I missed some conflicts in the css namespaces. You tend to do
that, when you work very late at night. I'll be checking them all, but a heads up wouldn't hurt.

cheers,

gary

A pianist who has learned the wrong system of fingering cannot become a virtuoso until he has laboriously taught himself the proper method.

My site is slo-o-owly being reconstructed; visit anyway.

Tyssen
Tyssen's picture
rank Moderator

Moderator


Posts: 6509
Joined: 2004-05-01
Location: Brisbane

In title headings,

  1. In title headings, conjunctions etc should be lowercase
  2. I always like a bit of margin between the last text and the bottom of the window
  3. I actually think less line-height on headings looks better otherwise they get too leaded out (especially at larger text sizes)
  4. When doing footnotes, it's good to link from the number to the footnote and back again.
  5. On the Team page, the first paragraphs after headings shouldn't be indented, but subsequent paragraphs can be (like you've done on the About Web Design page).
  6. From an accesibility point of view, if you're going to give a photo a caption, there's no need to give it the same alt attribute; otherwise the AT user is just hearing the same thing read out twice (or you read it twice if images are off).
  7. On the About Web Design page, I take it the items under the subheadings will eventually be links. Also, rather than saying section and sub-section contents, I'd say 'Name of the section contents'.
  8. On the workshop pages, the change from having a narrow left column with links to having a narrow right column with Recommended reading is a bit odd. On some of those pages, the content doesn't have enough margin or padding away from the outer edges, e.g.: http://gtwebdev.com/workshop/vcenter/vcenter-table.php
  9. On the pages where you have a skip link, it may be useful to give the user the option of skipping to content as well, e.g. you've chosen on a link, but after using the skip link, you still have another list of links to navigate before reading the content.

How to get help
Post a link. If you can't post a link, post ALL your code, both HTML & CSS. No server-side code; just the code sent to the browser.
Use tags.
My articles | CSS Reference

Tyssen
Tyssen's picture
rank Moderator

Moderator


Posts: 6509
Joined: 2004-05-01
Location: Brisbane

I think the spam flag is a

I think the spam flag is a bit too aggressive, as I had to fill in the captcha for the above post too. :/

How to get help
Post a link. If you can't post a link, post ALL your code, both HTML & CSS. No server-side code; just the code sent to the browser.
Use tags.
My articles | CSS Reference

gary.turner
gary.turner's picture
rank Moderator

Moderator


Posts: 5645
Joined: 2004-06-25
Location: Dallas

Tyssen wrote:1. In title

Tyssen wrote:
1. In title headings, conjunctions etc should be lowercase
I knew that, of course; I had Mrs Stokes for 7th grade English. Smiling I set header to capitalized in order to protect myself from the odd lowercased word (typo). I didn't notice but a couple of instances, is it pervasive enough to be annoying?

Quote:
2. I always like a bit of margin between the last text and the bottom of the window
Are you referring to the footer text?

Quote:
3. I actually think less line-height on headings looks better otherwise they get too leaded out (especially at larger text sizes)
I've set leading plus face to be a multiple of the base line-height. I've done this to maintain a rhythmic vertical motion. See Bringhurst, Elements of Typographic Style. It does seem over-leaded at times, but I think it's not as bad when there is something other than headings following headings. Look at some body text that contains sub-headers. Is it less obnoxious in those cases? Do you ever wish we could set top and bottom leadings separately?

Quote:
4. When doing footnotes, it's good to link from the number to the footnote and back again.
Good point. I'm not sure about the back link, though. From the reference to the footnote is unique. From the footnote to the reference is not necessarily unique, as there may be multiple refs to the same note.

Quote:
5. On the Team page, the first paragraphs after headings shouldn't be indented, but subsequent paragraphs can be (like you've done on the About Web Design page).
That bold tag line is a paragraph. So the indentation rules are the same for both pages. Should I add a <br /> after the tag to reset the indentation (and add top margin to the next paragraph)?

Quote:
6. From an accesibility point of view, if you're going to give a photo a caption, there's no need to give it the same alt attribute; otherwise the AT user is just hearing the same thing read out twice (or you read it twice if images are off).
Good point. Will remove the caption as redundant by context, and improve the alt text.

Quote:
7. On the About Web Design page, I take it the items under the subheadings will eventually be links. Also, rather than saying section and sub-section contents, I'd say 'Name of the section contents'.
Yeah, you're right. I've wrestled with this, and haven't yet been satisfied.

Quote:
8. On the workshop pages, the change from having a narrow left column with links to having a narrow right column with Recommended reading is a bit odd.
I'll tell you my thinking. There are three basic layouts:

The home, team (and c.v.s) and contact pages are single column and have only global navigation at the top, with maybe a bit of contextual links in the body, à la Diane's c.v. link on the team page.

There are section and sub-section pages that have tables of content. Besides being the expected location for local navigation, the toc is the most important part of those pages. The text is pretty much read once and go on. The toc is what is important, so is wider than common and on the left, where the eye goes first.

The workshop demos and the design articles have a sidebar for suggested reading. That is the least important part of the page, and is relegated to the least important location on the page. It is also the expected position for ads.

Then there are the demos that might have who-knows for layout, all dependent on the demo itself.

So, does going to a narrow right-side column, instead of the wider left-side column cause the problem, or is it that the Amazon ads are so strong? The latter causes me to wince.

Quote:
8a. On some of those pages, the content doesn't have enough margin or padding away from the outer edges, e.g.: http://gtwebdev.com/workshop/vcenter/vcenter-table.php
That's an artefact of outlining the demo for illustrative purposes.

Quote:
9. On the pages where you have a skip link, it may be useful to give the user the option of skipping to content as well, e.g. you've chosen on a link, but after using the skip link, you still have another list of links to navigate before reading the content.
Are you thinking about the global nav? The skip to links link takes you to the toc, which is the last in the source. Should I add another link to skip the global nav?

thanks,

gary

A pianist who has learned the wrong system of fingering cannot become a virtuoso until he has laboriously taught himself the proper method.

My site is slo-o-owly being reconstructed; visit anyway.

gary.turner
gary.turner's picture
rank Moderator

Moderator


Posts: 5645
Joined: 2004-06-25
Location: Dallas

About #3

About #3, margins are more the issue than line-height. Will have to find the appropriate selector combo to remove some top margins without breaking things elsewhere.

cheers,

gary

A pianist who has learned the wrong system of fingering cannot become a virtuoso until he has laboriously taught himself the proper method.

My site is slo-o-owly being reconstructed; visit anyway.

gary.turner
gary.turner's picture
rank Moderator

Moderator


Posts: 5645
Joined: 2004-06-25
Location: Dallas

1. fixed 3. got margins

1. fixed
3. got margins sorted
4. done ⇒, but not ⇐
6. done
7. settled on "Table of Contents"

cheers,

gary

A pianist who has learned the wrong system of fingering cannot become a virtuoso until he has laboriously taught himself the proper method.

My site is slo-o-owly being reconstructed; visit anyway.

ifohdesigns
ifohdesigns's picture
rank Enthusiast

Enthusiast


Posts: 273
Joined: 2008-02-22
Location: Providence, RI

Hey Gary, only a couple of

Hey Gary, only a couple of things:

1. The changing colors is a nice effect, but I would strongly advise having a "selected" state for the top nav. The hover you are using would work nicely.

2. In the footer, I like the functionality of being able to go back to the section heading, but maybe work on the wording a bit, for example:

"⇑ Up Return to section header page, Designing Web Sites."

"⇑ Up: To workshop"

Maybe have an "up to top" link, and a "return to: section" link

http://ifohdesigns.com - Web Design That Is Neat.
http://ifohdesigns.com/blog - Read it please.