Re: [WSG] Well since everybody... NOW WITH URL
Kim Kruse wrote: I know about the site breaking when font is increased. It's because of the tabmenu (which is btw is crossbrowser and css only... no javascripts) I removed a menu item and now I can use largest fontsize in IE and increase the textsize to what looks like 30px fontsize to me without the page breaks. Anyway... they'll all break at some point. Of course they will. I just thought they broke a little early. I don't know what a rule of thumb should be, but I think 200% font-resizing and 25px minimum font-size should look somewhat ok. Looks like your page is above that treshold now. I don't think I use any images to space out part of the pages. I use them because I think it looks good. They do look good, but once they're gone the page became somewhat harder to figure out. My browser (Opera 7.54) didn't render anything visible where those nav-images on top were. Made it a bit dificult to find them. Once found, the title-attribute lead me on, but title is not reliable on its own. I'm sorry to hear you find the tab menu confusing... in what way if I may ask? The thought behind them are as grouping... seemed logical to me. It's not your menu or the logic behind tabbing and the use of tabindex that's confusing... :) It's the way it works throughout browser-land. Gecko browsers are following the sequense in the source, or any order given by tabindex on elements, followed by the rest. IE/win is doing the same - it seems, but it depends on the layout-methods used in a page and what IE/win is focused on to begin with. My Opera doesn't tab on/between elements without tabindex, but _with_ tabindex it's working just as I like it. I may set tabindex in a chosen order on vital elements, to make sure tabbing is working - but the results are not always what I expect. I'm still not sure what the best strategy would be, or if I'm just confused on the subject. Wouldn't be the first time... ;) regards Georg ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Well since everybody... NOW WITH URL
OK... I'm glad to hear it's better now. I see what you mean with no imgs... not sure how to handle it though :o) Thanks a lot Kim Gunlaug Sørtun wrote: Kim Kruse wrote: I know about the site breaking when font is increased. It's because of the tabmenu (which is btw is crossbrowser and css only... no javascripts) I removed a menu item and now I can use largest fontsize in IE and increase the textsize to what looks like 30px fontsize to me without the page breaks. Anyway... they'll all break at some point. Of course they will. I just thought they broke a little early. I don't know what a rule of thumb should be, but I think 200% font-resizing and 25px minimum font-size should look somewhat ok. Looks like your page is above that treshold now. I don't think I use any images to space out part of the pages. I use them because I think it looks good. They do look good, but once they're gone the page became somewhat harder to figure out. My browser (Opera 7.54) didn't render anything visible where those nav-images on top were. Made it a bit dificult to find them. Once found, the title-attribute lead me on, but title is not reliable on its own. I'm sorry to hear you find the tab menu confusing... in what way if I may ask? The thought behind them are as grouping... seemed logical to me. It's not your menu or the logic behind tabbing and the use of tabindex that's confusing... :) It's the way it works throughout browser-land. Gecko browsers are following the sequense in the source, or any order given by tabindex on elements, followed by the rest. IE/win is doing the same - it seems, but it depends on the layout-methods used in a page and what IE/win is focused on to begin with. My Opera doesn't tab on/between elements without tabindex, but _with_ tabindex it's working just as I like it. I may set tabindex in a chosen order on vital elements, to make sure tabbing is working - but the results are not always what I expect. I'm still not sure what the best strategy would be, or if I'm just confused on the subject. Wouldn't be the first time... ;) regards Georg ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Well since everybody... NOW WITH URL
Sorry... http://www.mouseriders.dk/ Kim Bennie Shepherd wrote: Wonder where the site is located :o) On 11/4/2004 2:35:42 PM, [EMAIL PROTECTED] wrote: Hi, It seems today is check my page day so I wondered if you would like to check my page too. The products (produkter) is not done yet but the rest should work fine. I thought a lot about tab index. Is there any need for them... unless you want to direct tabbers a certain way round the pages? I'm also very unsure about the access keys. (I have one skip to content - accesskey=S) I read a lot about access keys and most of it was actually negative! What to do? If this is way OT I apologize and please disregard this post then. Kim ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Well since everybody... NOW WITH URL
Kim Kruse wrote:
Sorry... http://www.mouseriders.dk/ ...
It seems today is check my page day so I wondered if you would
like to check my page too. The products (produkter) is not done
yet but the rest should work fine.
Yes, it does - up to a point.
Looked at the actual content (since I can read it). It's quite clear
what the site is all about, and the navigation is easy to understand.
First impression is good.
Now to the points:
- You write under Hvorfor web standarder? that I can change font-size
without breaking the layout. Maybe true in some browser - but...
In Moz/FF it's breaking really bad after only a few steps of
font-resizing, and in Opera it breaks just as bad above 16px minimum
font size. I would see this as an accessibility-weakness.
I didn't look for the cause, but it should be fixable.
- The layout rely heavily on images to space out parts of the pages. It
works with images turned off, but I had a hard time figuring out the top
navigation. I would see this as another accessibility-weakness. Should
be easy to fix, I think.
- Long text-lines on wide screens are hard to read. Maybe an idea to
limit them? p {max-width: something?; }
I thought a lot about tab index. Is there any need for them...
unless you want to direct tabbers a certain way round the
pages?
Some browsers won't allow me to tab at all unless there are tabindex on
elements. There are other browsers that doesn't honor tabindex. Not sure
what the best strategy would be.
I'm also very unsure about the access keys. (I have one skip to
content - accesskey=S) I read a lot about access keys and most
of it was actually negative! What to do?
I like access-keys, but they create more problems than they solve, so I
wouldn't provide any.
Think it's only the number-keys that might be of some use - for some -
without creating conflicts with other software.
Lykke til
Georg
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
