<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Accessibility&gt;Web Browsers</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Web-Browsers</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Accessibility and Web Browsers in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Web Design&gt;Accessibility&gt;Web Browsers</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Web-Browsers</link>
	</image>
	<item>
		<title>Current Browsers and the User Agent Accessibility Guidelines 1.0</title>
		<link>http://tc.eserver.org/34003.html</link>
		<guid>http://tc.eserver.org/34003.html</guid>
		<description>Any effort on the part of web authors to add accessibility features is rendered useless if browsers and assistive technologies don’t take advantage of them. User agent developers need to ensure that their products support these features and, most crucially, make them available to users in an accessible and obvious manner. What follows is a quick run-down of most of UAAG’s guidelines and checkpoints, annotated with comments, suggestions, personal gripes about current levels of implementation, and wishlists for future browser versions.</description>
	</item>
	<item>
		<title>New Accessibility Features in Internet Explorer 8</title>
		<link>http://tc.eserver.org/33548.html</link>
		<guid>http://tc.eserver.org/33548.html</guid>
		<description>Hi, my name is JP Gonzalez-Castellan and I’m the Accessibility Program Manager for IE8. The IE team has been working towards making IE8 the most accessible browser possible, and we wanted to detail some of the work we’ve done toward this end. In this post I will provide you with some background on Accessibility, I’ll cover new UI features (Caret Browsing, Find on Page, Adaptive Zoom, High DPI, etc) and also platform features (support for ARIA, support for IAccessibleEx, and support for additional WinEvents) that improve the Accessibility of the browser.</description>
	</item>
	<item>
		<title>Web Browsing through Adaptive Technology: A Consumer Information Resource</title>
		<link>http://tc.eserver.org/32268.html</link>
		<guid>http://tc.eserver.org/32268.html</guid>
		<description>The Adaptive Technology Resource Centre (ATRC), University of Toronto coordinated efforts with the Diversity Management Directorate (DMD), Public Services Commission of Canada to systematically evaluate how commercial World Wide Web (WWW) browsers functioned with various types of adaptive technology under different operating systems. The types of adaptive technology examined include screen magnifiers, scanning / switch access systems, alternative keyboards, screen readers, Morse code input devices and voice recognition systems.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Accessibility/Web-Browsers.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>