[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[SEC508] Announcing WinDig 1.1--open source program for analyzing applications (fwd)
- To: "ISD508WG \(E-mail\)" <ISD508WG@LISTSERV.OPM.GOV>, "'SECT508WG \(E-mail\)" <SECT508WG@LISTSERV.GSA.GOV>, "Sec508 \(E-mail\)" <sec508@trace.wisc.edu>
- Subject: [SEC508] Announcing WinDig 1.1--open source program for analyzing applications (fwd)
- From: "Barrett, Don" <Don.Barrett@ed.gov>
- Date: Tue, 20 Sep 2005 16:00:17 -0400
- List-archive: <http://trace.wisc.edu:8080/mailarchive/sec508/>
- Sender: sec508-admin@trace.wisc.edu
- Thread-index: AcW5XJAqUjlkv3kqRM+oDnLAzhm3pgAA3/ggAS9o/qA=
- Thread-topic: Announcing WinDig 1.1--open source program for analyzing applications (fwd)
FYI, Just came across this program written by a blind programmer which may prove useful in developing/testing. See below. Now available at http://www.empowermentzone.com/wdsetup.exe WinDig is a free, open source utility that digs for as much technical information as it can about a currently running application. The information may be useful in learning how to use an application or knowing how to configure assistive technology to work with it. For example, the information includes a list of all hot keys and menu items. It also includes information about the types of controls in the user interface and the values they currently contain. WinDig may be useful to blind programmers generally, as well as to users or accessibility specialists. It can help you understand the hot keys or controls of a development IDE so that you can use it better. If you write JAWS scripts, the information about control IDs is particularly helpful, since that is often the best way to access a specific control. If you want to develop a program similar to something else you like, WinDig will tell you what controls you need to replicate. Also, the complete WinBatch source code is provided, which may give you techniques for how to do some things in your program.
- Prev by Date: RE: [SEC508] Office Update Problem
- Next by Date: [SEC508] Question about a 508-related job.
- Previous by thread: [SEC508] Office Update Problem
- Next by thread: [SEC508] Question about a 508-related job.
- Index(es):