Sorry Lea,
I get around 100 emails a day. Accessibility is in the scope of my work. AOL
definitely isn't.
... and if everyone on this forum had just a little bit of chatter OT then it
makes it hard to find the posts on topic.
c.
On 16/06/12 9:35 AM, Chris Pearce wrote:
I'm sorry but how is
is there for printing.
Darren Lovelock
MunkyOnline.comhttp://MunkyOnline.com
On 12 Sep 2011, at 05:57, Chris Vickery
chris.vick...@oaic.gov.aumailto:chris.vick...@oaic.gov.au wrote:
Hi all,
We’ve got some flat forms on our site, ie. They are not interactive forms, and
have no submit button
Hi all,
We've got some flat forms on our site, ie. They are not interactive forms, and
have no submit button. They are indicating that it's a check list that can be
ticked once the page is printed.
Someone suggested putting in regular check boxes and having no submit button,
but wouldn't that
Hi Marvin,
The date and time pop up in your menu bar when you click on copyright...
It's not accessibility or standards related but your copyright message needs
fixing.
It should at least read No unauthorised reproduction of material is allowed by
the copyright holder. Any unauthorized person
] Is pressing Enter to submit (or not) on forms an
accessability issue? [SEC=UNCLASSIFIED]
2009/10/21 Chris Vickery chris.vick...@privacy.gov.au:
In this case it's for an input field, not a textarea, and enter will still
not submit (unless you tab out) so in this case makes it contrary to 'native
We're accessibility testing at the moment. We've got some email forms (ie. Put
in your email address to subscribe - submit) that do not currently submit if
you press enter.
Personally I feel this should be an accessibility issue, but I am finding it
difficult to locate any solid documentation
) wireless device
From: Chris Vickery chris.vick...@privacy.gov.au
Date: Wed, 21 Oct 2009 10:20:51 +1100
To: wsg@webstandardsgroup.orgwsg@webstandardsgroup.org
Subject: [WSG] Is pressing Enter to submit (or not) on forms an accessability
issue? [SEC=UNCLASSIFIED
There's also a guide for Australian Government agencies here:
http://webpublishing.agimo.gov.au/
As a couple of people have said... at the end of the day it's just different
flavours of W3C
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
You used to be able to slice an image up in Photoshop and export it as HTML.
I’m not even sure if you can still do that. It used to make THE ugliest code,
maybe that’s how they did it, wouldn’t be the first time.
Regarding copyright... if you’re in Australia there’s a book put out by
That's an awesome help. Thanks everyone!
http://googlewebmastercentral.blogspot.com/2008/11/googles-seo-starter-guide.html
http://www.useit.com/alertbox/990321.html
http://www.w3.org/Provider/Style/URI
***
WARNING: The
Does anyone know where I could find a best practice guide to naming URLs?
We're trying to keep our URLs descriptive like...
www.whatever.com/news/events/index.html
...but not like this...
www.whatever.com/news articles/Events Sent from m...@me.com/my.file
I need it to pass on to a manager.
[mailto:li...@webstandardsgroup.org] On
Behalf Of Chris F.A. Johnson
Sent: Friday, 20 February 2009 1:29 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] URL naming best practice guide? [SEC=UNCLASSIFIED]
On Fri, 20 Feb 2009, Chris Vickery wrote:
Does anyone know where I could find a best
What's the best way to place a link in a document?
Is it more accessible to have your link in a sentence, as the URL, or as the
word 'link'?
ExampleA makes the information more readable but the link less visible
ExampleB the link is visible and page a bit neater but target URL hidden
ExampleC
That is a very cool tool. Nice job.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Jon Gunderson
Sent: Tuesday, 17 February 2009 4:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility testing
You can try the
That is a very cool tool. Nice job.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Jon Gunderson
Sent: Tuesday, 17 February 2009 4:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility testing
You can try the
That is a very cool tool. Nice job.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Jon Gunderson
Sent: Tuesday, 17 February 2009 4:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility testing
You can try the
That is a very cool tool. Nice job.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Jon Gunderson
Sent: Tuesday, 17 February 2009 4:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility testing
You can try the
That is a very cool tool. Nice job.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Jon Gunderson
Sent: Tuesday, 17 February 2009 4:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessibility testing
You can try the
If you're using outlook just set up a rule. Something like...
Where the subject line contains out of the office or autoreply then move it
to (trash or junk mail or a subfolder)
Works most of the time.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
More reasons to keep 'em short:
1. Makes it easy to quote URL (maybe over the phone)
2. I've seen a few email or publication programs break URLs where there's a
line return, so breaks the hyperlink
3. Makes layout difficult for desktop publishers and marketing ie.
anyway.
BAD IA IMHO
Joe
OK, in marketing terms you can easily create your own TinyURL by
redirecting vimportant traffic through a rewrite.
On 05/11/2008, at 12:40 PM, Chris Vickery wrote:
More reasons to keep 'em short:
1. Makes it easy to quote URL (maybe over the phone)
2. I've seen
Reiterating what Gerard said yesterday, my experience has also been that the
code is as compliant as the template you designed for the page.
I've implemented many contribute systems for clients and without exception
they've found it easy to use and does everything that they want. Some of these
I've been looking into this recently too.
I found a lot of info from Adobe of how accessible Acrobat can be made, but my
experience was that it takes a long time to set them up properly.
The success (or not) comes from how cleanly the pages were set up in the first
place, with proper heading
Sorry. Slightly OT:
Just a suggestion... there's every chance lecturer is just looking for a way to
assess that you've got demonstrated knowledge of when upper and lower case is
appropriate in HTML.
If you discuss it with him he'll probably think it's great you're interested.
If you approach
Hey Bob,
I totally agree with Ted and designer, and people who have the phone number
auto Skype 'thing' turned on will actually be expecting that highlighting on
any phone numbers. You should make it clear that you're really reducing the
accessibility of the page by disabling the feature, as
The AGIMO guidelines specify minimum A, preferably AA.
http://webpublishing.agimo.gov.au/Accessibility
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Boyd
Sent: Monday, 18 August 2008 8:58 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Lawsuits for inaccessible
Hi,
For anyone with experience in making a Joomla! site generate compliant code,
are there any tips, tricks, pitfalls or advice that you could impart?
We've got a company setting a site up for us in Joomla. Their other sites
seemed to validate quite well, but it would be great to get
27 matches
Mail list logo
