Re: [WSG] Brand logos with links to home
I agree w/ Paul + alt/title tags Andrew 109B SE 4th Av Gainesville FL 32601 Cell: 352-870-6661 http://www.andrewmaben.com [EMAIL PROTECTED] In a well designed user interface, the user should not need instructions. On Mar 17, 2007, at 3:44 PM, Paul Novitski wrote: At 3/17/2007 07:27 AM, Lee Powell wrote: I was wondering what the general consensus was on whether the main logo on a site should always be a link back to the home page. Is this a general 'rule of thumb' or do many tend not to do this? We routinely link the logo to the home page, and we also include an explicit home page link in the navigation menu. The redundancy of having two home page links seems like a pedantic concern and much less onerous than either of the alternatives: having a linkless logo or omitting home from the nav menu, both of which can produce both client and user complaints. Regards, Paul __ Paul Novitski Juniper Webcraft Ltd. http://juniperwebcraft.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] Teaching CSS
Can I just mention, that if you can possibly find the time, then _do_ try and teach things to your colleague; nothing else is as good for ironing out any issues in your own knowledge as having someone else saying but why? This may sound daft, but trust me, it always works for me. Mike *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] site check - almost ready for prime time
The test site at http://www.fotografics.it/fife/ has been refurbished to make it more standards compliant, before moving on to the accessibility layer I would appreciate it if you guys could check it out for any errors or wrong practices Thanks, bob *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] centring and viewport size (OT?)
Thanks to those who responded on this. What I've done is to make a file
which uses the javascript to determine the space available in the
browser window, viz:
script type=text/javascript
var height = 0;
if( typeof( window.innerWidth ) == 'number' )
{
//Non-IE
height = window.innerHeight;
}
else if( document.documentElement (
document.documentElement.clientWidth ||
document.documentElement.clientHeight ) )
{
//IE 6+ in 'standards compliant mode'
height = document.documentElement.clientHeight;
}
else if( document.body ( document.body.clientWidth ||
document.body.clientHeight ) )
{
//IE 4 compatible
height = document.body.clientHeight;
}
if (height0)
{
window.location.href = index.php?height=+ height;
} else
exit();
/script
Of course, since the php is server-side, I then have to send the height
variable to the php via another page load (window.location.href).
This page then takes the height, knocks off the div height and divides
by 2 to get the correct margin-top, which it then writes to the inline
CSS in two sections:
?php
IF ($_GET['height']100)
{
$space=$_GET['height'];
$margin=($space-200)/2;
} ELSE
{
$margin=100;
}
?
?php
echodiv id=\viewport\ style=\margin : .$margin.px auto;\\n;
echo h1The top margin is set to .$margin.!/h1;
echo/div\n ;
?
I have also trapped it, so that anyone without javascript will get a
top-margin of 100px;
You can see all this at: http://www.rhh.myzen.co.uk/gam/sandbox/
It's a bit clumsy, and I don't like reloading a page, so I'm grateful
for any really good /suggestions / improvements!
Thanks.
http://www.rhh.myzen.co.uk/gam/sandbox/i
--
Bob
www.gwelanmor-internet.co.uk
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] site check - almost ready for prime time
Looks pretty strong. *Joseph R. B. Taylor* Sites by Joe, LLC /Custom Web Design Development/ Phone: (609) 335-3076 www.sitesbyjoe.com http://www.sitesbyjoe.com Bob Schwartz wrote: The test site at http://www.fotografics.it/fife/ has been refurbished to make it more standards compliant, before moving on to the accessibility layer I would appreciate it if you guys could check it out for any errors or wrong practices Thanks, bob *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** --No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.13/725 - Release Date: 3/17/2007 12:33 PM *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***begin:vcard fn:Joseph R. B. Taylor n:Taylor;Joseph org:Sites by Joe, LLC adr:;;408 Route 47 South;Cape May Court House;NJ;08210;USA email;internet:[EMAIL PROTECTED] tel;work:609-335-3076 tel;cell:609-335-3076 url:http://www.sitesbyjoe.com version:2.1 end:vcard
Re: [WSG] site check - almost ready for prime time
I would appreciate it if you guys could check it out for any errors or wrong practices Most/every page has two h1's, and there should only be one per page. Ideally, you should keep the h1 for the page title, but not for the site title. Your cites should probably not be in their own paragraphs if the cite can be styled directly. Other than that, looks great. Some may also say that having a splash screen page (a page with no other navigation other than enter) is a bad practice, but I think that's more a matter of personal preference. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] site check - almost ready for prime time
On 19 Mar 2007, at 14:42:38, Bob Schwartz wrote: The test site at http://www.fotografics.it/fife/ has been refurbished to make it more standards compliant, before moving on to the accessibility layer I would appreciate it if you guys could check it out for any errors or wrong practices One thing I notice is that the links in the navigation have title attributes which, when they appear as a tooltip, obscure the contents of the submenus and of the menu items further down the page (I've looked in Safari and Firefox, BTW). Of course, when you move off the link the tooltip vanishes, but it reminded me of something that one of the speakers (I believe it was Anne McMeekin of the Royal National Institute for the Blind) mentioned at the WSG London Accessibility meetup a couple of weeks ago: a partially-sighted user might well have a screen magnification of as much as 32 times normal (or more), and the appearance of a big yellow tooltip box obscuring the actual content is usually a major hindrance to them. In this case, such a user might not even notice that a submenu (which could be partially off the right of their screen) had appeared, nor would they be able to scan down the main menu until the tooltip finally disappeared. As no screenreaders read title attributes by default (and no screenreader user ever changes the default setting, apparently) you aren't really deriving any benefit (at least in accessibility terms) from the title attributes, so they might as well go. Generally though I think it looks extremely good :-) Cheers, Nick. (Apologies if I've misrepresented what was said at the WSG meetup, but I believe I've remembered it correctly :-) -- Nick Fitzsimons http://www.nickfitz.co.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] centring and viewport size (OT?)
On Mon, 19 Mar 2007 14:43:58 +, Designer wrote: Thanks to those who responded on this. What I've done is to make a file which uses the javascript to determine the space available in the browser window, viz: [...] (code snipped) Of course, since the php is server-side, I then have to send the height variable to the php via another page load (window.location.href). This page then takes the height, knocks off the div height and divides by 2 to get the correct margin-top, which it then writes to the inline CSS in two sections: [...] (more code) You can see all this at: http://www.rhh.myzen.co.uk/gam/sandbox/ It's a bit clumsy, and I don't like reloading a page, so I'm grateful for any really good /suggestions / improvements! Use JavaScript to change the element's top-margin style directly, perhaps? Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] centring and viewport size (OT?)
On Mon, 19 Mar 2007 14:43:58 +, Designer wrote: Thanks to those who responded on this. What I've done is to make a file which uses the javascript to determine the space available in the browser window, viz: [...] (code snipped) Of course, since the php is server-side, I then have to send the height variable to the php via another page load (window.location.href). This page then takes the height, knocks off the div height and divides by 2 to get the correct margin-top, which it then writes to the inline CSS in two sections: [...] (more code) You can see all this at: http://www.rhh.myzen.co.uk/gam/sandbox/ It's a bit clumsy, and I don't like reloading a page, so I'm grateful for any really good /suggestions / improvements! Use JavaScript to change the element's top-margin style directly, perhaps? Cordially, David -- *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] site check - almost ready for prime time
On 3/19/07, Kenny Graham [EMAIL PROTECTED] wrote: Some may also say that having a splash screen page (a page with no other navigation other than enter) is a bad practice, but I think that's more a matter of personal preference. Personally, I'd have links to the major sections of the site, rather that one small insignificant link at the bottom of the page. A screen-reader user would have to trawl through the whole screen before they could get into the meat of the site, which doesn't seem ideal. On a non-accessibility tip, the header graphic appears to have quite significant JPEG artifacts on my screen (they show up more on the Macbook for some reason). Also, the sub-menus on the left-hand navigation appear, then grow slightly in size (in both Safari and Camino on MacOSX). I'm not sure if that's intentional or not, but it's a bit distracting. Cheers, -- Olly Hodgson http://thinkdrastic.net/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Teaching CSS - THANK YOU!
Just a short note of thanks to all for weighing in on my question about teaching CSS. I've taken all suggestions and book recommendations on board which I'm sure will assist the needs of this challenge! Best regards to all! Cole *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] site check - almost ready for prime time
Hi, From an WAI accessibility point of view: Your menu has links with the same anchor text but different destinations - introduction, current and members. When you can see the menu structure the context is obvious but when using a screen reader this can be confusing. You should also perhaps markup your logo H1 content as a change from the declared natural language of the page (English). Stuart On Mon, March 19, 2007 2:42 pm, Bob Schwartz wrote: The test site at http://www.fotografics.it/fife/ has been refurbished to make it more standards compliant, before moving on to the accessibility layer I would appreciate it if you guys could check it out for any errors or wrong practices Thanks, bob -- Stuart Foulstone. http://www.bigeasyweb.co.uk BigEasy Web Design 69 Flockton Court Rockingham Street Sheffield S1 4EB Tel. 07751 413451 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] site check - almost ready for prime time
On Mon, 19 Mar 2007, Bob Schwartz wrote: The test site at http://www.fotografics.it/fife/ has been refurbished to make it more standards compliant, before moving on to the accessibility layer I would appreciate it if you guys could check it out for any errors or wrong practices Bob, The navigation is dependent on javascript for the flyouts which not only do the flyouts cease to work when js is turned off they also become dead links leaving only a partial working menu. This would be very confusing for a screen reader user. -- Regards, | Lions District 201 Q3 Rob Unsworth | IT Internet Chairman Ipswich, Australia| http://www.lionsq3.asn.au - *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] site check - almost ready for prime time
Bob Schwartz wrote: The test site at http://www.fotografics.it/fife/ has been refurbished [...] I would appreciate it if you guys could check it out for any errors or wrong practices It looks like the site may have problems displaying at widths of less than 1000px in Opera 9 and Firefox. The backgrounds don't stay within the three columns properly, leaving some text unreadable. Probably an issue with div positioning, and the box model since the problem doesn't seem to show up in IE -- which is what you presumably used to test the positioning. Phil. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] site check - almost ready for prime time
Bob - I was wondering about the width of the #wrappers- 980px/960px which causes horizontal scrolling if viewed on a smaller screen resolution such as 800 x 600. I have always tried to avoid horizontal scolling sometimes with great difficulty - does it not matter so much now that many people are using higher screen resolutions? Lyn Western Web Design www.westernwebdesign.com.au The test site at http://www.fotografics.it/fife/ has been refurbished to make it more standards compliant, before moving on to the accessibility layer I would appreciate it if you guys could check it out for any errors or wrong practices *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
