# Ruby Accessibility Analysis Kit (RAAKT) 0.4

**URL:** <https://www.ruby-forum.com/t/ruby-accessibility-analysis-kit-raakt-0-4/65789>\
**Category:** Ruby\
**Created:** [August 21, 2006, 12:53pm UTC](https://www.ruby-forum.com/t/ruby-accessibility-analysis-kit-raakt-0-4/65789 "2006-08-21T12:53:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![peterkemp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/90db22/32.png) [@peterkemp](https://www.ruby-forum.com/u/peterkemp)\
**Post date:** [August 21, 2006, 12:53pm UTC](https://www.ruby-forum.com/t/ruby-accessibility-analysis-kit-raakt-0-4/65789/1 "2006-08-21T12:53:03Z")

</div>

Raakt is a toolkit to find accessibility issues in HTML documents.  
It can be used as part of a an automatic test procedure or as a  
command line tool to evaluate remote web sites. Focus is on finding  
accessibility issues that never should be present (thus, there are no  
“…if applicable”), and that are machine testable (you have to test  
your content some other way).

Changelog for 0.4 is:

- Method to load test document from URL (feed\_url)
- RAAKT is now easy to use in your Rails testing framework (see  
[http://peterkrantz.com/2006/accessibility-in-rails-with-raakt/](http://peterkrantz.com/2006/accessibility-in-rails-with-raakt/))
- Warnings for more formatting elements (patch by Daniel Morrison)

If you want to play with RAAKT without installing the gem I have  
created an online version here:

[http://peterkrantz.com/bacc/](http://peterkrantz.com/bacc/)

This service can be used to test remote web sites like this:

[http://peterkrantz.com/bacc/?url=http://www.ruby-lang.org/en](http://peterkrantz.com/bacc/?url=http://www.ruby-lang.org/en)

For more details see:

[http://raakt.rubyforge.org/](http://raakt.rubyforge.org/)  
[http://rubyforge.org/projects/raakt/](http://rubyforge.org/projects/raakt/)

Kind regards,

Peter K.

---

<div class="post-metadata">

**Author:** ![peterkemp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/90db22/32.png) [@peterkemp](https://www.ruby-forum.com/u/peterkemp)\
**Post date:** [August 21, 2006, 2:05pm UTC](https://www.ruby-forum.com/t/ruby-accessibility-analysis-kit-raakt-0-4/65789/2 "2006-08-21T14:05:13Z")

</div>

On 8/21/06, Peter K. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> [Automated accessibility tests in Ruby on Rails | Peter Krantz](http://peterkrantz.com/2006/accessibility-in-rails-with-raakt/))
> 
> - Warnings for more formatting elements (patch by Daniel Morrison)
> 
> If you want to play with RAAKT without installing the gem I have  
> created an online version here:
> 
> [http://peterkrantz.com/bacc/](http://peterkrantz.com/bacc/)

Hello

[http://peterkrantz.com/bacc/](http://peterkrantz.com/bacc/) itself is broken. It specifies background  
color but not text nor link color. Since it is not defined what the  
text or link color is unless you specify it, the text may render  
invisible.

Note that if you did not set the background it is the users  
responsibility to set text and link color that is visible on their  
selected background. However, you did set the backbround so it is your  
responsibility to set text and link color that is visible on it.

To test your site, try setting the default page colors to something  
different (ie black background, lightgray text, white links) in your  
browser.

I consider sites with broken HTML/styles also inaccessible.

Thanks

Michal