As I said - the coding errors.
On Sat, January 17, 2009 8:03 pm, Rick Faircloth wrote:
What did you find to be so bad about the site, Stuart?
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Stuart
Foulstone
Sent: Saturday,
If there were further communication between the user and server
between submission of the form that would entail a page reload then a
screen user shouldn’t have an issue, whereas if JavaScript would run
in the background and inject errors or suggestions as it thinks the
user makes them
There were a couple of articles on SitePoint (if I recall correctly) six
months ago or so, that covered this, in a fairly positive light.
I'm afraid I'm not in a position to chase after them right now; perhaps
someone else does have the time?
Mike
I am currently away and will be back on Thursday 22 Jan. Please contact IT
Helpdesk for IT matters or Joy Horton for all other matters.
***
This e-mail may be confidential and/or
after all it's impossible to tell those users using an accessibility aid like
a screen reader
from those who do not, and hey, the growing number of users who purposefully
disable
JavaScript won't see the glitzy JavaScript injected errors anyway.
Agreed, and any decent validation is going
Hmm, I made a typo. Coffee time.
On 1/20/09, james.duc...@gmail.com james.duc...@gmail.com wrote:
after all it's impossible to tell those users using an accessibility aid
like a screen reader
from those who do not, and hey, the growing number of users who
purposefully disable
JavaScript
Server side validation is of course a must...
however, if the visually impaired visitor has _javascript_ turned on and
these error elements are created, they won't exactly get to the server
side validation now, will they? ARIA looks good, looking forward to it
getting out of draft status.
Patrick H. Lauke wrote:
As the lord of microformats Tantek seems so vehemently opposed to it, I
sincerely doubt it will happen any time soon. It's now been roughly
three years since the debate around ABBR issues first started, and
little visible progress seems to have been made. Who knows,
Sorry, I was a bit vague. I'm saying do all validation server-side. If
you're looking for a quick and dirty solution to the element injection
issues when screen readers are being used, you can try setting focus
back to the new element's parent, though shifting focus is a practice
often frowned
Anthony Ziebell wrote:
ARIA looks good, looking forward to it getting out of draft status.
I wouldn't be waiting for ARIA to get out of draft before using it :) It
has pretty good support in browsers already so get stuck in. And because
essentially all you are doing with ARIA is adding
My only concern with a draft is that things change...
Chris Knowles wrote:
Anthony Ziebell wrote:
ARIA looks good, looking forward to it getting out of draft status.
I wouldn't be waiting for ARIA to get out of draft before using it :) It
has pretty good support in
.
http://www.theage.com.au/travel/virgin-blue-in-court-over-website-20090119-7kc1.html
Been a while since SOCOG..
Best
Chris
http://www.cogentis.com.au/
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
2009/1/20 Chris Dimmock chris.dimm...@gmail.com:
Did anyone else see this??
http://www.propellerglobal.com/news/News/128/virgin-blue-to-court-again-for-discrimination
http://www.theage.com.au/travel/virgin-blue-in-court-over-website-20090119-7kc1.html
Been a while since SOCOG..
Yes
Hi All,
If you haven't seen this yet, it may be of practical use when and if needed:
Validating (X)HTML + ARIA: http://www.paciellogroup.com/blog/?p=107
Written by Steve Faulkner, Technical Director - TPG (The Paciello Group)
Europe, Director - Web Accessibility Tools Consortium from his blog.
Is it true XHTML 1.1 supports modularization and thus, ARIA, except for
the role attribute / values? XHTML 1.1 (latest draft) allows XHTML 1.1
to be served as text/html as defined in RFC2854 or application/xhtml+xml
as defined in RFC3236. This is exciting as it looks like we are so close
to
15 matches
Mail list logo