Tenon.io is a new tool to test web sites against some of the Web Content Accessibility Guidelines criteria. While this does not guarantee the usability of a web site, it gives you an idea of where you may have some problems. Due to its API, it can be integrated into workflows for test automation and […]Read More Quickly check your website for common accessibility problems with tenon.io
Prompted by the recent Microsoft and GW Micro partnership announcement, I took a long overdue look at Microsoft’s Office 365 product offerings. The Home Premium edition not only gives you five installations of full Office Professional versions in your household, Windows and Mac combined, but also the apps for iOS and Android on up to […]Read More WAI-ARIA showcase: Microsoft Office web apps
For a while now, Firefox has had the ability to collect anonymous usage data. Internally, we call this telemetry. Recently, we also started to incorporate statistics about the way the accessibility features of Firefox are being used. Our newest addition to this feature is the collection of data about which screen reader is being used […]Read More Would you like to show us what assistive technology you use Firefox with?
In the nightly Firefox builds, which are already at version 10.0a1, a big refactoring patch was checked in mid of last week that reworks how the accessibility code handles focus changes and setting of the focus and its associated states for screen readers and assistive technologies. Among the improvements this rework introduces are bug fixes […]Read More Reworked accessibility focus handling now in Firefox nightly builds
This already happened a while ago, but I just now found time to blog about it. It was during preparation of Firefox 4.0Beta11 that I found a critical accessibility issue while the second build candidate was already in testing. The issue, documented in Mozilla bug 631160, was that due to a regression introduced in a […]Read More First time driver: A critical fix for Firefox 4.0Beta11
This blog post has to do with the reasons why Firefox 4.0Beta 5 and Beta 6 are totally inaccessible to most, if not all, Windows assistive technologies, and also cause problems with some mouse drivers and such. It all started with Bug 130078, a sequence of digits probably everyone in the Mozilla platform team will […]Read More What’s up with all those windows?
Last week’s work saw quite some code cleanup. Unification of role and finalRole Previously, our nsI*Accessible interfaces exposed both role and finalRole properties. While role returned a preliminary role, finalRole always returned the finally determined role after all markup and ARIA processing had taken place. It turned out that the role was hardly ever used, […]Read More Last week in the “Accessible” module, March 9, 2009
This is the first in an ongoing weekly series where I’ll highlight items that the accessibility team has been working on over the last week. I’ll be reporting on fixed bugs, or will also call out on items that we might appreciate your help on. Since this is the first issue, and my last update […]Read More Last week in the “Accessible” module, March 2, 2009
For those of you following the Firefox/Gecko platform development, or for those interested in helping out, this is a call for participation. If you’re not afraid to get your hands dirty a bit and would like to help the Firefox accessibility team, now would be a good time to get involved! The problem: The code […]Read More Starting an Accessible Name refactor, need your help in testing!
Today, I checked in two changes that allow the unit tests we’ve developed for the accessibility module so far, to run on what we call a staging server. A staging server is a server that simulates production conditions, but isn’t the live thing just yet. It allows us to test new features in build, testing, […]Read More Progress on automated testing for the accessibility module