<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Accessibility of the product and documentation</title>
		<link>http://kogics.wikidot.com/forum/t-10659967/accessibility-of-the-product-and-documentation</link>
		<description>Posts in the discussion thread &quot;Accessibility of the product and documentation&quot; - I would love to contribute in making the product accessible in general and the documentation in particular.</description>
				<copyright></copyright>
		<lastBuildDate>Sun, 19 Jul 2026 22:18:56 +0000</lastBuildDate>
		
					<item>
				<guid>http://kogics.wikidot.com/forum/t-10659967#post-4187227</guid>
				<title>Accessibility of the product and documentation</title>
				<link>http://kogics.wikidot.com/forum/t-10659967/accessibility-of-the-product-and-documentation#post-4187227</link>
				<description></description>
				<pubDate>Sun, 17 Mar 2019 01:43:07 +0000</pubDate>
				<wikidot:authorName>Rajakavitha Kodhandapani</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>Hi,<br /> Accessibility is a requirement and not just a nice to have feature. Organizations and open source projects alike realize that they could be unintentionally locking people with different abilities out of their products. We need to think about how we program our product and the documentation so that we can optimize for others success.<br /> Business case<br /> 1. Better SEO, and usability<br /> 2. Positive coding practices<br /> 3. Comply with any legal standards or regulations</p> <p>PS: Would like to quote stackoverflow survey One out of every 200 is hard of sight.</p> <p>Please let me know if this is something that interests you.</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>