Re: [WSG] Navs at bottom of pages
they can also be of great value to screen reader users, they read through the page and maybe want to have a look through the rest of your site. now you could provide a skip link at the bottom of each article to take them back to the main navigation OR you could provide the footer containing the main navigation so they don't have to clcik simple but i think rather nice and effective - Original Message - From: russ - maxdesign [EMAIL PROTECTED] To: Web Standards Group wsg@webstandardsgroup.org Sent: Friday, September 01, 2006 6:28 AM Subject: Re: [WSG] Navs at bottom of pages The use of broken pipes was mostly used (in my opinion, but then I'm an accessibility specialist ;) to address the Level AAA Checkpoint 10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. The better solution is to mark them up as a list of links (as they are still a list even if presented horizontally) and then use css to create the horizontal appearance (setting the li to display: inline is one method) and the illusion of pipes (applying a border ro one edge of the li or a elements). You could even add a structural label above them to give them meaning :) http://www.maxdesign.com.au/2006/01/17/about-structural-labels/ Russ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** ___ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] font standards today
Felix Miata wrote:
This is not a novel position I take. Our web standards organization
agrees with me. http://www.w3.org/QA/Tips/font-size
yes, but even they specify a font-family:
html, body, h2, h3, h4, div, p, ul, li, input {
font-family: Gill Sans, Trebuchet MS, Gill Sans MT, sans-serif;
}
Why is that?
because they didn't like the *look* of the defaults!!!
Commercial web development requires pragmatism not pedantry.
;o)
--
Join me: http://wiki.workalone.co.uk/
Thank me: http://www.amazon.co.uk/gp/registry/1VK42TQL7VD2F
Engage me: http://www.boldfish.co.uk/portfolio/
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Navs at bottom of pages
Kenny Graham wrote: I've noticed many people from this list stil put text-and-broken-pipe navs at the bottom of their pages. Is this still needed? I replicate link-relations as ordinary links in the page-footer, since there are so many browsers that can't make use of, or don't default to presenting, visible link-relations. A simple-styled short-list of basic navigation is a 'nice-to-have' thing IMO, so I'll probably keep adding them until all browsers present link-relations by default. Typical example found on... http://www.gunlaug.no/contents/molly_1_18.html ...and the rest of that site-section. Georg -- http://www.gunlaug.no *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] font standards today
[EMAIL PROTECTED] wrote:
Or was it because they have seen one of the readability studies on the
web, and decided that Sans-serif was better on-screen than Serif?
in which case
html, body, h2, h3, h4, div, p, ul, li, input {
font-family: sans-serif;
}
would have been adequate.
someone made a design decision about Gill Sans and Trebuchet MS being
better looking than just the users preference of sans-serif font.
;o)
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Navs at bottom of pages
Beautiful!! I´ve never seen link-relations working, it should really be a built-in spec for browsers... easy to get used to. A way to let anybody, in any site, know where they are standing. It should have also something like sitemap; Content plays that role? Regards; Eugenio. On 9/1/06, Gunlaug Sørtun [EMAIL PROTECTED] wrote: I replicate link-relations as ordinary links in the page-footer, since there are so many browsers that can't make use of, or don't default to presenting, visible link-relations. A simple-styled short-list of basic navigation is a 'nice-to-have' thing IMO, so I'll probably keep adding them until all browsers present link-relations by default. Typical example found on... http://www.gunlaug.no/contents/molly_1_18.html ...and the rest of that site-section. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] print style sheet - background problem
Designer wrote: Or, has anyone got any other brilliant ideas to solve this? How about adding/changing a border weight or style around that .event date cell or adding an overline-underline on the date number itself on the print style sheet so you don't have to rely on a color? This should circumvent the problem at hand while still providing something meaningful to the booked date for the person printing it out. Hope this helps. Sincerely, Mike Cherim http://green-beast.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] print style sheet - background problem
On Fri, Sep 01, 2006 at 06:35:37PM +0100, Designer wrote:
I have a one year calendar, where each day is a table cell. I have CSS
and php controlling the visual presentation of it. If a day is
'booked' it is assigned to be an event and shows up via a CSS class thus:
No such thing as a CSS class. HTML has classes, CSS has selectors
which can match HTML classes.
.event {
in other words, the day appears as a grey block. That's fine, but I
want to be able to print out the calendar, and (of course) if the user
has background printing turned off, nothing appears apart from the text.
My question, then, is can one check to see (DOM?) if the background is
#666; and if so, can the content be changed to 'n/a' (or something) in
the printout,
Well, you could do something like:
var cells = document.getElementsByTagName('td');
for (var i = 0; i cells.length; i++) {
if (cells[i].className != 'event') {
var text = n/a;
var textNode = document.createTextNode(text);
var span = document.createElement('span');
span.className = 'printOnly';
span.appendChild(textNode);
cells[i].appendChild(span);
}
}
but ...
so all users get a meaningful print?
Why isn't the lack of text content of the cells meaningful already? Or
is the sole indication that something is happening on a day the
stylesheet? (Hint optional presentation layers are not the ideal
place to put content).
--
David Dorward http://dorward.me.uk
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Navs at bottom of pages
TuteC wrote: Beautiful!! I´ve never seen link-relations working, it should really be a built-in spec for browsers... easy to get used to. A way to let anybody, in any site, know where they are standing. W3C seems to recommend them... http://www.w3.org/TR/relations.html http://www.w3.org/QA/Tips/use-links ...and have done so for a long time. You can turn on the 'navigation bar' in Opera - ToolsAppearanceToolbars... Mozilla support them too, and Firefox could get an extension last time I looked. IE doesn't support them, and I haven't tested in others. It should have also something like sitemap; Content plays that role? On my pages, yes. Some use 'index', but I find 'content' the most correct (and supported) term the way I have organized that section. regards Georg -- http://www.gunlaug.no *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] IE layout problems
wow, thanks kepler.i implemented your changes, and made a few of my own slight changes, and voila..!it seems to work perfectly now...although i did notice another thing now:in reference to tutec's referall to the fixed footer links, i was able to get it working, however, i am having trouble defining a certain amount of padding/margins at the bottom of the content,in order to prevent the footer from covering text when the browser window is too small.you can recreate this error by resizing the browser window small, and you can see it in IE. in FF, at least on this page, no content is covered, however it does get covered on some other pages.timOn 8/30/06, Kepler Gelotte [EMAIL PROTECTED] wrote:I think the margins on the #primary menu list was causing the list to wrap (just slightly) because of width:auto. To fix it make the changes below. ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] IE layout problems
beautiful :)i think i got it working now :Dthanks for all your help guystimOn 9/1/06, Tim Wong [EMAIL PROTECTED] wrote:although i did notice another thing now: in reference to tutec's referall to the fixed footer links, i was able to get it working, however, i am having trouble defining a certain amount of padding/margins at the bottom of the content,in order to prevent the footer from covering text when the browser window is too small. ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] Navs at bottom of pages
TuteC wrote: Beautiful!! I´ve never seen link-relations working, it should really be a built-in spec for browsers... easy to get used to. A way to let anybody, in any site, know where they are standing. Opera puts them to good use too... You can hold the left mouse button and click the right mouse button to take advantage of Next links instead of reaching for the navigation every time :) I think Opera is a bit tricky and might even bind that mouse shortcut to any (or perhaps only unique) Next link on a page as well. Still cool though! *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] print style sheet - background problem
On 9/2/06, Designer [EMAIL PROTECTED] wrote:
I have a one year calendar, where each day is a table cell. I have CSS
and php controlling the visual presentation of it. If a day is
'booked' it is assigned to be an event and shows up via a CSS class thus:
.event {
color: #666;
background-color: #666;
etc
}
in other words, the day appears as a grey block.
I'm assuming it is your PHP code adding the event class to your
table cells so you already know how the presentation should be
affected on the server-side of things... I think you should handle it
there rather than trying to fudge it with CSS or JS.
If you know which table cells should appear as a grey block on the
server-side then you can just print a nbsp; in the cells instead of a
number, so when it is printed only the unbooked days appear. Or if you
are really hung up on having a box appear when it is printed, insert
in img instead of the number.
You might also want to consider what happens when a lot of days are
booked. You would be printing out a page full of boxes with not many
numbers!
-- Justin
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
