<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Forging The Future &#187; Accessibility</title>
	<atom:link href="http://weblog.ieuc.org/archives/category/technology/accessibility/feed" rel="self" type="application/rss+xml" />
	<link>http://weblog.ieuc.org</link>
	<description>News and Views from the Institute for End User Computing, Inc.</description>
	<lastBuildDate>Fri, 06 Jan 2012 03:08:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Have You Upgraded Your Browser Lately?  ::: An IEUC Website Progress Report</title>
		<link>http://weblog.ieuc.org/archives/632</link>
		<comments>http://weblog.ieuc.org/archives/632#comments</comments>
		<pubDate>Wed, 15 Jun 2011 15:27:35 +0000</pubDate>
		<dc:creator>The IEUC</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Consumer Advocacy]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Webmaster's Log]]></category>

		<guid isPermaLink="false">http://weblog.ieuc.org/?p=632</guid>
		<description><![CDATA[We are hammering away behind the scenes on a major retooling of our website&#8217;s design and source code to embrace HTML 5 and CSS 3. There has been a lot of innovation in the browser space and we are doing our best to take advantage of it. As a result, we won&#8217;t be able to [...]]]></description>
			<content:encoded><![CDATA[<div style="text-align:justify;text-indent:1em;">
<p>We are hammering away behind the scenes on a major retooling of our website&#8217;s design and source code to embrace HTML 5 and CSS 3. There has been a lot of innovation in the browser space and we are doing our best to take advantage of it. As a result, we won&#8217;t be able to maintain our current level of support for older versions of Internet Explorer, but we really aren&#8217;t doing anyone any favors by helping them delay an upgrade to a more capable browser. As always, even if a page doesn&#8217;t look particularly aesthetic in an old browser, you should still be able to read its content. But seriously, why make yourself suffer? Upgrade to a current browser release now, so you&#8217;ll be able to fully enjoy our new site when we roll it out later this Summer!</p>
<p>Remember, current versions of the major browsers are all free and fast downloads for anyone with internet connectivity. For Mac Users, the latest incarnations of Safari, Chrome, and Firefox will serve you well. On Windows you can look forward to an impressive Internet Explorer 9 as well as Chrome and Firefox. Firefox and/or Chrome should already be pre-installed on current Linux distributions. Modern cell phones and tablets generally have mechanisms in place to keep their browsers updated and any new device is apt to provide strong support for emerging web standards.</p>
<p>Keeping any of these programs updated couldn&#8217;t be more painless or important since they are all undergoing very rapid evolution at this time. Each new release is adding new features that will noticeably improve your browsing experience as more sites like this one roll out HTML 5 &#038; CSS 3 based designs.</p>
<p>Of course if you are dealing with a school, library, or corporate setting where you can&#8217;t just install it yourself, remind the IT <strong>Powers That Be</strong>, that running older browsers exposes their organizations to countless security vulnerabilities and reduces your productivity and access to important websites!</p>
<p>If you are a Screen Reader User, the situation is slightly more volatile, since HTML 5 support may take some time to arrive. We are doing our best to use the new features in a manner that won&#8217;t compromise your experience, but it is vital that you contact the developers of your Screen Reader of choice to let them know that support for HTML 5 features like its outline model are important to you. </p>
<p>Remember, your Assistive Technology Vendor is the one in the best position to improve your web surfing experience. It makes no sense to force web developers to delay rolling out support for improved standards that benefit <strong>everyone&#8217;s</strong> usability when a software upgrade on your part can yield a superior web surfing experience to that produced by millions of ill informed attempts to tweak web sites for compatibility with obsolete assistive technologies.</p>
<p>In many respects, today&#8217;s Web Browsers have become just as important a computing platform as the operating systems they run under. Beyond surfing the web, you can now find plugins that extend their capabilities to everything from helping you follow Twitter and Tweak to your friends, to managing the sea of academic citations that go into a Ph.D. Dissertation, to taking some of the pain out of developing web content of your own,  to helping you blow off steam with cleaver in-browser puzzle games.</p>
<p>By allocating a few minutes each week to making sure your web browsers are up to date, you&#8217;ll be doing your part to make the World Wide Web work smoothly and securely while unlocking countless new possibilities!</p>
<p><strong>Upgrade now and surf safely, the Web awaits!</strong>
</div>
]]></content:encoded>
			<wfw:commentRss>http://weblog.ieuc.org/archives/632/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pre-Election Jitters — The Case for Mechanical Voting Machines</title>
		<link>http://weblog.ieuc.org/archives/530</link>
		<comments>http://weblog.ieuc.org/archives/530#comments</comments>
		<pubDate>Mon, 01 Nov 2010 15:37:12 +0000</pubDate>
		<dc:creator>The IEUC</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://weblog.ieuc.org/?p=530</guid>
		<description><![CDATA[Make no mistake, we love computers, especially where they are employed to give a measure of independence to people with disabilities. They are remarkably fluid and can have their behavior changed on the fly possibly without leaving any forensic evidence of their previous configuration. This makes us apprehensive of the potential for computerized election machines [...]]]></description>
			<content:encoded><![CDATA[<div style="text-indent:1em;text-align:justify;">
<p>Make no mistake, we love computers, especially where they are employed to give a measure of independence to people with disabilities.</p>
<p>They are remarkably fluid and can have their behavior changed on the fly possibly without leaving any forensic evidence of their previous configuration.</p>
<p>This makes us apprehensive of the potential for computerized election machines to be tampered with in ways that defy subsequent investigation. Indeed we are deeply troubled by radio reports that some of the new touch screen devices may be pre-selecting candidates of one party rather than presenting voters with a blank slate.</p>
<p>Equally troubling are reports of erroneous instructions on how to use the new voting machines and human factors issues that could lead voters to hit &#8216;enter&#8217; after accidentally entering an over-vote, which would have the effect of disenfranchising them! Likewise, on other machines, there is a simple counter that indicates that some mark was scanned without any feedback for the voter to know that all of his or her ballot selections were picked up in the vote.</p>
<p>Moreover, given the ease with which a technically competent criminally minded election worker might be able to tamper with tomorrow&#8217;s election, we urge you to exercise extreme caution in using whatever configuration of voting device you are confronted with. Also, bring a camera or cell phone in with you if it is permitted so you can <strong>snap a photo to create a record of any screen layout that you think might have been tampered with and immediately raise the alarm with election officials.<br />
</strong><br />
Beyond the sheer cost of replacing our old fashioned voting machines with these new computerized systems — for non-disabled voters — their user interfaces are unduly complicated. Filling in little bubbles with markers will take much longer, be harder for our seniors, and be more stressful for all compared to the ease of pulling a physical lever in older voting machines. Moreover, those older mechanical systems were infinitely more tamper resistant than anything driven by a computer chip.</p>
<p>For those with disabilities we really like the new multi-modal systems and it makes perfect sense to have one of them at each polling place. But for the rest of us, lever based systems with their mechanical interlock to prevent over voting and the direct one-to-one correspondence between lever positions and reliably recorded votes have yet to be matched by the newer designs.</p>
<p><strong>Newer is not always better and adding a computer to the mix doesn&#8217;t necessarily make for a better solution.</strong></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://weblog.ieuc.org/archives/530/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessible Mobile Phone Options for People Who Are Blind, Deaf-Blind, or Have Low Vision</title>
		<link>http://weblog.ieuc.org/archives/516</link>
		<comments>http://weblog.ieuc.org/archives/516#comments</comments>
		<pubDate>Tue, 28 Sep 2010 14:12:04 +0000</pubDate>
		<dc:creator>The IEUC</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://weblog.ieuc.org/?p=516</guid>
		<description><![CDATA[As is often the case for ordinary citizens who don&#8217;t spend their days trolling the Federal Register for notices of pending rule making, we are very late to the party in reporting that the time for input to the Federal Communications Commission on possible government action to make mobile phones accessible to disabled consumers is [...]]]></description>
			<content:encoded><![CDATA[<div style="text-indent:1em;text-align:justify;" >
As is often the case for ordinary citizens who don&#8217;t spend their days trolling the Federal Register for notices of pending rule making, we are very late to the party in reporting that the time for input to the Federal Communications Commission on possible government action to make mobile phones accessible to disabled consumers is nearly closed.</p>
<p>Indeed there are only two days left for End Users to register comments on this issue which was presented as follows:</p>
<blockquote><p>
In this document, the Commission, via the Wireless Telecommunications Bureau and the Consumer and Governmental Affairs Bureau (“the Bureaus”), seeks input from all stakeholders in order to be fully informed on issues raised by consumers and to determine the appropriate next steps to achieve telecommunications access. The Bureaus seek input on the following issues: The wireless phone features and functions in the current marketplace that are not accessible for people who are blind, have vision loss, or are deaf-blind and the extent to which gaps in accessibility are preventing wireless communication access by these populations; the cost and feasibility of technical solutions to achieve wireless accessibility for these populations; reasons why there are not a greater number of wireless phones—particularly among less expensive or moderately-priced handset models—that are accessible to people who are blind or have vision loss; technical obstacles, if any, to making wireless technologies compatible with Braille displays, as well as the cost and feasibility of technical solutions to achieve other forms of compatibility with wireless products and services for people who are deaf-blind; recommendations on the most effective and efficient technical policy solutions for addressing the needs of consumers with vision disabilities, including those who are deaf-blind; and recommendations on actions that the Bureaus or the Commission should take to address the current lack of access. For example, is additional guidance needed on specific access features that should be included in wireless products? Should the Bureaus or the Commission facilitate a dialogue among stakeholders in order to reach a specific agreement to address the accessibility concerns outlined herein?</p></blockquote>
<p>Naturally, the notion that mobile devices need to be fully accessible by those who are both deaf <strong>and</strong> blind probably strikes fear in the hearts of device developers given the tremendous design constraints any such mandate would entail. Whether we like it or not, current devices are designed around touch sensitive flat panels without any tactile controls beyond volume and power on/off. Voice input is a viable way to let the deaf-blind dial, but without dedicated hardware, it is hard to imagine that capability getting them very far. Moreover, even voice dialing will break down in extremely noisy environments and won&#8217;t do a thing for the deaf-blind-mute who are every bit as deserving of accommodation as the merely deaf-blind.</p>
<p>What we don&#8217;t want is to see is some naive attempt to limit technology development to a one-size-fits-all solution or to demand that vendors create in-house solutions for every conceivable permutation of disabilities as a pre-requisite to marketing products to the general public, since such moves would likely hobble innovation by driving good companies out or the market and driving up prices to the point than ever greater numbers of the poor, whether disabled or not, would no longer be able to afford them. An equally unpalatable solution would be yet another tax imposed on phone use to redistribute wealth to the users and developers of accessibility devices.</p>
<p>From both a technological and economic perspective, about the best we can hope to achieve through regulation would be a requirement that handset manufactures provide some sort of well documented I/O Port and/or wireless access interface and software API by which <strong>any</strong> user authorized accessibility device could assume control of the phone to place and receive calls. Then we could give a sizable tax break to companies building on those hooks and let the <strong>free market</strong> find the best forms of accommodation. Phone carriers could also help set up a non-profit entity to carry out pre-competitive accessibility research and channel <strong>voluntary</strong> public donations to subsidize phone purchases and use by the disabled.</p>
<p>That said, the last thing we at the Institute would want to do is to get into proposing legislative fixes since we represent many with varying views. If you want yours to be considered by the FCC, you only have two days left to act by <a href="http://www.federalregister.gov/articles/2010/08/05/2010-19298/accessible-mobile-phone-options-for-people-who-are-blind-deafblind-or-have-low-vision">submitting a formal comment</a>.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://weblog.ieuc.org/archives/516/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Site of the Day — Ajaxian</title>
		<link>http://weblog.ieuc.org/archives/236</link>
		<comments>http://weblog.ieuc.org/archives/236#comments</comments>
		<pubDate>Mon, 11 Jan 2010 15:40:07 +0000</pubDate>
		<dc:creator>The IEUC</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Webmaster's Log]]></category>

		<guid isPermaLink="false">http://weblog.ieuc.org/?p=236</guid>
		<description><![CDATA[If you develop websites or would like to see what technologies go into them, Ajaxian is the site for you. Here you can find up to the minute reports of all the major javascript based libraries and related tools that you can use to take a site to the next level. You&#8217;ll also find discussions [...]]]></description>
			<content:encoded><![CDATA[<p>If you develop websites or would like to see what technologies go into them, <a href="http://ajaxian.com/">Ajaxian</a> is the site for you.</p>
<p>Here you can find up to the minute reports of all the major javascript based libraries and related tools that you can use to take a site to the next level. You&#8217;ll also find discussions of hot web accessibility topics like <a href="http://ajaxian.com/archives/webaim-study-screenreaders-and-javascript-co-exist">yesterday&#8217;s revelation</a> that many screenreader users have javascript enabled — a situation not contemplated by most site designers.</p>
<p>You can also sign up for newsletters, grab podcasts, and find out about the latest conferences and job offers.</p>
<p>The site also features rich indexing by topic in the left sidebar, making it is easy to go back in time and bring yourself up to speed in any area of interest.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblog.ieuc.org/archives/236/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

