I realize that the issue with Microsoft access and screen readers is a complex topic. Here's the situation. I have a user who used JAWS 14 with a customized database using Access 2010 and things seemed to read well with no problem. The database opened with a main menu and each item read properly when the tab key was pressed. The user recently was migrated to JAWS 15 and pressing the tab key just says the number of the item, followed by the word "button" without reading the prompt or label associated with that button. The prompt creator will not work in this database. Using screen refresh and maximizing the window did not help. The user's theme was set to Dell: I changed it to windows Classic and windows 7 Basic but nothing worked. What is now a bit odd is that loading JAWS 14 produces the same results, where the tab key just says "button" without reading the prompt. We can use the JAWS cursor to read the prompts but I'm curious to know if anyone could suggest other things I could try. Pressing insert-Q verifies that Access 2010 scripts are loaded. Thank you in advance for anything you can suggest.
David Goldfield Computer Technology Instructor 919 Walnut Street 4th Floor Philadelphia, PA 19107 215-627-0600 ext 3277 FAX: 215-922-0692 dgold...@asb.org<mailto:dgold...@asb.org> www.asb.org<http://www.asb.org> Serving Philadelphia's and the nation's blind and visually impaired population since 1874. www.asb.org<http://www.facebook.com/pages/Associated-Services-for-the-Blind/234389409941928> www.asb.org<http://twitter.com/ASBPhiladelphia> For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/
