![]() For applications that use the GTK+ GUI toolkit, the GAIL module provides default accessibility functionality for stock widgets. "Applications use the GNOME Accessibility Toolkit (ATK) library to provide accessibility and isolate them from the raw AT-SPI. Along those lines here's something that I'm hoping will be of interest. As is probably obvious I'm more of a user than a developer, but since I'm an oldish retired software developer whose skills are vastly out-of-date I hope I can be of some little use in helping to move this 'cause' foward with whatever clumsy research I can provide. ![]() Is there something I'm missing that I can do to enable Narrator to "see" gpodder? If not, is there any chance gpodder might be updated to become visible to Narrator? Given my recently increased reliance on audio podcasts for staying connected with this world this is very disappointing. With gpodder Narrator merely sounds clicks over everything except the title bar - and there the only options for interaction are minimze, restore and close - hardly a robust enough set of controls to do anything meaningful.Īs a person who has recently lost a fair bit of my vision and who has been a long-time user of gpodder I'm disappointed that I can no longer utilizing gpodder. For applications that 'work' with Narrator when I'm moving over the application display Narrator will announce what is displayed on the screen and the interaction options available to me at that location. ![]() I use the touchscreen gesture interface with Narrator. What I do know is that from a user's perspective when I'm running Windows Narrator gpodder is virtually "invisible" to Narrator and hence "invisible" to a visually impaired user utilizing Narrator. I apologize in advance if this is vague, but I'm not sure is required for an application to "work" with screen readers such as Windows Narrator. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |