-
Archives
- May 2012
- April 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- November 2010
- October 2010
- September 2010
- June 2010
- May 2010
- March 2010
- February 2010
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
-
Meta
Monthly Archives: February 2009
NVDA 0.6p3 released, quite some news for Mozilla users!
As you may or may not have read, the NVDA team released NVDA 0.6p3 last night. Below, I’d like to highlight those of the changes that are of special interest to those using Mozilla products such as Firefox or Thunderbird … Continue reading
What should the action name for an indeterminate checkbox be?
As noted in this blog post, we’re currently working on implementing the accessibility for HTML 5 checkboxes that are indeterminate. An indeterminate checkbox is a checkbox that is neither checked nor unchecked, or half-checked if you will. The first stage … Continue reading
Implementing a new feature in Gecko that may have an impact on accessibility? Ping the accessibility team and tell them!
This morning, Jeff Walden pinged me on IRC to ask me whether the new indeterminate DOM property for checkboxes that is being introduced in HTML 5 and which recently landed on Mozilla 1.9.2, has any accessibility implications. I did a … Continue reading
At FOSDEM 2009
I’ll be at FOSDEM in Brussels this weekend. I’ll be at the Mozilla booth or attending sessions in the dev rooms. If you feel like dropping by and talk accessibility, ARIA and such, feel welcomed!
Accessibility fix in 3.0.6
As you may have read already, Firefox 3.0.6 was released on Tuesday. Among the fixes introduced in this version is one for accessibility. It has to do with CaretMoved events and selection changes not being communicated to screen readers properly … Continue reading