<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Paciello Group, The</title>	<link>http://tc.eserver.org/publisher/Paciello_Group,_The</link>
	<description>A listing of works published by Paciello Group, The 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>Paciello Group, The</title>
		<link>http://tc.eserver.org/dir/Paciello_Group,_The</link>
	</image>
	<item>
		<title>Opera&apos;s Lie Blasts Microsoft on IE and Web Standards Support</title>
		<link>http://tc.eserver.org/30629.html</link>
		<guid>http://tc.eserver.org/30629.html</guid>
		<description>Take a look at how Opera&apos;s Hakon Lie publicly blasted Microsoft for it&apos;s lack of support of Web Standards! Lie states. While this isn&apos;t new, I think it&apos;s important for accessibility developers to continue supporting the Mac accessibility community.</description>
	</item>
	<item>
		<title>One Reason Why Section 508 Isn&apos;t Working</title>
		<link>http://tc.eserver.org/30557.html</link>
		<guid>http://tc.eserver.org/30557.html</guid>
		<description>The article underscores one of the key weaknesses in Section 508 today: the lack of self-regulation and commitment to Section 508 by federal agencies. Since Section 508 was released in June 2001, the primary enforcement focus has been on industry&apos;s role and responsibility. The pervasive thinking was that compliance could be better achieved by ensuring that industry designed, developed, and delivered accessible electronic and information technology for agency procurement. And there seems to be merit to this way of thinking. But if federal contracting and procurement officers do not include the 508 requirements as part of their procurement request documentation, industry has no motivation to invest money and resources required to enhance their products for accessibility.</description>
	</item>
	<item>
		<title>Fieldsets, Legends and Screen Readers</title>
		<link>http://tc.eserver.org/30475.html</link>
		<guid>http://tc.eserver.org/30475.html</guid>
		<description>The grouping and labelling of thematically related controls within a form is an important aspect of providing semantic information so users can understand and complete a form successfully. Differences in quality and implementation of support across user agents can hamper some users&apos; ability to benefit from this information. This must not be taken as disincentive to developers, as the benefits of using these elements outweighs the negatives. But it is clear that some assistive technology vendors need to improve implementation of HTML features that enhance accessibility, so their users can gain the most benefit.</description>
	</item>
	<item>
		<title>Providing Context for Ambiguous Link Phrases</title>
		<link>http://tc.eserver.org/30474.html</link>
		<guid>http://tc.eserver.org/30474.html</guid>
		<description>This article demonstrates a technique that allows ambiguous link phrases to be rendered visually in a page, whilst making sense to screen readers, and other non-graphical devices, that might render the links out of context.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Paciello_Group,_The.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>