Hi,
Currently the name and description change events as documented in the Core AAM work well as they are, where a focused element will fire such an event when one of these properties change dynamically on that element.
There are scenarios though, which came up today from one of our clients, where this functionality would be good to optionally suppress in some cases. E.G. A textarea field that has an associated character number tooltip that dynamically changes as the user types into that field. In this case, the character count is announced over all characters typed in, and the field itself is meant to provide a means for drafting an essay so there are thousands of characters that can be typed into the field.
In general, the name and description change events should continue to work as they are. However, in cases where it is more accessible to optionally suppress these events, would it be reasonable to allow the explicit setting of aria-live="off" to negate this functionality in limited circumstances? It doesn't seem possible to leave this up to ATs to do this on their end, mainly because this will lead to some things working one way on some operating systems and differently on others.
If agreeable, where should this be filed against, the Core AAM or AccName specs?
Thanks,
Bryan
Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<http://www.levelaccess.com/>