Sure. A progress bar is a form of status. It inherits properties from status bar.
From that perspective you could consider it live but you don't have to explicitly set live properties. By default the AT knows these live areas are changing but you do not have to set any live properties on them as they have an assumed default behavior which is polite. An screen reader can ignore the status of each unless the user does something special like say ... announce changes to each form of status. Make sense? Rich Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer Jacob Farber <[EMAIL PROTECTED] ronto.ca> To Richard 07/25/08 09:54 AM Schwerdtfeger/Austin/[EMAIL PROTECTED], fluid-work <[email protected]> cc Subject Re: ARIA Progress bars Thanks Rich, Can you help clarify a couple of muddy points then? This map is points progressbar having a parent role of "status" : http://www.w3.org/TR/2008/WD-wai-aria-20080204/rdf_model.png. as does this document: http://www.w3.org/TR/2008/WD-wai-aria-20080204/#progressbar but like you said the link below only says "status" is a related role, with "widget" being the parent... the answer is probably straightforward but I'm a little lost :-\ Thanks Jacob All I could gather from this was that progressbar >> Richard Schwerdtfeger wrote: Hi Jacob, You don't need to set live attributes on a status bar. The ATs know how to deal with progressbars. A progress bar is not a region it is a widget. You don't need to worry about busy either. You need to support valuemax, valuemin, and and valuenow. http://www.w3.org/WAI/PF/aria/#progressbar For any range object you need to provide these values. max annd min are not effective without knowing the current value. An AT often needs to announce the current progress which cannot be computed without the current value. Cheers, Rich Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer Inactive hide details for Jacob Farber <[EMAIL PROTECTED]> Jacob Farber <[EMAIL PROTECTED]> Jacob Farber <jacob.farber @utoronto.ca> Sent by: To fluid-work-bo [EMAIL PROTECTED] fluid-work oject.org <[EMAIL PROTECTED] oject.org> 07/24/08 cc 02:31 PM Subject ARIA Progress bars Hi Everyone, I've been putting together some specs for semantic progress bars, specifically for the Uploader. I've been trying to wrap my head around the ARIA specs re: this patricular live region, and this is what I got as a starting point (as outlined in the JIRA key FLUID-983) Static attributes: • role = progressbar • valuemax = 100 • valuemin = 0 • live = assertive Dynamic attributes: • valuenow (number) • busy (boolean) So far, we've had some good JAWS feedback in FF as it reads out the valuenow attribute appropriately, but what I was wondering is can we put an actual phrase in the attribute? (㧥http://www.w3.org/TR/2008/WD-wai-aria-20080204/#valuenow says no, but is this for certain?) Jacob _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
<<inline: graycol.gif>>
<<inline: pic26080.gif>>
<<inline: ecblank.gif>>
_______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
