Re: [WSG] Form Widgets
Safari, Camino and Opera on Mac all apply form widgets differently. Safari is the most restricted, limiting font size to 12px on input type=submit If you want more control you can use button type=submit (not styled for Safari or Camino on Mac, but is for Opera on Mac), but you have to do some work for IE on PC If you want to compare what differences apply with Safari, Camino and Opera on Mac with input and button type=submit see slides 3 to 7 of http://nickcowie.com/presentation/s5-button.html -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Styling form elements in Safari
Tom You wrote: Am I correct in assuming there isn't a way to style an input of type submit in Safari to match what I've styled that shows in Firefox and Netscape? Input type submit is controlled by the Mac webkit, it effects Camino to, but not as much as Safari. Button type submit gives you much more control. See http://nickcowie.com/presentation/s5-button.html for more details. The downside with the the button element is you have to more work to get IE to play right. -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] 3 questions: flash, aimg and Ad Sense
Elle
Answer to 1.
Depends if you are viewing the page via Windows or OsX/*nix.
I expect you might be on OsX or *nix and flash does not work the same as on
Windows, put the logo in a iframe and that should fix it.
Nick
On 12/01/07, Elle Meredith [EMAIL PROTECTED] wrote:
Hey,
Just got 3 questions that are actually on 3 separate subjects:
1. I have a flash slide show in a page header and the page's logo is
positioned absolutely with higher z-index on top of the flash object
but only some of the logo is on top of the flash slideshow. Every
time a new image loads up in the flash movie, it hides part of the
logo. If you hover on the logo, it comes back up till the next image
loads.
Would you know why this happens?
2. Situation is:
I declare a general rule that says that all my links will have border-
bottom of some kind or background color when hovering on them.
Then I have an image that is also a link.
Even though I declare: a img {border-bottom: 0; background-color:
none;}, it doesn't have any effect and I still get a border-bottom or
can see background color on hover where I have padding around the image.
Why wouldn't it accept my second rule?
3. I recently added Google AdSense to my validated pages and it
caused errors on my page.
Is there anything I could do to still have pages that validate as
XHTML strict?
Much appreciated any help,
Elle
http://waznelle.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
--
Nick Cowie
http://nickcowie.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Images enlarging themselves
Lyn
You give the images a width:
ul#img li img {
display:block;
position:absolute;
bottom:0;
width: 100px;
}
So the browser automatically scales the image, ie if image was 80px high and
50px wide. The image becomes 160px high and 100px wide.
remove: width: 100px from ul#img li img and add it to ul#img li should fix
the problem
--
Nick Cowie
http://nickcowie.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Re: 3 questions: flash, aimg and Ad Sense
put the logo in a iframe and that should fix it. I thought iframe was deprecated in xhtml strict. I think it is too However, I think it is the only way to get flash to play fair, so looks like it will have to be html 4.01 strict or xhtml transitional -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] ainput//a - how wrong?
couple of points input:hover for type =submit (and others if my memory serves me) is pretty useless for Safari and limited for Camino, because you can only change a few properties on input. background-color, color and background-image are not affected by style (all to do with the form widgets built into Safari and Camino). You can use the button element instead of the input element if you want more control in these browsers. Why you use hover.htc instead of custom javascript for hover effects. 1 it saves you time 2 if you use in a number of places in your site, it saves users time, it only needs to be downloaded once 3 good browsers do not download it 4 if a good browser has js turned off effect still works 5 in really bad browsers (some versions of NS4) js can crash the browser, but these browsers ignore .htc files 6 of course .htc files do not work if js is turned off, they are js files for ie only. If you turn of js all javascript, .htc .js and inline stops working. 7 I have never had problems with hover.htc and IE5, 5.5 and 6 on windows. -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Does this hurt accessibility
Read http://lorelle.wordpress.com/2006/12/29/wordpresscom-please-stop-using-snap-preview/ Lorelle gives couple of examples of how it impacts on low vision users. -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Firefox and flash -missing border
Bruce It looks exactly the same for me in FF2 and IE6 on W2k. Is you problem with FF on a Mac or *nix box? because their flashplayer works differently. -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] CSS resources for Graphic designers?
It is all dependant on how willing your graphic designer is to let go of certain features of their design. (ie font choice on menu items).It works a lot easier if you have website guidelines and/or corporate style guide. (I had four - State Government website guidelines, State Government style guide [print orientated], agency specific website guidelines and separate agency style guide. A couple of years back did a major agency wide redesign, had the choice between two inhouse print graphic designers, one who had built websites a few years early, ie creating table based layouts by cutting up psds and one with no experience in web. Went with the designer with no web experience, because it was easier to teach from scratch than make them relearn everything. They knew the style guides (which fixed most font choices, including menus), in addition they knew from the start, font size had to be relative and page width elastic. Spent a day at CSS Zen Garden showing what can be done (and to get some inspiration), the designer went away and produced a couple of illustrator files that got converted into HTML and CSS very easily. Nick Cowiehttp://nickcowie.com ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
[WSG] An alternative to browsercam
Screenshots of a site of your choosing of from various browsers and it is freehttp://browsershots.orgvia D. Keith Robison -- Nick Cowiehttp://nickcowie.com ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] Standards sites with clever use of Flash?
The best I can offer is one that use flash for vector images and scales depending on the width of your browser window. (try a few size c=variations)http://nickcowie.com/It is a proof of concept and there are some problems anybody not using a windows flash player (ie Mac or *nix). More details read: http://nickcowie.com/2006/elastic-fluid-design-some-notes/Nick-- Nick Cowiehttp://nickcowie.com ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] Flash is more accessible than CSS?
The article appear based around one person, Leonie Watson opinions and they are very different to mine and probably most people on this list. Leonie Watson quote about CSSHowever, that's quite a new technology, it's only been around a couple of years, and a lot of designers are still very wary of using it.But wasn't CSS introduced in 1996 the same year as Future Splash aka Flash? (source wikipedia)Most designer I know are more wary of using Flash than CSS. I know because I have been campaigning to use flash for vector images and most designers are wary of using flash over a gif or jpeg even though the flash file is much smaller file and can be scaled. Two years ago, Adobe updated this technology so designers using Flash could build in accessibility features.I saw Bob Regan Macromedia and now Adobe accessability evangelist, give a demo four years and I was impressed then by how accessible Flash could be in the right hands. (He also gave a great demo on CSS and accessibility). Macromedia and Adobe have been working on Flash accessibility for many years now, not the last couple. It [Flash] has a lot of very easy ways to build in accessibility, providing the developer sets out to do that from the beginningAs with any website technology, flash or otherwise. The main problem is the lack of flash web designers who understand accessibility. I have yet to met a flash web designer who has a more than a basic understanding of accessibility and actually builds accessible flash websites. The best I have seen is a text only alternate version. Not that I have meet a lot of flash web designers. My opinion (and that what it is an opinion) is that flash website can be accesible when:1. the are built by a flash web designer who understands accessibility and how to achieve that with flash; and2. the audience are using a reasonably powerful windows computer with recent versions of the OS, IE, flash and other software required (ie the latest version of JAWS as a screen reader). -- Nick Cowiehttp://nickcowie.com ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] Flash is more accessible than CSS?
RussYou are being picky ;-)I choose the date that CSS 1 recommendations where published by the W3C as the offical introduction.The point was CSS has been around as long as Flash (if not longer 10 years or 12, it is still a long time, not a couple of years) On 28/10/06, russ - maxdesign [EMAIL PROTECTED] wrote: But wasn't CSS introduced in 1996 the same year as Future Splash aka Flash? (source wikipedia)Well... Apologies for getting picky, but Hakon Wium Lie published the firstdraft of Cascading HTML Style Sheets on 10 October 1994. The draft is still online:http://www.w3.org/People/howcome/p/cascade.htmlYou can read the full history here: http://www.w3.org/Style/LieBos2e/history/ThanksRuss***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED]***-- Nick Cowie http://nickcowie.com ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] Safari doesn't like transparent flash
Safari is not to blame it is the Mac (and also Linux) versions of the flash plugins. You get the same results with Firefox on OsX, when overlaying HTML over flash 50% of the time flash appears above, the other 50% of the time below the HTML no matter which one has the higher z-index or is last in source order. Note I have not tried the new version 9 of the flash plugins to see if the problem is fixed in them.I have been told, that you can use an iframe shim to fix the problem. I just have not tested that yet. Nick-- Nick Cowiehttp://nickcowie.com ***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] Form playing havoc with nav (maybe)
SeonaIt is out of alignment for me on IE6 on Win2k.No idea why, except it looks like IE does not want to play with ul#nav being absolutely positioned. Suggestion position it relative by using float: right; and a margin. -- Nick Cowiehttp://nickcowie.com **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] Displaying page in different resolutions
Gary wrote: Yeap, but just remember some people may have browser widths starting at (1680 x 1024)wide screen LCDs are out there and it use.Viewing thefully fluid elastic sites at this resolution can be a bit frightening.Yes but those screens are WXGA which have around 150 pixels per inch. Which is means your fixed width sites appear half the size they would on regular monitor. Fully fluid sites are regular size but all text and image appear half the size they would on regular monitor, which in my opinion is worse, long lines of small text is extremely difficult to read. My suggestion, is let people choose their browser window width and the website then scales to fit their window. (Elastic design + _javascript_ enhancement)Even if you do get complaints from friends who have to read your site from the other side of the room because they surf the web with a browser maximized on a 23 screen. -- Nick Cowie http://nickcowie.com **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] Displaying page in different resolutions
Tom wrote:How about this then: http://www.positioniseverything.net/articles/jello-expo.htmlIt works well for the normal computer monitors 800px, 1024px and even 1280px wide monitors at 72dpi or 96dpi. It is what happens when you try and view them on a WXGA 15.4 screens which are 1680 pixels wide at 150dpi.Best way to replicate that is if you are using a standard monitor at arms length, roll you chair back (or stand up and move) two to three metres (6 to 9 feet) so you screen is only occuppying half the width in your field of vision is was before and try to read the screen. That is roughly what people with the latest notebooks are seeing when the view your site. Except the monitor is normal size, the text and images are all 50% of normal size, because they have twice as many pixels per inch. Nick-- Nick Cowiehttp://nickcowie.com **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] Re: what do you use instead of embed
Personally I use a little bit of _javascript_ to handle the eolas patent in IE and the does not have flash alternative content issue, SWFobject is my personal choice. An equally good alternative is Unobtrusive Flash Objects-- Nick Cowiehttp://nickcowie.com **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] help needed with position of text links
On 11/07/06, Germ [EMAIL PROTECTED] wrote: but i was wondering if there was another better css way??? use padding, padding: top right bottom left;note : after padding, which is missing in your CSSpadding: 1px 10px 1px 1px; will get the text 10px from the right edge, (note box model problems with IE5/5.5) vertical centering text - one line only:line-height: 35px;line-height equal to the block size will put a single line of text in the middle of the block.Two lines is ugly -- Nick Cowiehttp://nickcowie.com **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] Can it be done?
You can make your flash object fluid by providing a % width via CSS. Unfortunately it does have one problem, you need to provide the flash object with both a width and height to keep it proportional.However it is not impossible, go to my blog, a couple of posts http://nickcowie.com/2006/the-fluid-elastic-reboot/ and http://nickcowie.com/2006/flash-and-the-fluid-elastic-design/ give some details of the techniques I used to get the header image which is a 4k flash file to stretch and remain in the right proportions. You can resize the browser window from 600px to 4000+px wide and the header graphic will fill the width of the whole browser window. _javascript_ is used to do the scaling and to insert the flash over alternative content (for non js or non flash browsers) and of course there is the flashblock plugin. But for me flash is the only way to put scalable vector images into today's browsers. As you are using pure vector images in flash they will scale to any size. As I have tested my header to over 4000px wide and it scales fine. Note my choice of font, does cause some odd looks at certain widths. -- Nick Cowiehttp://nickcowie.com **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] Centering forms
From a quick look at the code:It has to do with the float: left; on input and label elements. (it is to do with floated block elements and non-floated parents)I would say the 1px margin around #contorno is actually only a single line.
The quick fix is add another div to contain #contorno, lets call it #holder and use the following CSS instead of the current #contorno values#holder {
margin 0 auto;
width: 50%;
text-align: center;}#contorno { margin 18em 0 0;border: 1px red solid;float: left;}unwritten rule of CSS #2if you float a block element and it misbehaves float it's parent element
-- Nick Cowiehttp://nickcowie.com
**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] Pixel Perfect
Adobe Acrobat has the ability to capture a website as a pdf documentWhen I last used it with Acrobat 4 in about 2001, it's rendering engine then was quite different to other browsers at the time (IE5 and NN4.7). The differences that your client is seeing is probably due to differences in rendering engine. ie the Adobe engine is not standard compliant.My advice, show your client how to capture her website using tools other than Adobe Acrobat. -- Nick Cowiehttp://nickcowie.com **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] Why is Border Getting Eaten
If you float div#pagebody the border will returnAn element that contain floated elements must be floated to retain their height. Hopefully somebody can explain it fully (and better than that). -- Nick Cowiehttp://nickcowie.com **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] Pixel Perfect
Bruce [EMAIL PROTECTED] wrote: Quote:The differences that your client is seeing is probably due to differencesin rendering engine. ie the Adobe engine is not standard compliant. Is great info!!!**I should of written:The differences that your client is seeing is probably due to differences due to the Adobe rendering engine. ie that engine is probably not standard compliant.It was a few years ago since I had to deal with saving websites (or in my case intranet newsletters) as pdfs. There were rendering differences then and probably still are now, don't know how big the adobe web capture team is and how fast they are moving. You will need to do research (I could not find anything with a quick look on the adobe site).-- Nick Cowiehttp://nickcowie.com **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] Pixel Perfect
Adobe Acrobat has the ability to capture a website as a pdf documentWhen I last used it with Acrobat 4 in about 2001, it's rendering engine then was quite different to other browsers at the time (IE5 and NN4.7). The differences that your client is seeing is probably due to differences in rendering engine. ie the Adobe engine is not standard compliant.My advice, show your client how to capture her website using tools other than Adobe Acrobat. -- Nick Cowiehttp://nickcowie.com **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] Accessibility standards - for commercial consumption
Gian Sampson-Wild wrote: - WCAG 2.0 has *not* been released yet. Success criteria such as parsedunambiguously and baseline may change significantly before then. I would notrecommend completing any work until WCAG 2.0 has been released as a W3C RecommendationAgreed we need to wait, but if WCAG 2.0 is released as a recommendation without major changes, something needs to be done to translate WCAG 2.0 into language understood by developers, so it can be implemented. I would seriously hope the W3C employ a small team to write clear concise version of how to apply the WCAG 2.0 guidelines to technology X. (one for XHTML/CSS, another for JS etc.) - Without spending a significant amount of time reading the documents weneed to be careful not to misinterpret particular success criteria. Forexample, the parsed unambiguously success criteria specifically does *not* require you to validate your documents.I agreed, parsed unambiguously does not mean you must validate your documents. However, is there a tool to help you make sure the documents you write are parsed unambiguously. For HTML it is the HTML validator. Otherwise the author will need to check manually against all the user agents that fit the baseline, that they are parsed unambiguously. - The fact that WCAG 2.0 is difficult to interpret is one of the least ofits problems - even in plain English there are checkpoints missing (one Member of the Working Group has just lodged a formal complaint about thelack of cognitive disability related success criteria - a complaint that Ihave cosigned). Creating a plain English version of WCAG 2.0 will still be an incomplete set of guidelines.I disagree that interpretation is a minor problem. Yes WCAG 2.0 is seriously lacking when it comes to dealing with cognitive disabilities and there are other problems. But once WCAG 2.0 is released as a W3C recommendation, good or bad it will have an impact. The translation is need to make sure developers at least apply the WCAG 2.0 instead of ignoring it because they do not understand it. - Joe Clark is not talking about rewriting WCAG 2.0 in plain English - he is talking about rewriting the guidelines completely. Writing WCAG 2.0 in plainEnglish will legitimise a document that still has serious problems.The problems are which guidelines will have more influence: The WCAG 2.0 with some serious problems (and good as well) released by the W3C, orA set of guidelines (no matter how superior) released by Joe Clark and the secretive WCAG ninja.For the next few years at least, the W3C recommendations, they will be seen by most people as the accessability guidelines purely because they come from the W3C.. - This mailing list (mostly) contains people with a significant amount of experience in the web standards area and not so much in the accessibilityarea. The irony is that WCAG 2.0 practically ignores web standards entirely.The target audience for this translation is the people on this mailing list, developers. The people you want writing guidelines for developers are developers with a good understanding of and care about accessibility and you should find a good few on this mailing list. - And finally, there is not yet any evidence that we (Australia) will ever need to refer to WCAG 2.0. HREOC - the governing body - may decide to keepreferring to WCAG 1.0 instead of WCAG 2.0. They may also decide to writetheir own set of guidelines.Do you want to talk about the HREOC guidelines on pdfs and how they are ignored by almost all of Australia (including most Government departments). Personally I do not see HREOC as the governing body, more as the sheriff whose job it is to round up the really bad offenders and publicly humilate them. HREOC's big stick is to taking the offending company/government department to court. How do you think a case would go with HREOC saying the offending web site is inaccessible because it did not validate it's documents as required by the HREOC guidelines and the web site is inaccessible. And the defendant saying it complied with the accepted international standard, the WCAG 2.0 by ensuring that all it's documents could be parsed unambiguously. No judge is going to be able to understand the issues and with a good lawyer arguing accepted international standard vs HREOC guidelines, HREOC will be left paying hefty court costs. Nick CowieB. PsychologyWeb Services ConsultantState Library of Western Australia
Re: [WSG] HELP: Disappearing text and other problems in IE
A lot of your problems relate to using relative font sizes (you use % for font size) and expecting them to line up neatly over an image when you use pixels to size your images. Warren is right just quickly - I can see that you have position:absolute - but u dont specifiy a position WHERE. also - u have it floated right. Float: right; effects #help-nav not position: absolute; where as position: absolute; effects #nav not float: right; try doing position: relative and put your nav ul INSIDE the header div, allow room for it in your div height and then positon it so it is in the bottom of the header div.In your HTML put #help-nav and #nav inside #header In your CSS add position: relative; to #headerremove float: right; and the margins from #help-nav and #navadd top: 0; left: 50%; to #help-navadd bottom: 0; left: 50%; to #navthat should help, it should work on standard font sizes but increase the font size a couple of steps and problems will occur. Nick-- Nick Cowiehttp://nickcowie.com
Re: [WSG] Goals for FF Text Zoom?
Other than being totally pig headed and building sites that will not break not matter what the level of text zoom.As a rule of thumb, I am with Gunlaug All resizing steps in IE/win. 8 - 10 steps (or 200%) in Mozilla / Firefox, Safari and Opera I don't worry too much about smallest is IE, but it has to work down two or three steps in Mozilla/Firefox, Safari and Opera.-- Nick Cowiehttp://nickcowie.com
Re: [WSG] CSS problem
JohnGiven your fluid layout, the only way to stop the input boxes breaking out is to give them a relative width (ie relative to their container)input: { width: 85%;} works in FF on a PC--
Nick Cowiehttp://nickcowie.com
Re: [WSG] Australian Govt guidelines
I'm looking for some australian govt accessibility guidelines - both disability wise and other cases like content management for dial up connection speed etc.You didn't specify FedGov, so I thought I'd throw this at you:The VicGov Acessibility Toolkit http://www.egov.vic.gov.au/index.php?env=-categories:m1496-1-1-7-sThe West Australian accessibility guidelines are chapter four of Guidelines for State GovernmentWebsites found at: http://www.egov.dpc.wa.gov.au/index.cfm?event=policiesWebGuidelinesThey are fairly basic you must met level 1 WCAG 1, should met level 2 WCAG 1 and may met level 3 WCAG 1The WA website guidelines were good in their day, over four years ago, but have only been amended once in the past three years. The Vic stuff is more up to date. Nick
Re: [WSG] IE 7 beta 2 and IE6 Standalone
TeeI have been running IE7 beta 2 and IE6 Standalone on XP SP2 AMD PC without a problem. IE7 beta 2 worked like a charm and I only used IE6 (along with IE4, IE5 and IE5.5) for site testing. So I have not pushed IE6 too hard, just for testing sites locally and a couple of sites. I will check the print menu when I get back home. I had originally tried the IE7 standalone, but that kept crashing, even the batch file version.It is possible to run multiple versions of IE at the same time, I have done it, problem is remembering which one is which when you have four instances running. -- Nick Cowiehttp://nickcowie.com
Re: [WSG] UK Standardistas - PAS 78
Joe Clark did and he blogged about it http://blog.fawny.org/2006/03/21/pas78/ as only Joe can ;-)-- Nick Cowie http://nickcowie.com
