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

Understood but it does seem very similar to the way that it is done in Visual 
Basic 2005.  In that programming environment you select the control you want to 
make accessible and it has a series of properties layed out in a series of edit 
boxes.  These are things like Accessible Name and Accessible role and you 
simply type in what the text should be for the object then for the accessible 
role you tell it whether it is a button, combo box, slider, etc.  Other 
properties you can control are things like the tab order and whether a control 
is active or not.  It does seem to me after reading that document that 
Dreamweaver or whatever they call it these days, grin, is much the same way.
  ----- Original Message ----- 
  From: Debra Riese 
  To: nvda@xxxxxxxxxxxxx 
  Sent: Wednesday, September 26, 2007 11:10 AM
  Subject: [nvda] Re: Debra's Flash application [was Audacity problem]


  This document does describe what I said in my earlier email, the developer 
has to assign the text in some manner.


  On 9/26/07, John Greer <jpgreer17@xxxxxxxxxxx> wrote: 
    Sorry for the long web address but I think this bit of info can help with
    flash accessibility.
    If the address below doesn't work people can just type creating an 
    accessible flash application into a google search and look through the
    results.
    
http://64.233.169.104/search?q=cache:Rv3TprXLi-oJ:www.adobe.com/resources/accessibility/best_practices/best_practices_acc_flash.pdf+creating+an+accessible+flash+application&hl=en&ct=clnk&cd=2&gl=us

    ----- Original Message -----
    From: "James Teh" <jamie@xxxxxxxxxxx>
    To: <nvda@xxxxxxxxxxxxx>
    Sent: Wednesday, September 26, 2007 7:48 AM 
    Subject: [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
    >

    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: