Comments on: New tools in the making: Accessibility Analysis in Rails http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/ A pragmatic approach to web standards and accessibility Wed, 20 Aug 2008 18:47:36 +0000 http://wordpress.org/?v=2.6 By: Peter Krantz http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/#comment-348 Peter Krantz Thu, 13 Jul 2006 16:03:41 +0000 http://localhost:8888/?p=33#comment-348 <p><strong>Michael</strong>: Hey, it is only four months since my last post! And I have been busy over at <a href="http://peterkrantz.com">peterkrantz.com</a> while trying to raise a baby at the same time.</p> Michael: Hey, it is only four months since my last post! And I have been busy over at peterkrantz.com while trying to raise a baby at the same time.

]]> By: Michael Ward http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/#comment-346 Michael Ward Thu, 13 Jul 2006 13:06:39 +0000 http://localhost:8888/?p=33#comment-346 <p>6 months between posts -good to know you're still here!</p> <p>The kit for RoR should help nicely.</p> 6 months between posts -good to know you’re still here!

The kit for RoR should help nicely.

]]> By: Jeremy Seitz http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/#comment-342 Jeremy Seitz Thu, 06 Jul 2006 07:59:20 +0000 http://localhost:8888/?p=33#comment-342 <p>This sounds awesome, I would love to see this project progress. I am very interested in beta testing -- it will be interesting to see how a site that passes basic accessiblity through automated testing performs in real-world use.</p> This sounds awesome, I would love to see this project progress. I am very interested in beta testing — it will be interesting to see how a site that passes basic accessiblity through automated testing performs in real-world use.

]]> By: Peter Krantz http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/#comment-341 Peter Krantz Mon, 03 Jul 2006 22:21:40 +0000 http://localhost:8888/?p=33#comment-341 <p><strong>Jesper</strong>: I am thinking you could use it both ways. The core component will be a gem which you install. The gem has methods to check arbitrary HTML documents (e.g. stuff you send it from your assert_basic_accessibility in your functional test). This means that it would be very simple to set up a service (which I am planning as well) to check remote sites.</p> Jesper: I am thinking you could use it both ways. The core component will be a gem which you install. The gem has methods to check arbitrary HTML documents (e.g. stuff you send it from your assert_basic_accessibility in your functional test). This means that it would be very simple to set up a service (which I am planning as well) to check remote sites.

]]> By: Jesper Rönn-Jensen (justaddwater.dk) http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/#comment-340 Jesper Rönn-Jensen (justaddwater.dk) Mon, 03 Jul 2006 20:43:25 +0000 http://localhost:8888/?p=33#comment-340 <p>Very nice idea. Cant wait to use it! Let me understand tis correctly: The tool will work as a plugin to a Rails application to test accessiblity on that Rails app?</p> <p>Or is it the other way around: A Rails app that you feed with a URL to evaluate accessibility on one or more websites?</p> Very nice idea. Cant wait to use it! Let me understand tis correctly: The tool will work as a plugin to a Rails application to test accessiblity on that Rails app?

Or is it the other way around: A Rails app that you feed with a URL to evaluate accessibility on one or more websites?

]]> By: Coda Hale http://www.standards-schmandards.com/2006/accessibility-analysis-in-rails/#comment-339 Coda Hale Mon, 03 Jul 2006 18:29:31 +0000 http://localhost:8888/?p=33#comment-339 <p>Oh, super-sweet. That'll mesh nicely with my plugin, <a href="http://blog.codahale.com/rails-plugins/">responsible_markup</a>, which has checks for markup validity, doctype, content type, XML prolog, overly long style attributes, inline Javascript, and others.</p> <p>Moving this level of QA into the functional tests has been great for me. Every time I'm tempted to be lazy with the markup, my tests explode.</p> Oh, super-sweet. That’ll mesh nicely with my plugin, responsible_markup, which has checks for markup validity, doctype, content type, XML prolog, overly long style attributes, inline Javascript, and others.

Moving this level of QA into the functional tests has been great for me. Every time I’m tempted to be lazy with the markup, my tests explode.

]]>