[nvda] Debra's Flash application [was Audacity problem]

Debra Riese wrote:
All that screen readers do is read text, and as long as there is text on the screen it will be read.
This isn't entirely true, especially in the case of a screen reader like NVDA and especially with a technology such as Flash. The easiest way to expose information to screen readers is through the use of accessibility APIs such as MSAA. You would never use MSAA directly; Flash would expose certain information to the accessibility API for the platform in use. However, I'm not sure how Flash determines what information to expose for accessibility.
The method is to be able to code the keys to tab from button to button, have the button function with either a control/enter or two keystrokes on the users keyboard, and to place the text over the button, This is also the limitation of the TTS voice files
Again, I'm not sure how Flash implements accessibility, but you should theoretically be able to have a piece of text which is exposed for accessibility but which is not visible on the screen. You should be able to do this as part of the control itself, rather than having to place a separate text control over the button. At least, this is how it is done in other UI toolkits. Hopefully, Flash is intelligent enough to have something similar... 

Jamie


--
James Teh
Email: jamie@xxxxxxxxxxx
WWW: http://www.jantrid.net/
MSN Messenger: jamie@xxxxxxxxxxx
Jabber: jteh@xxxxxxxxxx
Yahoo: jcs_teh
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda

Other related posts: