You're right about a client like that being a pain in the rear. I had a client who wanted customers to contact them via email, but didn't want to use a contact form and didn't want them to just use a link to email from the website. He was dead-set against forms even though they were the answer. He was so hard to work with, I eventually cut him loose. (Glad I got 50% of the cost up front! :o)
I imagine this "image-map" client was just after a certain look and had been told by someone that an image map was the answer and wasn't open to other solutions which are better and provide the same results. Rick > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Wednesday, August 27, 2008 9:45 AM > To: wsg@webstandardsgroup.org > Subject: RE: [WSG] Question about accessibility > > Hi Rick, > > If any client were to tell me how to code their website I would > probably tell them to go elsewhere. The client is more than likely > going to be a pain throughout the project and then also when making > payment. > > Obviously this is within reason - design aspects - of course they > decide. When it comes to the coding, the client most certainly does > not know best! If they want it to be of a high quality and well > optimised then I will make it using the best of my abilities. There's > no reason that they should specify how it is coded, unless they're a > developer and they need it formatted in a specific way. > > This must not be a normal customer anyway if they know about image > maps. I'm interested to know why they requested it in the first place.. > > Quoting Rick Faircloth <[EMAIL PROTECTED]>: > > > Darren... > > > > I find your comment, "I would most certainly not allow the use of > > an image map", interesting. > > > > What would you do, as is Jason's situation, if your "client demands it"? > > > > You can always turn down the work, but would you simply because a client > > wants to do something that you don't like? > > > > Rick > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of > >> [EMAIL PROTECTED] > >> Sent: Wednesday, August 27, 2008 7:39 AM > >> To: wsg@webstandardsgroup.org > >> Subject: Re: [WSG] Question about accessibility > >> > >> Hi Jason, > >> > >> I would most certainly not allow the use of an image map. They are > >> only useful for defining polygon or circular areas on maps (or > >> similar) as links. They are not good for a sites primary navigation. > >> > >> For navigation that is consisting of an image I would create an > >> unordered list: > >> > >> <ul id="nav"> > >> <li class="img1">link1</li> > >> <li class="img2">link1</li> > >> <li class="img3">link1</li> > >> </ul> > >> > >> Set the main img background on ul#nav to go behind all the links then > >> set the individual link graphics on each list item anchor - li.img? a > >> > >> Make the anchors display:block and you can then define height and > >> width of the link. > >> > >> Then when images are turned off you are still left with a fully > >> accessible menu. > >> > >> Darren Lovelock > >> Munkyonline.co.uk > >> > >> Quoting Jason Pruim <[EMAIL PROTECTED]>: > >> > >> > Good Morning everyone! > >> > > >> > I have a client that wants me to write his navigation mostly as a > >> > picture and then use image maps to get to the actual links. > >> > > >> > I am wondering, how would I go about convincing my client that this > >> > isn't the best way to do it? I personally think that some nice text > >> > links, styled properly with CSS would look just as good if not better > >> > then image maps. > >> > > >> > Oh, and to put it into context, it's a picture rating site so I don't > >> > know that Blind users are going to be too much of a concern for him > >> > since they can't see what the main part of the site is for. > >> > > >> > Any info I could get about this would be wonderful! > >> > > >> > Thanks everyone! > >> > > > > > > > > > > > ******************************************************************* > > 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] > ******************************************************************* > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.138 / Virus Database: 270.6.9/1637 - Release Date: 8/27/2008 > 7:01 AM ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
