RE: Android FruitBasket re-posted
- From: "Ken Perry" <whistler@xxxxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Wed, 19 Jan 2011 07:29:59 -0500
If you have jaws, and you are not in the old forms mode on off stuff. Just try to type the file and path in the edit box before pressing browse. Ken From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James Sent: Wednesday, January 19, 2011 6:49 AM To: programmingblind@xxxxxxxxxxxxx Subject: RE: Android FruitBasket re-posted Hi Ken, I'm unsure why it wouldn't let you just put in the name of the file. I'll do some testing. Thanks for your persistance. If you found any other quirky stuff, just tell me and I'll try to cover it in the tutorial. Jim Jim Homme, Usability Services, Phone: 412-544-1810. Skype: jim.homme Internal recipients, Read my accessibility blog <http://mysites.highmark.com/personal/lidikki/Blog/default.aspx> . Discuss accessibility here <http://collaborate.highmark.com/COP/technical/accessibility/default.aspx> . Accessibility Wiki: Breaking news and accessibility advice <http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%2 0Wiki/Forms/AllPages.aspx> From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Tuesday, January 18, 2011 4:41 PM To: programmingblind@xxxxxxxxxxxxx Subject: Android FruitBasket re-posted OK I got the file to delete and uploaded the other file. So I think everything is fixed on the page now. I even fixed the hyper link in my short description. I was still not able to just put the file in without going to the browse link. Ken _____ This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.