<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Microsoft Messenger for Mac 7.0 Released without Accessibility</title>
	<atom:link href="http://www.lioncourt.com/2008/04/29/microsoft-messenger-for-mac-70-released-without-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lioncourt.com/2008/04/29/microsoft-messenger-for-mac-70-released-without-accessibility/</link>
	<description>...extra! extra!...</description>
	<lastBuildDate>Sun, 05 Sep 2010 19:37:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jake</title>
		<link>http://www.lioncourt.com/2008/04/29/microsoft-messenger-for-mac-70-released-without-accessibility/comment-page-1/#comment-39</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Wed, 30 Apr 2008 15:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=121#comment-39</guid>
		<description>This is far from surprising. Given MS&#039;s past efforts, or lack there of, for accessibility on both their own OS and Mac I would be very surprised to see any accessible software come out from MS.
Remember, MS Office is no more accessible out of the box on Windows then it is on the Mac, what makes it work are the endless tweaks, hooks, and hidden APIs that the Windows screen readers have come to use. The same is true for messenger, for explorer, and indeed for most of Windows itself. Microsoft has done very little when it comes to accessibility itself (Narrator, anyone?), as they know the screen reader developers will do their work for them.
This matters little to the average user, however, and given the political motivations behind the blindness organizations, I agree that this will probably look bad for Apple, though through no fault of their own. The fact that the Windows screen readers use hacks doesn&#039;t matter to most people, what matters is that it works, though in my opinion in a very unstable and reactionary fashion. The fact that Apple has an integrated accessibility infrastructure that Microsoft chose not to employ will not matter. 95% of people believe everything they&#039;re told, be they blind or otherwise, and what they&#039;ll be told is that Voiceover doesn&#039;t work, and they&#039;ll believe it.
About Messenger itself I honestly don&#039;t care much, I didn&#039;t even use it under Windows. I prefer the multi-protocol IM clients, like Trillian on Windows or Adium on OS X. Regardless, this issue is bigger than Messenger, and I&#039;d urge anyone and everyone to write to MS and express your desire for accessibility, though I honestly hold little hope for it from them anymore.</description>
		<content:encoded><![CDATA[<p>This is far from surprising. Given MS&#8217;s past efforts, or lack there of, for accessibility on both their own OS and Mac I would be very surprised to see any accessible software come out from MS.<br />
Remember, MS Office is no more accessible out of the box on Windows then it is on the Mac, what makes it work are the endless tweaks, hooks, and hidden APIs that the Windows screen readers have come to use. The same is true for messenger, for explorer, and indeed for most of Windows itself. Microsoft has done very little when it comes to accessibility itself (Narrator, anyone?), as they know the screen reader developers will do their work for them.<br />
This matters little to the average user, however, and given the political motivations behind the blindness organizations, I agree that this will probably look bad for Apple, though through no fault of their own. The fact that the Windows screen readers use hacks doesn&#8217;t matter to most people, what matters is that it works, though in my opinion in a very unstable and reactionary fashion. The fact that Apple has an integrated accessibility infrastructure that Microsoft chose not to employ will not matter. 95% of people believe everything they&#8217;re told, be they blind or otherwise, and what they&#8217;ll be told is that Voiceover doesn&#8217;t work, and they&#8217;ll believe it.<br />
About Messenger itself I honestly don&#8217;t care much, I didn&#8217;t even use it under Windows. I prefer the multi-protocol IM clients, like Trillian on Windows or Adium on OS X. Regardless, this issue is bigger than Messenger, and I&#8217;d urge anyone and everyone to write to MS and express your desire for accessibility, though I honestly hold little hope for it from them anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlindGeek</title>
		<link>http://www.lioncourt.com/2008/04/29/microsoft-messenger-for-mac-70-released-without-accessibility/comment-page-1/#comment-38</link>
		<dc:creator>BlindGeek</dc:creator>
		<pubDate>Wed, 30 Apr 2008 05:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lioncourt.com/?p=121#comment-38</guid>
		<description>And does this honestly surprise you? I mean, Apple&#039;s Microsoft&#039;s biggest competitor. I&#039;m frankly more surprised that they have a Mac MSN client at all. Besides, think what great fodder it will be once NFB and ACB and other like-minded organizations (Boy, what times we live in when NFB and ACB can be said to be like-minded about anything!) once they&#039;re able to say &quot;Apparently, Voiceover couldn&#039;t even handle the Microsoft Messenger update, which naturally Window-Eyes and Jaws handle fine with its counterpart.&quot;

Of course, if they&#039;re having accessibility issues of their own, this might be a moot point.</description>
		<content:encoded><![CDATA[<p>And does this honestly surprise you? I mean, Apple&#8217;s Microsoft&#8217;s biggest competitor. I&#8217;m frankly more surprised that they have a Mac MSN client at all. Besides, think what great fodder it will be once NFB and ACB and other like-minded organizations (Boy, what times we live in when NFB and ACB can be said to be like-minded about anything!) once they&#8217;re able to say &#8220;Apparently, Voiceover couldn&#8217;t even handle the Microsoft Messenger update, which naturally Window-Eyes and Jaws handle fine with its counterpart.&#8221;</p>
<p>Of course, if they&#8217;re having accessibility issues of their own, this might be a moot point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
