E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 8 (In chronological order)

From: Thorson, Marc
Date: Wed, Nov 06 2013 3:12PM
Subject: Automated Accessibility Testing Recommendations?
No previous message | Next message →

There is interest in our organization to improve the automated accessibility testing we do behind-the-scenes along with our manual testing processes. The WAVE API appears to be a great tool for evaluating static pages, and we are seriously considering it, but I'm also interested in inquiring about other tools in the community that might provide more capabilities for evaluating dynamic pages, for example, recording user input in forms and repeating transactional page flows that could be incorporated into an automated enterprise build process. Any recommendations?

Thanks,
Marc Thorson

----------------------------------------------------------------------
The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.

From: Stanzel, Susan - FSA, Kansas City, MO
Date: Wed, Nov 06 2013 3:59PM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | Next message →

Here at USDA we are acquiring WorldSpace by Deque Systems.

Susie Stanzel

From: lists
Date: Wed, Nov 06 2013 7:19PM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | Next message →

Other alternative could be you can leverage on HTML Code Sniffer [1] and customize as per your needs.

[1] http://squizlabs.github.io/HTML_CodeSniffer/

Regards,
Srinivasu Chakravarthula | PayPal | @VasuTweets
Sent from my iPhone 4S

> On 07-Nov-2013, at 4:29, "Stanzel, Susan - FSA, Kansas City, MO" < = EMAIL ADDRESS REMOVED = > wrote:
>
> Here at USDA we are acquiring WorldSpace by Deque Systems.
>
> Susie Stanzel
>
>

From: Ryan E. Benson
Date: Wed, Nov 06 2013 7:57PM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | Next message →

> evaluating dynamic pages,
Hate to tell you, dynamic pages are really impossible to truly test. See
http://www.karlgroves.com/2013/09/29/some-thoughts-on-automated-web-accessibility-testing/

--
Ryan E. Benson


On Wed, Nov 6, 2013 at 5:12 PM, Thorson, Marc < = EMAIL ADDRESS REMOVED = > wrote:

> There is interest in our organization to improve the automated
> accessibility testing we do behind-the-scenes along with our manual testing
> processes. The WAVE API appears to be a great tool for evaluating static
> pages, and we are seriously considering it, but I'm also interested in
> inquiring about other tools in the community that might provide more
> capabilities for evaluating dynamic pages, for example, recording user
> input in forms and repeating transactional page flows that could be
> incorporated into an automated enterprise build process. Any
> recommendations?
>
> Thanks,
> Marc Thorson
>
> ----------------------------------------------------------------------
> The information contained in this communication may be confidential, is
> intended only for the use of the recipient(s) named above, and may be
> legally privileged. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution, or
> copying of this communication, or any of its contents, is strictly
> prohibited. If you have received this communication in error, please notify
> the sender immediately and destroy or delete the original message and any
> copy of it from your computer system. If you have any questions concerning
> this message, please contact the sender.
> > > >

From: Cameron Cundiff
Date: Wed, Nov 06 2013 8:10PM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | Next message →

Hi Marc

It's possible to perform this kind of testing by defining steps with a web driver like selenium and inserting JavaScript assertions into the pages on visit. For Rails apps there's capybara-accessible https://github.com/Casecommons/capybara-accessible.

> On Nov 6, 2013, at 5:12 PM, "Thorson, Marc" < = EMAIL ADDRESS REMOVED = > wrote:
>
> There is interest in our organization to improve the automated accessibility testing we do behind-the-scenes along with our manual testing processes. The WAVE API appears to be a great tool for evaluating static pages, and we are seriously considering it, but I'm also interested in inquiring about other tools in the community that might provide more capabilities for evaluating dynamic pages, for example, recording user input in forms and repeating transactional page flows that could be incorporated into an automated enterprise build process. Any recommendations?
>
> Thanks,
> Marc Thorson
>
> ----------------------------------------------------------------------
> The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
> > >

From: Will Anderson
Date: Wed, Nov 06 2013 8:15PM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | Next message →

We built a test suite for things that can and could/should be tested in an automated fashion by extending google accessibility Dev tools.

See
http://pivotallabs.com/automated-accessibility-testing-rails/

And I'd be happy to answer questions to get you going. The disclaimer is that it only tests a small portion of what could make a site accessible but it's better than nothing


Sent from my phone. Sorry about any typos or mistakes!

> On Nov 6, 2013, at 5:12 PM, "Thorson, Marc" < = EMAIL ADDRESS REMOVED = > wrote:
>
> There is interest in our organization to improve the automated accessibility testing we do behind-the-scenes along with our manual testing processes. The WAVE API appears to be a great tool for evaluating static pages, and we are seriously considering it, but I'm also interested in inquiring about other tools in the community that might provide more capabilities for evaluating dynamic pages, for example, recording user input in forms and repeating transactional page flows that could be incorporated into an automated enterprise build process. Any recommendations?
>
> Thanks,
> Marc Thorson
>
> ----------------------------------------------------------------------
> The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
> > >

From: Dylan Barrell
Date: Sun, Nov 10 2013 10:09PM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | Next message →

Issues with automated testing are not limited to dynamic pages. The
bottom line is that you will always need some form of manual testing.

That having been said, some automated tools can give you more
automated coverage than others and some will also assist manual
testing.

On Nov 6, 2013, at 9:57 PM, "Ryan E. Benson" < = EMAIL ADDRESS REMOVED = > wrote:

>> evaluating dynamic pages,
> Hate to tell you, dynamic pages are really impossible to truly test. See
> http://www.karlgroves.com/2013/09/29/some-thoughts-on-automated-web-accessibility-testing/
>
> --
> Ryan E. Benson
>
>
>> On Wed, Nov 6, 2013 at 5:12 PM, Thorson, Marc < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> There is interest in our organization to improve the automated
>> accessibility testing we do behind-the-scenes along with our manual testing
>> processes. The WAVE API appears to be a great tool for evaluating static
>> pages, and we are seriously considering it, but I'm also interested in
>> inquiring about other tools in the community that might provide more
>> capabilities for evaluating dynamic pages, for example, recording user
>> input in forms and repeating transactional page flows that could be
>> incorporated into an automated enterprise build process. Any
>> recommendations?
>>
>> Thanks,
>> Marc Thorson
>>
>> ----------------------------------------------------------------------
>> The information contained in this communication may be confidential, is
>> intended only for the use of the recipient(s) named above, and may be
>> legally privileged. If the reader of this message is not the intended
>> recipient, you are hereby notified that any dissemination, distribution, or
>> copying of this communication, or any of its contents, is strictly
>> prohibited. If you have received this communication in error, please notify
>> the sender immediately and destroy or delete the original message and any
>> copy of it from your computer system. If you have any questions concerning
>> this message, please contact the sender.
>> >> >> >>
>

From: Karl Groves
Date: Mon, Nov 11 2013 10:22AM
Subject: Re: Automated Accessibility Testing Recommendations?
← Previous message | No next message

Ryan,

Thanks for linking to my post. I have a number of posts on Accessibility
Testing at http://www.karlgroves.com/category/accessibility-testing/

Its actually possible to do some testing on dynamic pages. Deque's FireEyes
always impressed me with the ability to script an interaction and perform
testing on that interaction, including testing changes to the page's DOM.

One of the primary shortcomings of automated accessibility testing of
JavaScript-driven interaction is that the tool must first be "JavaScript
aware", must know what elements have events bound to them, and must be able
to trigger those events and test the changes that result. From a testing
perspective it would require a ton of heavy lifting to check out every node
to see if it has events bound to it, trigger those events, detect which
nodes have changed and test those changes to make sure the right changes
occurred.

For instance, just the other day I saw a menu that, when opened, allowed
you to traverse through tabbing much like a list of links would. But this
had a role of "menu" and the items each had a role of "menuitem". In this
scenario you should arrow through the options, not tab. Again, all of this
type of stuff *could* be done automatically, but I don't know anyone who is
doing it. Instead, a lot of tools either don't try to do it or say they do
but just don't to it well.

In any case the end result is the same: Manual testing is required no
matter how good the tool is.




On Wed, Nov 6, 2013 at 9:57 PM, Ryan E. Benson < = EMAIL ADDRESS REMOVED = >wrote:

> > evaluating dynamic pages,
> Hate to tell you, dynamic pages are really impossible to truly test. See
>
> http://www.karlgroves.com/2013/09/29/some-thoughts-on-automated-web-accessibility-testing/
>
> --
> Ryan E. Benson
>
>
> On Wed, Nov 6, 2013 at 5:12 PM, Thorson, Marc < = EMAIL ADDRESS REMOVED = > wrote:
>
> > There is interest in our organization to improve the automated
> > accessibility testing we do behind-the-scenes along with our manual
> testing
> > processes. The WAVE API appears to be a great tool for evaluating static
> > pages, and we are seriously considering it, but I'm also interested in
> > inquiring about other tools in the community that might provide more
> > capabilities for evaluating dynamic pages, for example, recording user
> > input in forms and repeating transactional page flows that could be
> > incorporated into an automated enterprise build process. Any
> > recommendations?
> >
> > Thanks,
> > Marc Thorson
> >
> > ----------------------------------------------------------------------
> > The information contained in this communication may be confidential, is
> > intended only for the use of the recipient(s) named above, and may be
> > legally privileged. If the reader of this message is not the intended
> > recipient, you are hereby notified that any dissemination, distribution,
> or
> > copying of this communication, or any of its contents, is strictly
> > prohibited. If you have received this communication in error, please
> notify
> > the sender immediately and destroy or delete the original message and any
> > copy of it from your computer system. If you have any questions
> concerning
> > this message, please contact the sender.
> > > > > > > >
> > > >



--

Karl Groves
www.karlgroves.com
@karlgroves
http://www.linkedin.com/in/karlgroves
Phone: +1 410.541.6829