Sorry again, To clarify, I think the most critical issue to deal with is the ALT text for the buttons. Enhancing the a11y for screen readers (especially NVDA), in my opinion can wait - while it could be better it's already pretty accessible. I'll try to find an NVDA user to help us.
Alison On Thu, Dec 10, 2009 at 10:51 PM, Alison Benjamin <[email protected] > wrote: > Good evening, > > Sorry if that wasn't a very meaningful ticket! > > The tasks in the description should definitely get done fog - I think the > only ally issue there is the ALT tag needed for the buttons. > > I just updated my earlier comment. I don't think the screen reader issues I > have highlighted are critical problems, because I think the site is still > usable (especially to JAWS). Perhaps we could create a separate screen > reader ticket to deal with them, and see if a sr user in our community has > any insight. I can't think of a fix right now but will be in tomorrow > afternoon to discuss this further. > > Thanks, > Alison > > > > On Thu, Dec 10, 2009 at 9:32 PM, Colin Clark <[email protected]>wrote: > >> Hi Alison, >> >> I'm doing a quick review of your excellent Builder a11y enhancement >> ticket, trying to determine if it's appropriate for inclusion on the Builder >> bug parade. There's clearly lots of good stuff here, but I'm a bit fuzzy on >> the details. >> >> http://issues.fluidproject.org/browse/FLUID-3424 >> >> Can you elaborate a bit more on the issues you've found, your suggested >> fixes, and how severe the issues are? I'm thinking that might help me split >> these up into a few separate JIRAs and decide how to best schedule them. >> >> Thanks so much, >> >> Colin >> >> --- >> Colin Clark >> Technical Lead, Fluid Project >> Adaptive Technology Resource Centre, University of Toronto >> http://fluidproject.org >> >> >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
