Monthly Archives: January 2007

Seattle Seahawks’s lost yesterday may have saved the city of New Orleans

Posted on by
Reply

Could you imagine if the Saints had played Chicago for a chance at the superbowl in the Superdome?  New Orleans may have (barely) survived Katrina, but it wouldn’t have survived that football game.

Had the Seahawks won, i would have changed my flight back to seattle for next monday, just so i could say i was in New Orleans when hell froze over. 

Who dat say they are goin’ to beat them saints.  who dat? who dat?

Good luck Saints.  Keep warm in Chicago.

I hate snow

Posted on by
Reply

I think everyone in Seattle can relate to this statement right now.  What is going on?  Is this the 3rd time that we’ve had significant snow?  Like Jimmy Buffet said, "I gotta go where there ain’t any snow.  I gotta go where it’s warm!"

"i’m starting to get pretty good driving in the snow, not freaking out when the car loses traction, sliding down hills, spinning wheels," is a statement i never wanted to be able to say.

At 4pm I saw the dark clouds of doom out the window and ran for the car.  I am so glad that i did.

View original comments

Reintroducing MsaaVerify as an open source project on CodePlex

Posted on by
Reply

Prior to my retirement from accessibility (i’m still retired, btw), i wrote a testing tool for verifying the required MSAA properties needed for Assistive Technology devices, like screen readers, Braille displays, and so forth.  Working on the power toys for the past year has made me want to pick up the little guy again and try to finish all of the ideas i had started.  I’m a huge believer in leading by example, so i’ve been itching to start my own pet project on codeplex .  And of course, this little tool is a natural first choice. 

MsaaVerify Pet Project on CodePlex

Another motivation for reintroducing this tool stems from my overall community work.  I want to better understand community engagement.  It’s a part of a larger plan to understand the term community and everything that goes along with it.

Ways to Participate

Besides the obvious software development aspects of contributing code or bug reports, i could use some help with

  • What is the best way to represent pass / failure in the UI
  • How should I describe what changes need to be made to fix a failure

The more i work on this tool, the more i think that maybe a better home is in FXCop, but i want to get the proof of concept working first, then maybe port to FXCop.  Thoughts?

Current Release – MsaaVerify 1.1 Alpha

  • A rearchitectured baseline prototype with lots and lots of code clean-up
  • Verifies only push buttons and edit boxes
  • Verifies only one object at a time (and with the current design, if a child object is captures, e.g. a listview item, the parent object is the one that’s verified)
  • Updates to the UI from the version on GotDotNet

Future Releases – MsaaVerify 1.1 Beta

Once i have these things implemented, i’ll release a Beta version

  • Verification support for many more standard controls
  • Hopefully, updated UI for the verification results
  • Support for capturing a control based on tab order (needed to verify things like a text box’s name comes from the control that immediately precedes it in tab order)

And Further Out Future Releases

I’ve written a lightweight vision doc on the direction of the tool, some functionality i’d like to add to it, etc.