Is this template accessible and usable?

Webnauts · #1 (**permalink**) 10-22-2003, 12:24 PM

Hi Accessibility Advocates and Friends.

I am redesigning my web site, and I am trying to reach the maximum accessibility and Usability possible.

I created a template here: http://www.webnauts.net/css_final/index.shtml

The links and content are not ready yet and accessibility and privacy statement links are still missing.

Can you please have a look and give me suggestions, ideas or so ever?

By the way, I would appreciate if you would vote, and if you answer "Somewhat" or "No", please post your opinion.

Thanks

apisdesign · #2 (**permalink**) 10-25-2003, 12:49 PM

Very usable and very accessible. Great job!

I do not understand the wording of the link 'We for You' in the left hand navigation area. Should it read 'We are for you' or 'We're for you' or something like that?

Nice use of the access keys and good use of the 'title' attribute in your links. Your main logo still needs some alt text, though.

Also, your section 'Layout without tables' you state, and I quote: "We do use tables for layout purposes." I think you are missing the word "not" between 'do' and 'use'.

Also, strictly speaking, your <TITLE> tag should come immediately after your <HEAD> tag. Most HTML editors put it just before the </HEAD> tag - not sure why.

Again, great job!

Webnauts · #3 (**permalink**) 10-25-2003, 07:20 PM

Apisdesign thanks for you kind suggestions and comments.

1. We for You! You are right. it does not make sence.
I mean "what we can do for you." But I am trying to igure out how to get that shorter.

2. My main logo does not need more than the name of my company "Webnauts Net". I know I can profit by SEO if I make a longer description with possible keywords "as accessibility, usability" and so on, but then I will have a bad usability for blind users. If they use a browser speaker as i.e JAWS, they must hear that description at every next page they visit within my web site.

I know I could avoid that, if I have placed the skip navigation before the logo. But the next blind user usability problem. When the user goes to the next page, he must wait until the logo is read, to be sure that he/she is still on my web site.

3. About the mistakes in my content, no need to worry. I am not done yet. Thanks though.

4. About placing the <TITLE> tag immediately after the <HEAD> tag is no obligation or standard. It must only be between the headers of the document.

I just have seen that on a successful in SEO web site, and I thought it might make sence. If not, for sure it does not hurt at all.

I would be glad your further comments/suggestions.

weegillis · #4 (**permalink**) 10-29-2003, 09:02 PM

Had to vote, "don't know." No expertise in this field. Did find the template very informative, though.

This is just the example I needed to help with implemetation of accessibilty features in my own XHTML 1.0 tableless design.

I'm impressed with the flow of tableless, stylesheet supported web page design, and have only to bridge the gap of understanding that exists around accessibility.

I'd like to watch where you go with this. Thanks for putting it up.

Webnauts · #5 (**permalink**) 11-01-2003, 10:09 AM

Would you have a look at again please?
My template is updated:

http://www.webnauts.net/css_final/index.shtml

Thanks

weegillis · #6 (**permalink**) 11-02-2003, 08:02 PM

One of my questions (see 'when is enough, enough?)would appear to be answered by your example, that of the tabindex.

Ever think of creating a point-by-point tutorial for non-professionals working on community and organization web sites? We could sure use your help! There is not a lot of expertise out here in the boonies.

Webnauts · #7 (**permalink**) 11-03-2003, 03:02 AM

Hey weegillis!

Thanks for your kind comments. Be sure though that there is still some work to be done on my page. I am not satisfied when all accessibility validators/evaluators/lints as Bobby, WAVE, CynthiaSays, Watchfire, A-Prompt, CSE and others tell me that my page is accessible.
And that, while the check only the code.

I rely mainly on tests by users with all kind of disabilities and manual code QA.

That is why I need a bit more time, until I am 100% satisfied.

Therefore, stay tuned.