Software:WebbIE
Please use PROD only on articles. It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Timestamp: 20211029093320 09:33, 29 October 2021 (UTC) Administrators: delete |
| Developer(s) | Alasdair King |
|---|---|
| Stable release | 5.0.0 [1]
/ December 22, 2018 |
| Operating system | Windows |
| Type | Web browser |
| Website | http://www.webbie.org.uk/webbrowser/index.htm |
WebbIE is a freeware web browser designed for screen reader users. It re-presents web pages as text with a caret, allowing users to use their existing screen reader or assistive technology to read it, but is not self-voicing, unlike (for example) Home Page Reader.
History
WebbIE was developed as a student project at the Department of Computation at UMIST. It was first released in 2002 and has been under development and release since. It is often bundled with the LookOUT screen reader and Thunder screen reader.
Technology
WebbIE uses the Microsoft WebBrowser ActiveX control to fetch and parse web pages, and then iterates through the DOM tree to create a text representation of the page. The implications of this include:
- There is a delay between the WebBrowser control rendering the web page for sighted people and presenting the DOM to WebbIE to process. WebbIE can only access the DOM when all images and other embedded content have been rendered, which for some slow or media-heavy sites can take time.
- The text representation is divorced from the underlying DOM, so realtime updates to the DOM (e.g. Ajax writes) may fail to be represented.
References
External links
 |
