RE: [flexcoders] Flex Accessibility - TextInput Component

2006-11-07 Thread Andrew Kirkpatrick





A bunch of questions:

What version of JAWS?

Do you have the JAWS scripts installed? (http://www.adobe.com/macromedia/accessibility/features/flex/jaws.html)

Try hitting ins+f5 - is your info in this 
list?

Do you know about forms mode and virtual PC cursor mode in 
JAWS? You will get some different information out of the controls in each 
mode. To enter forms mode, navigate to the textinput and hit enter - jaws 
will say "Forms mode on".

Background info: 
Virtual PC cursor mode is when JAWS navigates through the 
off-screen model that it constructs for its own purposes. when in this 
mode (this is the mode that users are in when they enter a page) JAWS listens to 
the keypresses made by the user, acts on some of them and passes some on to the 
browser/player (this is a bit of a simplification). JAWS uses many 
keystrokes - "f" is used by JAWS to move the virtual focus to the next form 
control, right arrow reads the next character, down arrow reads the next line, 
etc. If a user wants to enter text into a control such as a textInput, or 
use arrow keys to switch the active tab in a tabnavigator, they need to be in 
forms mode.

Forms mode allows user keystrokes to pass through to the 
player/browser. Additional navigation of the content (e.g. reading line by 
line through non-focusable objects) is not possible, and the user's interaction 
model is basically identical to that of a keyboard-only user. 


let me know if this helps,
AWK

Andrew KirkpatrickCorporate Accessibility Engineering 
LeadAdobe Systems

  
  
  From: flexcoders@yahoogroups.com 
  [mailto:[EMAIL PROTECTED] On Behalf Of Mike 
  ShawSent: Monday, November 06, 2006 6:12 PMTo: 
  flexcoders@yahoogroups.comSubject: [flexcoders] Flex Accessibility 
  - TextInput Component
  
  
  
  Hi, we are building a financial calculator app in 
  flex 2 which is required to be accessible. 
  So far we have got through most of the pitfalls 
  except for one. 
  We have a TextInput which due to the visual design 
  is not in a FormItem (so no label). So instead we assign a name or description property to the 
  accessibilityProperties object. The TextInput may or may not be editable. The question is: 
  How do we get Jaws to read the name or description 
  properties. Currently it is only reading the value. I know the properties are set because I can see them using 
  Microsoft's Inspect32. 
  Any help would be much appreciated. 
  Regards, 
  Mike. 
  
__._,_.___





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com








   






  
  
SPONSORED LINKS
  
  
  

Software development tool
  
  
Software development
  
  
Software development services
  
  


Home design software
  
  
Software development company
  

   
  






  
  Your email settings: Individual Email|Traditional 
  Change settings via the Web (Yahoo! ID required) 
  Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured 
   
Visit Your Group 
   |
  
Yahoo! Groups Terms of Use
   |
  
   Unsubscribe 
   
 

  




__,_._,___



RE: [flexcoders] Flex Accessibility - TextInput Component

2006-11-07 Thread Mike Shaw





Hi Andrew,

we are using JAWS 7.1 and have the scripts 
installed.

It doesn't read 
the name out in forms or virtual PC mode.

hitting ins+F5 shows the info in this list and unless you 
can suggest a better option this will have to do. (I presume
that this option is well understood by most JAWS users of 
course. Is this a correct assumption?)

Thanks,

Mike.



From: flexcoders@yahoogroups.com 
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew 
KirkpatrickSent: Tuesday, 7 November 2006 1:45 PMTo: 
flexcoders@yahoogroups.comSubject: RE: [flexcoders] Flex 
Accessibility - TextInput Component



A bunch of questions:

What version of JAWS?

Do you have the JAWS scripts installed? (http://www.adobe.com/macromedia/accessibility/features/flex/jaws.html)

Try hitting ins+f5 - is your info in this 
list?

Do you know about forms mode and virtual PC cursor mode in 
JAWS? You will get some different information out of the controls in each 
mode. To enter forms mode, navigate to the textinput and hit enter - jaws 
will say "Forms mode on".

Background info: 
Virtual PC cursor mode is when JAWS navigates through the 
off-screen model that it constructs for its own purposes. when in this 
mode (this is the mode that users are in when they enter a page) JAWS listens to 
the keypresses made by the user, acts on some of them and passes some on to the 
browser/player (this is a bit of a simplification). JAWS uses many 
keystrokes - "f" is used by JAWS to move the virtual focus to the next form 
control, right arrow reads the next character, down arrow reads the next line, 
etc. If a user wants to enter text into a control such as a textInput, or 
use arrow keys to switch the active tab in a tabnavigator, they need to be in 
forms mode.

Forms mode allows user keystrokes to pass through to the 
player/browser. Additional navigation of the content (e.g. reading line by 
line through non-focusable objects) is not possible, and the user's interaction 
model is basically identical to that of a keyboard-only user. 


let me know if this helps,
AWK

Andrew KirkpatrickCorporate Accessibility Engineering 
LeadAdobe Systems

  
  
  From: [EMAIL PROTECTED]ups.com 
  [mailto:flexcoders@yahoogroups.com] On Behalf Of Mike 
  ShawSent: Monday, November 06, 2006 6:12 PMTo: 
  [EMAIL PROTECTED]ups.comSubject: [flexcoders] Flex 
  Accessibility - TextInput Component
  
  
  
  Hi, we are building a financial calculator app in 
  flex 2 which is required to be accessible. 
  So far we have got through most of the pitfalls 
  except for one. 
  We have a TextInput which due to the visual design 
  is not in a FormItem (so no label). So instead we assign a name or description property to the 
  accessibilityProperties object. The TextInput may or may not be editable. The question is: 
  How do we get Jaws to read the name or description 
  properties. Currently it is only reading the value. I know the properties are set because I can see them using 
  Microsoft's Inspect32. 
  Any help would be much appreciated. 
  Regards, 
  Mike. 
  

__._,_.___





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com








   






  
  
SPONSORED LINKS
  
  
  

Software development tool
  
  
Software development
  
  
Software development services
  
  


Home design software
  
  
Software development company
  

   
  






  
  Your email settings: Individual Email|Traditional 
  Change settings via the Web (Yahoo! ID required) 
  Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured 
   
Visit Your Group 
   |
  
Yahoo! Groups Terms of Use
   |
  
   Unsubscribe 
   
 

  




__,_._,___



RE: [flexcoders] Flex Accessibility - TextInput Component

2006-11-07 Thread Andrew Kirkpatrick





It varies. This does confirm that JAWS is getting the 
information out of the player, I'm not sure why you're only seeing the result 
here without seeing it. Is there an example you can forward to 
me?

Thanks,
AWK

  
  
  From: flexcoders@yahoogroups.com 
  [mailto:[EMAIL PROTECTED] On Behalf Of Mike 
  ShawSent: Tuesday, November 07, 2006 5:15 PMTo: 
  flexcoders@yahoogroups.comSubject: RE: [flexcoders] Flex 
  Accessibility - TextInput Component
  
  Hi Andrew,
  
  we are using JAWS 7.1 and have the scripts 
  installed.
  
  It doesn't read 
  the name out in forms or virtual PC mode.
  
  hitting ins+F5 shows the info in this list and unless you 
  can suggest a better option this will have to do. (I 
  presume
  that this option is well understood by most JAWS users of 
  course. Is this a correct assumption?)
  
  Thanks,
  
  Mike.
  
  
  
  From: flexcoders@yahoogroups.com 
  [mailto:[EMAIL PROTECTED] On Behalf Of Andrew 
  KirkpatrickSent: Tuesday, 7 November 2006 1:45 PMTo: 
  flexcoders@yahoogroups.comSubject: RE: [flexcoders] Flex 
  Accessibility - TextInput Component
  
  
  
  A bunch of questions:
  
  What version of JAWS?
  
  Do you have the JAWS scripts installed? (http://www.adobe.com/macromedia/accessibility/features/flex/jaws.html)
  
  Try hitting ins+f5 - is your info in this 
  list?
  
  Do you know about forms mode and virtual PC cursor mode 
  in JAWS? You will get some different information out of the controls in each 
  mode. To enter forms mode, navigate to the textinput and hit enter - 
  jaws will say "Forms mode on".
  
  Background info: 
  Virtual PC cursor mode is when JAWS navigates through the 
  off-screen model that it constructs for its own purposes. when in this 
  mode (this is the mode that users are in when they enter a page) JAWS listens 
  to the keypresses made by the user, acts on some of them and passes some on to 
  the browser/player (this is a bit of a simplification). JAWS uses 
  many keystrokes - "f" is used by JAWS to move the virtual focus to the next 
  form control, right arrow reads the next character, down arrow reads the next 
  line, etc. If a user wants to enter text into a control such as a 
  textInput, or use arrow keys to switch the active tab in a tabnavigator, they 
  need to be in forms mode.
  
  Forms mode allows user keystrokes to pass through to the 
  player/browser. Additional navigation of the content (e.g. reading line 
  by line through non-focusable objects) is not possible, and the user's 
  interaction model is basically identical to that of a keyboard-only 
  user. 
  
  let me know if this helps,
  AWK
  
  Andrew KirkpatrickCorporate Accessibility Engineering 
  LeadAdobe Systems
  


From: [EMAIL PROTECTED]ups.com 
[mailto:flexcoders@yahoogroups.com] On Behalf Of Mike 
ShawSent: Monday, November 06, 2006 6:12 PMTo: 
[EMAIL PROTECTED]ups.comSubject: [flexcoders] Flex 
Accessibility - TextInput Component



Hi, we are building a financial calculator app in 
flex 2 which is required to be accessible. 
So far we have got through most of the pitfalls 
except for one. 
We have a TextInput which due to the visual 
design is not in a FormItem (so no label). So instead we assign a name or description property to the 
accessibilityProperties object. The TextInput may or may not be editable. The question is: 
How do we get Jaws to read the name or 
description properties. Currently it is only reading the value. 
I know the properties are set because I 
can see them using Microsoft's Inspect32. 
Any help would be much appreciated. 
Regards, 
Mike. 

   
__._,_.___





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com








   






  
  
SPONSORED LINKS
  
  
  

Software development tool
  
  
Software development
  
  
Software development services
  
  


Home design software
  
  
Software development company
  

   
  






  
  Your email settings: Individual Email|Traditional 
  Change settings via the Web (Yahoo! ID required) 
  Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured 
   
Visit Your Group 
   |
  
Yahoo! Groups Terms of Use
   |
  
   Unsubscribe 
   
 

  




__,_._,___