<?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>TheAccessPond.com &#187; 1194.22</title>
	<atom:link href="http://theaccesspond.com/category/section-508/119422/feed/" rel="self" type="application/rss+xml" />
	<link>http://theaccesspond.com</link>
	<description>Making Accessibility A Reality!</description>
	<lastBuildDate>Thu, 25 Mar 2010 22:13:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Section 508 1194.22 Guidelines</title>
		<link>http://theaccesspond.com/2009/02/23/section-508-119422-guidelines/</link>
		<comments>http://theaccesspond.com/2009/02/23/section-508-119422-guidelines/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 03:46:56 +0000</pubDate>
		<dc:creator>Mike Adams</dc:creator>
				<category><![CDATA[1194.22]]></category>
		<category><![CDATA[Legal & Policy]]></category>
		<category><![CDATA[section 508]]></category>

		<guid isPermaLink="false">http://theaccesspond.com/?p=82</guid>
		<description><![CDATA[I hadn&#8217;t really thought about it but our posts focus on a lot of specific accessibility issues.  That being said we haven&#8217;t gotten too deep into the conception of accessibility and the guidelines, rules and/or regulations themselves.
I thought maybe it was a good time to put up a few posts that just lay out some [...]]]></description>
			<content:encoded><![CDATA[<p>I hadn&#8217;t really thought about it but our posts focus on a lot of specific accessibility issues.  That being said we haven&#8217;t gotten too deep into the conception of accessibility and the guidelines, rules and/or regulations themselves.</p>
<p>I thought maybe it was a good time to put up a few posts that just lay out some basic information for some of the different sets of criteria that is out there.  Here I&#8217;ll focus on Section 508 and the 1194.22 guidelines that at the very least can be a quick resource for what they are.</p>
<p>A very quick history of Section 508:  The Rehabilitation Act was amended in 1998 and requires Federal agencies to make sure their electronic and information technology accessible.  While that sounds simple enough we can quickly complicate it with the separation of software, telecommunications, web content, etc&#8230; so for now let me just provide a simple list of the web content guidelines also known as 1194.22. </p>
<p><strong>§ 1194.22 Web-based intranet and internet information and applications.</strong></p>
<p>(a) A text equivalent for every non-text element shall be provided (e.g., via &#8220;alt&#8221;, &#8220;longdesc&#8221;, or in element content).</p>
<p>(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.</p>
<p>(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.</p>
<p>(d) Documents shall be organized so they are readable without requiring an associated style sheet.</p>
<p>(e) Redundant text links shall be provided for each active region of a server-side image map.</p>
<p>(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.</p>
<p>(g) Row and column headers shall be identified for data tables.</p>
<p>(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.</p>
<p>(i) Frames shall be titled with text that facilitates frame identification and navigation.</p>
<p>(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.</p>
<p>(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.</p>
<p>(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.</p>
<p>(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).</p>
<p>(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.</p>
<p>(o) A method shall be provided that permits users to skip repetitive navigation links.</p>
<p>(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.</p>
<p>***These can also be found at <a href="http://www.section508.gov">http://www.section508.gov</a>, but don&#8217;t go there looking for too much help as unfortunately the criteria is provided but no real interpretation or example is.***</p>
<p>I hope this helps at least from a simple perspective of what the requirements are, if you have specific questions feel free to sign up, log in and ask away as we&#8217;ll do our best to help you out.</p>
]]></content:encoded>
			<wfw:commentRss>http://theaccesspond.com/2009/02/23/section-508-119422-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
