|
|||
Webnauts Net redesign would appreciate review
We have redesigned our web site, and will be very soon in German too, while we want to paticipate at the Biene Awards also.
Therefore, we would appreciate your feedback about the following: - XHTML 1.0 - CSS 2.0 - XML - P3P - Graphics - Accessibility - Usability - SEO - Readability - Credibility - OS, Browser and screen readers compatibility - Download time and everything else you might think of. Thanks a lot in advance! |
Sponsored Links |
|
||||
Zitat:
- you should use "back to top" links - your tab order is terrible, use tabindex You should have a glossary for <acronym>/<abbr>-tags, because the title is only visible, if you use a mouse. Persons who only use a keyboard or can't use a mouse don't see the title. Then, after make a print preview, i see that the <abbr>-tag is underlined on the page. You should remove this. Make a CSS file only for "media=print".
__________________
Personal stuff |
Sponsored Links |
|
|||
Thanks for the useful feedback. You are right that I have some tabbing problems.
Were would you add the tabindexes, in a way that I will not have any tabbing conflicts? About the other issues, I am having another closer look. |
|
|||
Tooltips
First your English is not bad at all.
So back to our topic: I already have titles for the abbreviations and acronyms. As for example: <abbr title="Search Engine Optimization">SEO</abbr> Would you suggest something like this? <abbr title="Search Engine Optimization"><span title="Search Engine Optimization">SEO</span></abbr>? I did not test that yet with screen readers, but I would ask here, won't the screen readers read the titles twice? If yes that would be a bad usability for blind users. And by the way, I do not want to use Java Script on our site, if that is the method you met for tooltips. |
|
||||
Zitat:
Zitat:
The problem probably comes from the lack of active/focus styling on my main navigation. There is no visual cue for keyboard users that those links are focused. I shall fix that though. So, I would definetelly not implement tabindex for such issues. I would possibly add somewehere another navigation link if necessary. Tabindex always produce diverse conflicts, which I must avoid. As a general rule of thumb we should not use tabindex unless we have a table based layout where the source order makes no sense. Zitat:
Zitat:
After all, keyboard navigation is very bad in a lot of mainstream user agents. Lynx and Opera are the only browsers I know of with decent keyboard navigation. It's probably a user agent problem. Or not? Therefore, can you tell me with which browser you had that tabbing problem? Thanks a lot again for your kind review and comments.
__________________
- Web Site Accessibility, SEO, & Usability Testing & Consulting - Human and Search Engine Friendly Web Directory Geändert von Webnauts (24.06.2006 um 00:43 Uhr) |
|
|||
I mean something like this:
Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en-US"> <head> <title>Tooltip</title> <style type="text/css" media="screen"> * { margin:0; padding:0; text-decoration:none; color:#000; cursor:default; } abbr { background-color:#efe; border-bottom: 1px dotted black; } a.tooltip abbr span { display:none; } a.tooltip:hover abbr span { display:block; position:relative; top:10px; left:10px; padding:5px; border:1px solid black; width:150px; background-color:#eee; } </style> </head> <body> <div><a class="tooltip" href="#"><abbr>HTML<span>Hypertext markup language</span></abbr></a></div> </body> </html> EDIT: it doesn´t work in IE 6 |
|
|||
Thanks for the idea.
But, the "href" attribute specifies an internal link that you may not want. An internal link name should usually follow the # character, but it doesn't in this case. Or what is met there? Don't forget semantic markup. So what's next? |
|
|||
Ok, it isn´t semantic, but it shows how it can be.
The <a> is for the IE, but if i code some EcmaScript, it can work with a simple <span>. Now i made a Script, but it doesn´t work in IE. Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en-US"> <head> <title>Tooltip</title> <style type="text/css" media="screen"> * { margin:0; padding:0; } span.tooltip span { display:none; position:relative; top:10px; left:10px; width:150px; border:1px solid black; } span.tooltip:hover span { display:block; } </style> <script type="text/javascript"> function makeTT() { aS = document.getElementsByTagName("span"); for (i = 0; i < aS.length; ++i) { cS = aS[i]; if(cS.getAttribute("class") == "tooltip") { aT = cS.getElementsByTagName("abbr")[0].getAttribute("title"); tS = document.createElement("span"); tSt = document.createTextNode(aT); tS.appendChild(tSt); cS.appendChild(tS); } } } </script> </head> <body onload="makeTT()"> <span class="tooltip"> <abbr title="Hypertext markup language">HTML</abbr> </span> </body> </html> and today or tomorrow i´m going to make a script that only needs the <abbr> Geändert von _42 (24.06.2006 um 01:41 Uhr) |
Sponsored Links |
|
|||
Thank you very much for your help, but I must repeat myself here, that we are against implementing Java Scripts on our web site.
And that we do not implement any techniques that are not cross-browser. |
Sponsored Links |
Themen-Optionen | |
Ansicht | |
|
|