Tom,
I put this together a while ago which you'll probably find useful
http://www.dave-woods.co.uk/?p=91 with it in action here
http://www.dave-woods.co.uk/wp-content/uploads/2007/09/accessible-forms1.html
If you group the label with the form field then it's usually much
easier to style the
Glad it helped :o)
The idea for the span around the legend and div around the
fieldset initially came from
http://www.tyssendesign.com.au/articles/css/legends-of-style/
This then gave me the idea of including a span around the actual
label text as it then provides extra flexibility for styling
Mike, This is exactly the reason why I include the br at the end of
the labels so that the form still displays nicely without the styles
applied.
I suppose a better case could be made for removing the display: block;
from the labels in this situation but would be needed if for example
you wanted
Alternatively you could introduce and extra div and apply padding/margin
to create the effect you need. If the background outside the container is a
plain colour you could always apply a border-top or 120px to make it appear
as you want.
The first will definitely work for your situation whilst
Hi,
Are these what you're after?
http://www.w3.org/TR/WAI-WEBCONTENT/
http://www.section508.gov/index.cfm?FuseAction=ContentID=12
Thanks
Dave
On 03/10/2007, Tom Livingston [EMAIL PROTECTED] wrote:
Hi listers,
Does anyone have a reference (link) to a site that actually spells out
what
attributes, using semantic HTML, ensuring that JavaScript
isn't used for critical functionality etc shouldn't be nice to have's
for the client, they should be built in as standard by any reputable
web designer.
- - - - - - - - - - - - - - - - - - - - - - - - -
Dave Woods
http://www.dave-woods.co.uk
of development that
they now need to consider accessibility.
- - - - - - - - - - - - - - - - - - - - - - - - -
Dave Woods
http://www.dave-woods.co.uk
[EMAIL PROTECTED]
On 08/10/2007, Steve Green [EMAIL PROTECTED] wrote:
The cost of adding accessibility should really be zero.
Statements like
.
Hope that helps.
Dave
- - - - - - - - - -
Dave Woods
http://www.dave-woods.co.uk
On 23/10/2007, Gaspar [EMAIL PROTECTED] wrote:
Hello,
iam trying to understand how a page that have 1 or 2 javascript in
href could pass in level A of WCAG 1.
it have a noscript but that doesnt prove
Hi Dean,
Not sure what these two styles are actually doing but it looks like
they're the cause within your menu.css
#p7TBMsub03 { padding: 0 0 0 150px; }
#p7TBMsub04 { padding: 0 0 0 210px; }
Removing them seems to fix the problem with no adverse effect.
Cheers
Dave
- - - - - - - - - -
Dave
altogether.
Hope that helps.
- - - - - - - - - -
Dave Woods
http://www.dave-woods.co.uk
On 24/10/2007, Dave Woods [EMAIL PROTECTED] wrote:
Hi Dean,
Not sure what these two styles are actually doing but it looks like
they're the cause within your menu.css
#p7TBMsub03 { padding: 0 0 0 150px
Hi Simon,
If you have an image for purely presentational purposes then you can
use a blank alt attribute
alt=
However, if it's purely for presentational purposes then you should
really apply it using CSS as a background image ;o)
Thanks
Dave
http://www.dave-woods.co.uk
On 26/10/2007, Simon
As a general rule, any images that add to the content or are required
for navigation should be applied as a foreground image using the img
tag and an alt attribute should be applied.
If an image is purely for presentation then use CSS and apply it as a
background image.
Obviously there are
Yeah, the webdev toolbar for Firefox has direct links to the
cynthiasays (WAI) checker and the section 508 checker along with some
other useful tools so if you don't already have it, that's a must for
all developers.
http://chrispederick.com/work/web-developer/
There's also a colour contrast
Sorry about that, the validator seemed to suggest that you had some
image tags that weren't closed and that you were using instead of
amp; but having validated it again, it appears fine. Strange.
I've had problems with the WAI validator in Firefox sometimes as well,
it seems that locally it has
It depends what you're using it for. If it's for black hat search
engine tactics which will contain keywords then yes it's bad as it can
get you completely banned from Google.
If it's for hiding an element of the page which you'll then be
displaying using either CSS or JavaScript then it's not
As far as I'm aware, it's not something that Google will automatically
ban a site for anyway but if it is being used for black hat tactics
then the site is open to being reported by anyone (possibly a
competitor) which Google may then do a manual check of and ban the
site if they deem the site to
Hi Mike,
I was considering using span's instead of div's for my example but
was a little torn between the two as I'd usually use span's for
their inline purpose in a block of text or for styling something
within an inline element (when obviously a div would be invalid).
I suppose in either case
Hi James,
I'd always create a site and content so that it initially works and
all the content can be reached using just HTML. It certainly won't
look all that pretty but by making sure that everything works fine
before you add CSS or JavaScript then you're ensuring that the site
will be usable
Hi Michael,
The overall structure is probably how I'd tackle this but I do have a
couple of suggestions.
1 - You don't really need the div for part4 as this seems to just be
applying a margin which could be applied directly to #article.
2 - Within the part4infosmall div I wouldn't use a
Vanilla is definitely the most standards compliant forum software I've seen.
If you wanted to go down the social networking/bookmarking site route then
there's some software called pligg which I believe the likes of digg and
sphinn use.
http://www.pligg.com/
On 09/11/2007, Rahul Gonsalves
I'm in a similar position and recently bought the Simply JavaScript book
from SitePoint... it's easy to understand and all the books I've seen of
theirs in the past have been up to date and use the latest standards so I
presume I'm learning the correct way as apposed to following out of date and
Looks like it's more likely to do with your use of the pre tag.
Firefox is allowing the content to overflow into the other container whilst
IE6 won't.
The easiest fix would probably be to use some kind of overflow: auto; in
that section of the page along with a width to force a scrollbar on any
Hi,
Principles of Beautiful Web Design is worth a read, not only for the
information on colours and the theory behind is but there's also plenty of
other useful design information especially for web developers who aren't
from a design background.
http://www.principlesofbeautifulwebdesign.com/
Hi,
Personally, I'd use heading's for the questions and paragraphs for the
answers but that's down to my own preference and have seen it done a variety
of ways.
Cheers
Dave
- - - - - - - -
http://www.dave-woods.co.uk
On 17/01/2008, Mike at Green-Beast.com [EMAIL PROTECTED] wrote:
Hello
I completely agree with most of the comments so far. Why create
functionality that is simply replicating the functionality of a browser?
There was an article on text resizing a while ago that I'm sure most people
are already aware of by Roger Johansson...
The first question I'd ask is why not just use check boxes instead of trying
to replicate them? If you mark them up correctly then there's really no
better accessible method than using the correct element as it was meant.
If you go down this route then you're likely to create all kinds of
]
[mailto:[EMAIL PROTECTED] *On Behalf Of *Dave Woods
*Sent:* Wednesday, January 23, 2008 8:59 AM
*To:* wsg@webstandardsgroup.org
*Subject:* Re: [WSG] Background images versus image
The first question I'd ask is why not just use check boxes instead of
trying to replicate them? If you mark
I just like to ask if it might be possible to turn off this version
freezing thing in IE8, maybe with some markup or something. I agree
with Drew Mclellan when he said in his blog that old browsers must die.
Using an HTML5 doctype will remove the need to include the meta tag. Using
edge within
A better approach would be to switch to a more standards compliant browser
like Firefox/Opera or Safari ;o)
http://www.mozilla.com/en-US/firefox/
http://www.opera.com/
http://www.apple.com/safari/ (still appears to be in beta for windows
though).
If you're a web developer/designer, you should
Also, think about the important factors first when creating a website. Build
something that satisfies the requirements, provides the function/content
required, is accessible, usable and uses the latest web standards and if the
site falls into the web2.0 category then so be it, if not then really
Hi Andrew,
As Thierry has pointed out, Zoom will fix this issue but you may want to
have a read of the following as it explains the reasons why...
http://www.satzansatz.de/cssd/onhavinglayout.html
For fix width layouts, I'd usually tend to fix this by providing a width (in
your case width:
...
I know there's a lot of people that don't like conditional comments,
but it can save A LOT of time.
Best Regards,
On Thu, Feb 14, 2008 at 7:29 AM, Dave Woods [EMAIL PROTECTED]
wrote:
Hi Andrew,
As Thierry has pointed out, Zoom will fix this issue but you may want to
have a read
Looks like the double margin bug.
Try changing this...
#navMain ul li a
{ margin:43px 35px 0 0;
border:1px solid black;
float:right; display:block;
}
to this
#navMain ul li a
{ margin:43px 35px 0 0;
border:1px solid black;
float:right; display:inline;
}
Hope that helps.
On 15/02/2008, kevin
I'm sure John won't mind me posting a link to his article on the subject...
http://www.tyssendesign.com.au/articles/css/legends-of-style/
Hope that helps.
2008/2/28 Cole Kuryakin [EMAIL PROTECTED]:
Hello All -
I've already spent a lot of time researching this and - from the threads
I've
Try getting rid of the comments in your source code. I've not had chance to
investigate your code thoroughly but that's usually what causes the
duplicate character bug.
I'm sure that there are other fixes for it but I personally find that if
you've structured your markup correctly, indented
Go for the first option...
h2section title/h2
ul
liapage name 1/a/li
liapage name 2/a/li
...
/ul
Google won't give anymore weight as it'll simply dilute the weight of all
your h3 tags so only use them where they're relavant and where they are
actually heading up contnet.
I'd always advise
Personally, I'd use overflow on the container to clear the float's and then
add width: 100%; to apply layout for IE7 and below.
div#innerContainer ul{margin: 0; padding: 0;* width: 100%; overflow: hidden;
*}
Hope that helps.
Dave
- - - - -
http://www.dave-woods.co.uk
2008/4/17 Frederick
Don't fix or change anything in your site to be compatible with a beta
version.
The beta version is available so that developers can report problems to
Microsoft so that any bugs can be fixed for the final release. By changing
your code now, you're likely to find that you'll need to change it
.
On Tue, Apr 29, 2008 at 9:04 AM, Sam Sherlock [EMAIL PROTECTED]
wrote:
looks like another quagmire is about to open up;
funny how I still feel that I am getting over ie6
2008/4/29 Dave Woods [EMAIL PROTECTED]:
Don't fix or change anything in your site
I've downloaded Firebug 1.1 Beta and it seems to work fine with Firefox 3
http://getfirebug.com/releases/
Hope that helps.
- - - - -
http://www.dave-woods.co.uk
2008/6/18 kate [EMAIL PROTECTED]:
I hear about so many goodies on my lists I tried to dl Firebug (if our
people like it its got
40 matches
Mail list logo
