Re: [WSG] JavaScript Language Clarifying within HTML

The language attribute was deprecated in html 4, so I wouldn't advise using it. see: http://www.w3.org/TR/REC-html40/interact/scripts.html#h-18.2.1 Thanks, David On 14/7/09 13:23, Brett Patterson wrote: I am not sure about the most recent standards regarding the language attribute of the

Re: [WSG] utf8 character display problem

you should also be able to add/edit a .htaccess file on the shared web space and add the following: AddDefaultCharset utf-8 most hosts, even shared hosts should allow this (and it saves adding php headers to every page) Thanks, David On 7/7/09 18:46, Nick Roper wrote: Hey Rimantas, I

Re: [WSG] SEO vs. Accessibility

spider, google do manually check pages (either randomly, or when the spider, or even a person, flag something up). Its that manual detection that will spot this kind of fraud, and will likely result in an immediate ban. regards, David Dixon e: da...@temperedvision.com w: www.temperedvision.com

[WSG] Javascript Accessibility

others thoughts on the subject. David -- David Dixon t: 07967 569 489 e: da...@digitaloasis.co.uk linkedin | http://www.linkedin.com/in/davidjdixon twitter | http://twitter.com/daviddixon *** List Guidelines: http

Re: [WSG] Javascript Accessibility

, t'was a fairly minor point, but yes i think you're interpretation of the request is more accurate than my initial one. David -- David Dixon t: 07967 569 489 e: da...@digitaloasis.co.uk linkedin | http://www.linkedin.com/in/davidjdixon twitter | http://twitter.com/daviddixon

Re: [WSG] Javascript Accessibility

, not on WAI ARIA, apologies if the content of my original email didn't make this clear. My issue with ARIA is one of documentation, and would prefer deal with ARIA in a separate conversation. David -- David Dixon t: 07967 569 489 e: da...@digitaloasis.co.uk linkedin | http

Re: [WSG] Javascript Accessibility

Guys please, move this to a different topic, this ARIA issue has now clouded the original question. David -- David Dixon t: 07967 569 489 e: da...@digitaloasis.co.uk linkedin | http://www.linkedin.com/in/davidjdixon twitter | http://twitter.com/daviddixon Matt Morgan-May wrote: As someone

Re: [WSG] Opera Targeting?!

Not quite right im afraid. Patrick Lauke sent an email about this in December that highlighted the Firefox zoom config as shown below: -- Quote -- toolkit.zoomManager.zoomValues, and this will show the various zoom factors at each step. In my case (which should be the default) these are: .3,

Re: [WSG] Opera Targeting?!

Chomping at the bit to dismiss IE7 a little early aren't we Georg? :) David Gunlaug Sørtun wrote: Besides: one should only target/hack dead browsers, like IE7 and older. Targeting/hacking live browsers like Opera, Firefox, Safari etc. for real, will only create maintenance-problems as new

Re: [WSG] Parenthesis around list counters

Either that or simply go down the PDF route and put the important legal information into a separate document. I've found similar issues to this from legal teams who require a perfect translation from a word doc etc, and as Georg says, relying on individual browser support is often not

Re: [WSG] Users who deliberately disable JavaScript

Agreed, if people have real long term usage statistics that they can share to support the claim that Javascript use is in decline, and not focus on very one-sided arguments of personal use or everyone i know then I'd be interested to hear. Until that time, or my own analysis supports these

Re: [WSG] Users who deliberately disable JavaScript

Again, can you show that the small decline in IE's market share has contributed to users blocking Javascript or using specific Firefox extensions? IE has had plugins such as the Web Accessibility Toolbar etc for some years now that allow disabling of Javascript very easily, so why would the

Re: [WSG] CSS IE6/7 - what a surprise

Just to correct Todd's reply, the :after property isnt support by either IE7 or IE6 (and below), therefore you would need to adjust your CSS to state (assuming you're using a CSS hack, for ease of display): #NameofContainingDiv { *zoom: 1; /* all your other styles for the element */ }

Re: [WSG] Examples of great high-school websites?

Perhaps the blatant disregard for common web standards could be the reason? (this is after all a web *standards* list and not a web designers list...) Lets see: - tables for layout - no alt attributes for images - obtrusive javascript (are professional companies really still getting away

Re: [WSG] dl v table for form layout

Personally I think that form elements lend themselves to practically all the semantic meaning you need. Labels and input elements are either implicity or explicity linked (ie either labellabelnameinput ...//label or label for=myinput/labelinput id=myinput.../), and then you have fieldsets as

Re: [WSG] Hack for all IE versions including 7

The problem is though, that these browser never actually go, they simply evolve a little which doesn't always make the hack redundant, just altered slightly. Therefore, for me, having the hacked styles alongside the valid css styles makes things infinitely easier to see what is actually

Re: [WSG] PopUp windows

Hi Bob, You may want to look at solutions like thickbox (http://jquery.com/demo/thickbox/) which offers a very degradable way to open faux popups, or floating divs, and also adds some nice animation in there too. This way, if the browser has javascript support (and it's enabled) then what