You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jeff Cooper <js...@gmail.com> on 2005/06/21 14:14:31 UTC
508 compliance and tacos components
The company I work for is developing an application for a federal
client and I would like to use some of the components from the t-deli
site. The one in question is the example(xtile) they have where you
type in a textbox and it starts doing the search on the keypresses.
The client wants this ability when searching for ssn's. My boss seems
to think this won't pass 508 compliance; was just wondering if anyone
knows if this would be the case. Will we run across other issues with
making the site more interactive for the user?
Thanks,
Jeff Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 508 compliance and tacos components
Posted by Scott Morgan <mo...@gmail.com>.
Well in that case you wouldn't need AJAX, you would just need some
javascript to submit the form when the SSN number has been completely
entered. I'd probably look to do this when the user tabbed out of the
field.
scott
On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
> Thanks for the info.
>
> The ssn search that the federal user has in the current application is
> that after the 9th digit is typed in; a search is automatically done
> to retrieve items such as person's name. I was hoping could do
> something similar in the web application we will be creating.
>
> Jeff Cooper
>
> On 6/21/05, Viktor Szathmary <ph...@gmail.com> wrote:
> > On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
> > > The company I work for is developing an application for a federal
> > > client and I would like to use some of the components from the t-deli
> > > site. The one in question is the example(xtile) they have where you
> > > type in a textbox and it starts doing the search on the keypresses.
> > > The client wants this ability when searching for ssn's. My boss seems
> > > to think this won't pass 508 compliance; was just wondering if anyone
> > > knows if this would be the case. Will we run across other issues with
> > > making the site more interactive for the user?
> >
> > XTile is a not part of the Tacos component library.
> >
> > Generally speaking, AJAX approaches will make it harder to achieve
> > accessibility (ie. I have no idea how screenreaders handle dynamic DOM
> > replacements, probably not very well). On the other hand, as long as
> > you use it in a conservative fashion where the functionality works
> > fine with javascript disabled, you can most likely make things degrade
> > in a usable way. The Tacos library in particular works like this
> > (http://tacos.sf.net/). You should try some tests with some relevant
> > products...
> >
> > A related note: to me auto-completion on social-security number
> > searches sounds like a profoundly bad idea, as far as privacy is
> > concerned. Not sure what federal regulations require, but one would
> > hope that the requirements are at least as stringent as credit card
> > security in ecommerce apps (which I'm familiar with, and which even
> > with all the restrictions remains unsecure in many ways :). You
> > definitely should not be able to just type in 12* to get all numbers
> > starting with that :)
> >
> > regards,
> > viktor
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 508 compliance and tacos components
Posted by Paul Woodward <pa...@gmail.com>.
Doesn't that mean you can get anyone's details? With the number of residents
there are in the US, it must be easy to make up a valid SSN, right?
On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
>
> Thanks for the info.
>
> The ssn search that the federal user has in the current application is
> that after the 9th digit is typed in; a search is automatically done
> to retrieve items such as person's name. I was hoping could do
> something similar in the web application we will be creating.
>
> Jeff Cooper
>
> On 6/21/05, Viktor Szathmary <ph...@gmail.com> wrote:
> > On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
> > > The company I work for is developing an application for a federal
> > > client and I would like to use some of the components from the t-deli
> > > site. The one in question is the example(xtile) they have where you
> > > type in a textbox and it starts doing the search on the keypresses.
> > > The client wants this ability when searching for ssn's. My boss seems
> > > to think this won't pass 508 compliance; was just wondering if anyone
> > > knows if this would be the case. Will we run across other issues with
> > > making the site more interactive for the user?
> >
> > XTile is a not part of the Tacos component library.
> >
> > Generally speaking, AJAX approaches will make it harder to achieve
> > accessibility (ie. I have no idea how screenreaders handle dynamic DOM
> > replacements, probably not very well). On the other hand, as long as
> > you use it in a conservative fashion where the functionality works
> > fine with javascript disabled, you can most likely make things degrade
> > in a usable way. The Tacos library in particular works like this
> > (http://tacos.sf.net/). You should try some tests with some relevant
> > products...
> >
> > A related note: to me auto-completion on social-security number
> > searches sounds like a profoundly bad idea, as far as privacy is
> > concerned. Not sure what federal regulations require, but one would
> > hope that the requirements are at least as stringent as credit card
> > security in ecommerce apps (which I'm familiar with, and which even
> > with all the restrictions remains unsecure in many ways :). You
> > definitely should not be able to just type in 12* to get all numbers
> > starting with that :)
> >
> > regards,
> > viktor
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
Re: 508 compliance and tacos components
Posted by Jeff Cooper <js...@gmail.com>.
Thanks for the info.
The ssn search that the federal user has in the current application is
that after the 9th digit is typed in; a search is automatically done
to retrieve items such as person's name. I was hoping could do
something similar in the web application we will be creating.
Jeff Cooper
On 6/21/05, Viktor Szathmary <ph...@gmail.com> wrote:
> On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
> > The company I work for is developing an application for a federal
> > client and I would like to use some of the components from the t-deli
> > site. The one in question is the example(xtile) they have where you
> > type in a textbox and it starts doing the search on the keypresses.
> > The client wants this ability when searching for ssn's. My boss seems
> > to think this won't pass 508 compliance; was just wondering if anyone
> > knows if this would be the case. Will we run across other issues with
> > making the site more interactive for the user?
>
> XTile is a not part of the Tacos component library.
>
> Generally speaking, AJAX approaches will make it harder to achieve
> accessibility (ie. I have no idea how screenreaders handle dynamic DOM
> replacements, probably not very well). On the other hand, as long as
> you use it in a conservative fashion where the functionality works
> fine with javascript disabled, you can most likely make things degrade
> in a usable way. The Tacos library in particular works like this
> (http://tacos.sf.net/). You should try some tests with some relevant
> products...
>
> A related note: to me auto-completion on social-security number
> searches sounds like a profoundly bad idea, as far as privacy is
> concerned. Not sure what federal regulations require, but one would
> hope that the requirements are at least as stringent as credit card
> security in ecommerce apps (which I'm familiar with, and which even
> with all the restrictions remains unsecure in many ways :). You
> definitely should not be able to just type in 12* to get all numbers
> starting with that :)
>
> regards,
> viktor
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 508 compliance and tacos components
Posted by sj <my...@gmail.com>.
Hi,
Question abt Xtile. To my understanding, when the user enters a
character, we fire Xtile onKeyUp event (say), a thread starts doing
the query. what if the user types in fast and a second thread is
called before the first returns. This can lead into problems rt? Willl
this become asynchronous? Any thoughts?
t
On 6/21/05, Viktor Szathmary <ph...@gmail.com> wrote:
> On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
> > The company I work for is developing an application for a federal
> > client and I would like to use some of the components from the t-deli
> > site. The one in question is the example(xtile) they have where you
> > type in a textbox and it starts doing the search on the keypresses.
> > The client wants this ability when searching for ssn's. My boss seems
> > to think this won't pass 508 compliance; was just wondering if anyone
> > knows if this would be the case. Will we run across other issues with
> > making the site more interactive for the user?
>
> XTile is a not part of the Tacos component library.
>
> Generally speaking, AJAX approaches will make it harder to achieve
> accessibility (ie. I have no idea how screenreaders handle dynamic DOM
> replacements, probably not very well). On the other hand, as long as
> you use it in a conservative fashion where the functionality works
> fine with javascript disabled, you can most likely make things degrade
> in a usable way. The Tacos library in particular works like this
> (http://tacos.sf.net/). You should try some tests with some relevant
> products...
>
> A related note: to me auto-completion on social-security number
> searches sounds like a profoundly bad idea, as far as privacy is
> concerned. Not sure what federal regulations require, but one would
> hope that the requirements are at least as stringent as credit card
> security in ecommerce apps (which I'm familiar with, and which even
> with all the restrictions remains unsecure in many ways :). You
> definitely should not be able to just type in 12* to get all numbers
> starting with that :)
>
> regards,
> viktor
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: 508 compliance and tacos components
Posted by Viktor Szathmary <ph...@gmail.com>.
On 6/21/05, Jeff Cooper <js...@gmail.com> wrote:
> The company I work for is developing an application for a federal
> client and I would like to use some of the components from the t-deli
> site. The one in question is the example(xtile) they have where you
> type in a textbox and it starts doing the search on the keypresses.
> The client wants this ability when searching for ssn's. My boss seems
> to think this won't pass 508 compliance; was just wondering if anyone
> knows if this would be the case. Will we run across other issues with
> making the site more interactive for the user?
XTile is a not part of the Tacos component library.
Generally speaking, AJAX approaches will make it harder to achieve
accessibility (ie. I have no idea how screenreaders handle dynamic DOM
replacements, probably not very well). On the other hand, as long as
you use it in a conservative fashion where the functionality works
fine with javascript disabled, you can most likely make things degrade
in a usable way. The Tacos library in particular works like this
(http://tacos.sf.net/). You should try some tests with some relevant
products...
A related note: to me auto-completion on social-security number
searches sounds like a profoundly bad idea, as far as privacy is
concerned. Not sure what federal regulations require, but one would
hope that the requirements are at least as stringent as credit card
security in ecommerce apps (which I'm familiar with, and which even
with all the restrictions remains unsecure in many ways :). You
definitely should not be able to just type in 12* to get all numbers
starting with that :)
regards,
viktor
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org