I’m currently attending the Mozilla 2008 summit in Whistler, British Columbia, Canada. Among all the good sessions we’re having, there are a couple that I definitely want to blog more about over the course of the next few days, but wanted to share a few thoughts right now so we all kind of know what […]Read More Some random thoughts
For those of you on the bleeding edge, namely on the Firefox 3.1a1pre nightly builds, the Friday’s nightly build will include one big new feature in accessibility for 3.1: Text attributes and spell checking support! This means that assistive technologies now have access to the attributes of any text run on a page via the […]Read More Support for text attributes and spell checking is coming in Firefox 3.1!
I know, I know, it’s been a while since I posted my last Easy ARIA tip. But I’m hoping that this one will find you all excited and willing to play with it some more! The problem: You have a form, a contact form, for example, that you want to put some accessible error checking […]Read More Easy ARIA tip #3: aria-invalid and role “alert”
I just upgraded this blog to WordPress 2.6. This version brings with it a number of accessibility enhancements. One thing you might have noticed already is that there is now a default language set. Default English blogs should now always cause screen readers that support language switching to use the English variant of their default […]Read More WordPress 2.6 brings a lot of accessibility improvements!
Today, a post announcing the WebVisum Firefox extension was posted to the mozilla.dev.accessibility newsgroup. The things talked about in this post and on the WebVisum homepage almost sound too good to be true. Among the features are: Ability to tag graphics, form fields, links, and other page elements. While some or all of these features […]Read More Review of the WebVisum Firefox extension
After my first reach out to extension developers, Aaron and I have brainstormed and come up with the 5 most common things you as an extension developer should consider to make your extension more accessible. Here’s what we came up with: Make sure your extension is easily discoverable using the keyboard. A common pattern is […]Read More Extension developers: 5 things to make your extension more accessible