, 2009 1:22 PM
To: cf-talk
Subject: (sot) CF and Section 508 compliance a 508 compliant date/time
picker
We just picked up a site that needs to be 508 compliant. I am getting a
crash course right now. I (or any of us really) never made a site/app that
needed to be 508 compliant.
My only
[mailto:ju...@wiredotter.com]
Sent: Friday, February 20, 2009 11:31 PM
To: cf-talk
Subject: Re: (sot) CF and Section 508 compliance a 508 compliant date/time
picker
I'd also recommend looking at the ARIA (accessible rich internet
applications) initiative through the W3C:
http://www.w3.org/WAI/PF/aria
that there
are plans to do so in a future release.
-Original Message-
From: Judah McAuley [mailto:ju...@wiredotter.com]
Sent: Friday, February 20, 2009 11:31 PM
To: cf-talk
Subject: Re: (sot) CF and Section 508 compliance a 508 compliant date/time
picker
I'd also recommend looking
We just picked up a site that needs to be 508 compliant. I am getting a
crash course right now. I (or any of us really) never made a site/app that
needed to be 508 compliant.
My only concern is the use of JS. It is basically a data entry and reporting
app and there is going to be a TON of form
Gerald Guido wrote:
using CFForm will be an issue. Yes I know... we shouldn't use CFForm etc..
but it is uber-crunch time and that is what our code generator spits out.
I'm curious, what are the current torch and pitchfork arguments against
using CFFORM? In the past it was terrible and I
Also.. Does anyone know of any 508 compliant date/time pickers? Those
are going to be the only JS widgets that may be an issue.
Any date-picker should be fine, provided that the widget is used to
populate a text field that can also be manually entered. I integrated
the Dynarch widget into the
AM
To: cf-talk
Subject: (sot) CF and Section 508 compliance a 508 compliant date/time
picker
We just picked up a site that needs to be 508 compliant. I am getting a
crash course right now. I (or any of us really) never made a site/app that
needed to be 508 compliant.
My only concern is the use
Any date-picker should be fine, provided that the widget is used to
populate a text field that can also be manually entered.
Thanx Ike,
So if I understand correctly, if I have a date/time widgets that can can be
used as (or considered to be) a convenience or an adjunct, but not the
primary
Any date-picker should be fine, provided that the widget is used to
populate a text field that can also be manually entered.
Thanx Ike,
So if I understand correctly, if I have a date/time widgets that can can be
used as (or considered to be) a convenience or an adjunct, but not the
I'm curious, what are the current torch and pitchfork arguments against
using CFFORM?
No reason for me to bring it up other than to avoid having the post
derailed. I have seen it brought up a few times tends though not as bad as
evaluate(). I have been using CF form for years with out a problem
If we have time we will roll our own, prolly using spry as long as it
doesn't conflict with the Dynarch widget like said it could/would.
You can work around that by disabling Spry's date hints for
date-validated text fields.
--
s. isaac dealey ^ new epoch
isn't it time for a change?
Subject: (sot) CF and Section 508 compliance a 508 compliant date/time
picker
We just picked up a site that needs to be 508 compliant. I am getting a
crash course right now. I (or any of us really) never made a site/app that
needed to be 508 compliant.
My only concern is the use of JS
=
http://www.shayna.com
Training and Consulting in CSS and Accessibility
Team Fusebox
-Original Message-
From: Gerald Guido [mailto:gerald.gu...@gmail.com]
Sent: Friday, February 20, 2009 1:22 PM
To: cf-talk
Subject: (sot) CF and Section 508 compliance a 508 compliant
13 matches
Mail list logo
