[WSG] directory structures
It's more to do with usability than accessibility, as it affects all users IMHO. But as a start, a logical directory structure is important, so long as it's logical to the user not the owner. Well, I agree and disagree. I think logical to the user not the owner is spot in for the website navigation. But the actual directory structure, where you put your content, you need to own that. And the #1 rule I aim for is that you don't want to change your directory structure (whereas you quite likely will want to adapt your website navigation). Because the directories will be reflected in the URL, you want it to be stable because you don't want the URLs to change. I'm not going to list all the reasons why here... this article by TBL on the topic is excellent. http://www.w3.org/Provider/Style/URI * The discussion list for http://webstandardsgroup.org/ *
[WSG] Re: px em pt ???
Why doesn't anyone push the barrow saying Font sizes should be LARGE by default, and designers should MAKE THE FONT SMALLER if/when they don't like it. Why do we aim to please designers and expect users to make the adjustments? I don't get it. But then, I skipped all the subjects on typography at uni! Hoping the average Joe will fiddle with their browser environment is way out of line, from a usability perspective. You want users to focus on their task and working in that domain - simple and direct feedback as they accomplish what they set out to achieve. Having to stop and figure out computer stuff (yet again) is distracting at least, confusing and frustrating for many. Ah but reality never quite reaches Utopia does it? :) But I'm heartened to see that CSS3 looks to include more font keywords. CSS2 gave us menu, icon, caption, etc. These use the fonts (sizes and styles) as specified in the desktop settings of the computer. You would hope, at least, that the user has their computer configured to their personal preference. (Sorry... doesn't help with the netcafe scenario, does it). Does make you wonder why IE (in particular) doesn't pick up any of the desktop settings for use as a default font size. Why is that? I was disappointed CSS2 never had a font keyword for standard window text. Perhaps CSS3 will help us finally put the font issue to rest - or at least down a very deep pit where I don't have to listen to it anymore. Sorry but I've copped almost a years worth of discussion on this at work, directly and indirectly. Fonts. Grrr. Perhaps it's time to render all text as images once more! *ducks* * The discussion list for http://webstandardsgroup.org/ *
[WSG] :hover accessibility
does anyone else feel that :hover is a little too enticing and likely to lead to some accessibility issues? depends on what you're using it for of course, rollover images is a non-issue, but for things like rollover menus, where's the keyboard support? just a random thought. * The discussion list for http://webstandardsgroup.org/ * * The discussion list for http://webstandardsgroup.org/ *
[WSG] Re: relative positioning of nested lists
The extra linebreak vanishes if you specify padding-bottom or border-bottom. I've opted for border-bottom. It's not ideal but it works. http://inspire.server101.com/bttdb/mb/ Anyone see any other problems? Russ, I tried stripping out all the whitespace with no success. Worth a shot tho! * The discussion list for http://webstandardsgroup.org/ *
[WSG] relative positioning of nested lists
Anyone have any thoughts on why IE6 keeps shoving in a linebreak in this example? http://inspire.server101.com/bttdb/mb/ It appears to put the line break in at each point where there is a nested list (UL) being repositioned. thanks Ben * The discussion list for http://webstandardsgroup.org/ *
[WSG] Targeting IE5
I would have thought the best way to target a browser (be it IE5 or other) was content negotiation. Detect the browser and serve content in the appropriate format. Does anyone else get the feeling this technique is rarely used whilst cruder methods proliferate? IMHO, web servers can do a lot more than just serve files and should be exploited for all they are worth - and that's plenty. I feel this cornerstone of the web is oft overlooked, much to the detriment of the online experience when cruder technologies are called on to compensate. Maybe it's just too difficult for developers to get access to webserver configuration, or too tedious to produce content in multiple formats? Gotta weight that against the time and effort we've all invested in workarounds and hacks though ... The right tool for the job. One can't solve every problem with a hammer. cheers Ben * The discussion list for http://webstandardsgroup.org/ *
