Infusion 1.3 Accessibility Sprint
colinbdclark at gmail.com
Mon Sep 20 16:45:12 UTC 2010
These dates seem reasonable to me. The testing phase is, as you say, pretty tight, so we'll need to make sure we have all hands on deck for the week of October 21-27.
Do you want to go ahead and create our usual release status page whenever you get a chance?
We might also want to take one more pass through all the bugs and make sure they're grouped and organized in a way that the whole community can follow.
On 2010-09-20, at 10:07 AM, Justin Obara wrote:
> Here is a minor revision to the suggested dates.
> Bug Parade: October 4
> Code Freeze: October 21
> Release date: October 27
> How do those seem?
> I like the idea of having testing start the day after the dev meeting, in case there are any last minute items we need to talk about. However, it will leave us with only 4 days of testing. This may be okay if we have enough help, but we may have to push back the release date a bit if testing doesn't finish on time.
> On 2010-09-17, at 6:38 PM, Colin Clark wrote:
>> Hi everyone,
>> We're currently in the midst of an accessibility sprint for Infusion, which will form a substantial portion of the new features planned for Infusion 1.3. Here's a quick summary of the improvements we're working on:
>> * Refine Inline Edit's use of ARIA to improve its use with a screenreader [Mike and Justin]
>> * For the Progress component, work around ARIA progress role bugs in NVDA [Golam and Justin]
>> * Port Uploader from Flash to HTML 5, substantially improving its overall accessibility [Colin and a buddy]
>> * Provide improved labeling and new, optional interactions for screen reader users in the Reorderer [Michelle and a buddy]
>> * Tidy up and implement additional ARIA roles in our demos [Anastasia and buddies]
>> Infusion 1.3 will also include a number of other exciting features, including:
>> * The first official release of the Infusion Builder
>> * A new Inversion of Control system for the Infusion framework
>> * Transactional support in the ChangeApplier
>> * Improved infrastructure for components that use the Renderer
>> A full list of the issues we're working on for the release is available here:
>> The AEGIS Project has offered to help us with AT-based usability tests in November, so our goal is to wind up the accessibility fixes by the end of October so we have time to prepare demos and instructions to testers. Justin hasn't yet set the exact release date, but here's a suggestion off the top of my head:
>> Bug Parade: October 1
>> Code Freeze: October 20
>> Release date: October 28
>> My rationale for suggesting such a long bug parade phase is that most of the feature-based work for 1.3 is already finished, and we're largely focussed on targeted bug fixes. Thoughts?
Technical Lead, Fluid Project
More information about the fluid-work