<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.0.4" -->
<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/"
	>

<channel>
	<title>Website QA &#038; Tools from Erigami</title>
	<link>http://www.erigami.com/blog</link>
	<description>News about Truwex web site check tool</description>
	<pubDate>Thu, 06 Mar 2008 10:42:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>
	<language>en</language>
			<item>
		<title>Web Page Redirects and Truwex</title>
		<link>http://www.erigami.com/blog/web-page-redirect/</link>
		<comments>http://www.erigami.com/blog/web-page-redirect/#comments</comments>
		<pubDate>Wed, 22 Aug 2007 11:21:09 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Website compliance and QA</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/web-page-redirect/</guid>
		<description><![CDATA[Web page redirect is an event when a website visitor types one URL in a browser, but a finally displayed page has another URL. This article discusses a role of HTML redirect in website compliance and quality management, and how Truwex can help with that.]]></description>
			<content:encoded><![CDATA[Web page redirect is an event when a website visitor types one URL in a browser, but a finally displayed page has another URL. This article discusses a role of HTML redirect in website compliance and quality management, and how Truwex can help with that.

One URL can be redirected to another web page by a number of ways, all they can be split into two groups: server side and client side URL redirects.
<h3>Server side or HTTP redirect</h3>
Server side redirects are triggered by a web server. A web server responds on a user URL request returning another URL and redirect response code in the HTTP header. Server side redirect codes are defined in the <a target="_blank" href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3">HTTP protocol</a>. The most popular codes are:
<ul>
	<li>301, a web page is moved permanently</li>
	<li>302, a web page is moved temporarily</li>
</ul>
301 redirect is a correct way to forward visitors to another web page. A website visitor can not distinguish 301 and 302 redirects, however the search engines can. A search engine assigns 301-redirected web page with the target page. All external hyperlinks are assigned to the target page as well. It increases the target page rankings in search engines, especially if the both pages share the same topic.

On a Linux system a 301 redirect is created by placing the file with name &#8220;.htaccess&#8221; on a web server. For example, <a href="http://www.truwex.com/">http://www.truwex.com/</a> is 301-redirected to <a href="http://www.erigami.com/truwex/">http://www.erigami.com/truwex/</a>. The .htaccess file is placed in the truwex.com web site root folder with the following content:

Redirect 301 / <a href="http://www.erigami.com/truwex/">http://www.erigami.com/truwex/</a>

Where:
<ul>
	<li>&#8220;Redirect&#8221; is a command to Apache web server</li>
	<li>&#8220;301&#8243; redirect HTTP code</li>
	<li>&#8220;/&#8221; is a path on the local web server to forward. In our case &#8220;/&#8221; means all files on the truwex.com will be redirected. This parameter could be a file name. &#8220;/index.html&#8221;, for inctance</li>
	<li>&#8220;<a href="http://www.erigami.com/truwex/">http://www.erigami.com/truwex/</a>&#8221; is a full target URL</li>
</ul>
If we check <a href="http://www.truwex.com/">http://www.truwex.com/</a> by <a href="http://checkwebsite.erigami.com/accessibility.html">Truwex Online Tool</a>, it shows the original URL is redirected to <a href="http://www.erigami.com/truwex/">http://www.erigami.com/truwex/</a>. Web page Inventory tab contains information about the redirect.

<img alt="Truwex tracks 301 redirects" title="Truwex tracks 301 redirects" src="http://www.erigami.com/blog-images/301-redirect.png" />
<h3>Client side or browser redirect</h3>
Client side redirect is triggered in a user browser. The most popular methods are: meta refresh redirect and JavaScript redirect.

Meta refresh example:
&lt;meta http-equiv=&#8221;Refresh&#8221; content=&#8221;0; url=http://www.target-url.com/&#8221; /&gt;

The browser redirects are often used by black-hut SEOs (Search Engine Optimizers). This technique is known as doorway. A web page with a set of keywords is placed on a domain with high authority, sometimes by using hacker methods. A search engine shows this web page high in rankings. When a user visits this page, it is automatically redirected to another site. The doorways do not live long now, because search engines detect and remove them from index. However they can damage reputation of good websites.

Client side redirects can not be recommended for corporate content websites. However they may be used in web applications.
<h3>How Redirects improve a Web Site</h3>
<h4>Easy to remember URLs for marketing</h4>
For example, <a href="http://microsoft.com/sqlserver/">http://microsoft.com/sqlserver/</a> is easy to remember and relates to the SQL Server product. Many users type it in their browsers to visit SQL Server website. Microsoft redirects this URL to the actual SQL Server home page.

<img alt="Truwex tracks multi-step redirects" title="Truwex tracks multi-step redirects" src="http://www.erigami.com/blog-images/redirect-ms.png" />
<h4>Integrate several domains into one website</h4>
This situation is common after company merges and acquisitions. An acquired website domain is a very important asset and should be integrated into a corporate web presence. If a company plans websites integration, the acquired domain should be 301 redirected to a sub-domain or to a folder of a corporate website. It is a good idea to keep the original domain name as a sub-domain or a folder name. The domain web pages should be moved to a corporate server. The search engine will notice the domain redirection and forward web traffic to a new location.
<h4>Keep external links for search engines</h4>
Every incoming link from external website is an asset. If a web page with many incoming links is deleted, the power of external links just dies with the page. The correct way is to 301-redirect it to another page with similar content.
<h4>Avoid broken links from partner websites and user bookmarks.</h4>
The corporate websites link to each other. For example, resellers link to vendors&#8217; product pages. When a product is discontinued by a vendor, a website administrator may remove a product web page. It may produce a number of broken links not only on own website, but also on the partner sites. The correct approach is setting a permanent 301 redirect to an alternative web page or to a home page of discontinued products every time when a valuable page is deleted from a website.
<h4>Avoid duplicated web pages.</h4>
Duplicated web pages is major issue related to search engines. If a web site contains two pages with the same content,  a search engine must choose one in a response to a user search request. Many pages with the same content reduce a website value for search engines. A good solution is using 301 redirects to forward web page copies to the original page. For example, if a website home page exists in two forms: <a href="http://www.homepage.com/">http://www.homepage.com/</a> and <a href="http://www.homepage.com/main.html">www.homepage.com/main.html</a>, it is reasonable to 301-redirect one URL to another.
<h3>Redirect issues</h3>
<ul>
	<li>Redirect to a third party website may be an issue. In this case the redirect works as a hidden hyperlink, but it is more difficult to track.</li>
	<li>Client side redirects are not honored by search engines.</li>
	<li>A user can disable a client side redirection in a browser.</li>
	<li>Multi-step redirects. One redirect may point to another, in this case a user request will be redirected several times to reach the target page. A missing chain in this redirect sequence leads to a broken link. The multi-step redirects should be avoided to simplify website management.</li>
</ul>
<h3>How Truwex tracks redirects</h3>
Truwex loads web pages to Internet Explorer browser instance. If a final web page URL is different from the original one, a web page was redirected. Truwex tracks HTTP headers and records status codes for a web page. 301, 302 and other 3xx codes mean server side redirect. Truwex also tracks IE BeforeNavigate browser event. In case this event is detected, Truwex records a client side redirect. Truwex reports redirects on a web page level as server side, client side, and multi-step redirects. It also builds a table with a list of all redirects on a website.

<img alt="Website redirect table in Truwex" title="Website redirect table in Truwex" src="http://www.erigami.com/blog-images/redirects.png" />
<h3>Other interesting reading on redirects</h3>
The article with many redirect methods explained: <a href="http://www.stevenhargrove.com/redirect-web-pages/">http://www.stevenhargrove.com/redirect-web-pages/</a>

Wikipedia article on redirects: <a href="http://en.wikipedia.org/wiki/URL_redirection">http://en.wikipedia.org/wiki/URL_redirection</a>]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/web-page-redirect/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Publications and User Testimonials about Truwex</title>
		<link>http://www.erigami.com/blog/truwex-testimonials/</link>
		<comments>http://www.erigami.com/blog/truwex-testimonials/#comments</comments>
		<pubDate>Wed, 16 May 2007 14:01:35 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Truwex News</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/truwex-testimonials/</guid>
		<description><![CDATA[Truwex has been featured on many blogs and received positive feedback from many users. Read what the others say about Truwex...]]></description>
			<content:encoded><![CDATA[<h3>Blog Posts About Truwex Online Tool</h3>
<p><a href="http://accessites.org/site/2007/03/truwex-a-new-accessibility-tester/"><strong>Accessites by Mike Cherim</strong></a></p>
<p>“It’s pretty impressive, so much so that we’ve added to our Resources Page line-up of testing tools… One tab, called “Map” provides a visual of the page with an arrow pointing out the specific culprit. No more counting lines trying to figure out what the heck the tester is talking about — very nice.”</p>
<p><a href="http://www.456bereastreet.com/archive/200703/truwex_online_an_accessibility_and_quality_validator/"><strong>456 Berea street by Roger Johansson</strong></a></p>
<p>“The major difference is that Truwex checks the generated source, not just the raw HTML source. That means checking all the ugly HTML that gets injected into the page by JavaScript. Like the Google Ads on this site.”</p>
<p><a href="http://wai.phpmagazine.net/2007/03/truwex_online_more_than_an_acc.html"><strong>Online PHP Magazine</strong></a></p>
<p>“Truwex Online 2.0 is an excellent accessibility validation tool …, which aims to create a very complete report on Section 508 and WCAG Accessibility, Privacy, and website Quality… Best of all is the map view, which show you a list of issues found on the sidebar and when you click on every issue it will be highlighted on the website.“</p>
<p><strong><a href="http://www.webmasterlibre.com/2007/03/29/truwex-online-validando-la-calidad-de-tus-sitios/">In Spanish by Alma Fernández</a></strong></p>
<p><strong><a href="http://horaciosoares.blogspot.com/2007/03/truwex-online-um-validador-de.html">In Portuguese by Horácio Pastor Soares</a></strong></p>
<p><strong><a href="http://www.bakou.net/index.php/02/03/2007/truwex-online-2-outil-pour-tester-l-accessibilite-de-vos-sites-web/">In French</a></strong></p>
<h3>Truwex User Testimonials</h3>
<p>“A very impressive and free automated accessibility checking tool. In addition to the usual text display of issues with links to the relevant accessibility standards, it displays the checked page with highlighted areas for each of the reported issues.”<br />
- <a href="http://www.sitepoint.com/blogs/2007/03/07/news-wire-cracker-adds-backdoor-to-wordpress/">Kevin Yank</a>, SitePoint.com</p>
<p>“It offers much finer-grained accessibility testing than anything I&#8217;ve used up to this point. I was able to find some nagging accessibility issues with my own site and will refer to it with all new development going forward.”<br />
- Trevor Pierce</p>
<p>“I have my favourites for testing my pages, number one on my list is &#8220;Truwex Online 2.0 beta, Section 508 and WCAG Accessibility, Privacy, Quality validation Tool&#8221;, it has a long name but provides an excellent report and is free. Truwex even displays an image of your page and can show you where your errors are taking place, this is very handy.”<br />
- <a href="http://www.adamskee.com/">Adam Piro</a></p>
<p>“Fascinating. Helped me catch a possible color contrast problem that I wouldn’t have ever thought of.”<br />
- <a href="http://www.elainenelson.org">Elaine Nelson</a></p>
<p>“I like the analysis of how much text can be read by a screen reader within 90 seconds. That’s a very different way of looking at page structure and I’m already considering making changes to a page that I put through Truwex on the basis of this report. Definitely a very useful tool and one I’ll be using in the future.”<br />
- <a href="http://www.blackwidows.co.uk">Mel Pedley</a></p>
<p>“Just when I had my XHTML and CSS validating, and WebXact saying my site was valid Priority 3, I just had to go and test it with this new tool. Geesh, I am humbled again. Now I gotta get back to work! Seriously, looks like a pretty comprehensive tool.”<br />
- <a href="http://www.stoneycreekwebdesign.com/">David Zemens</a></p>
<p>&#8220;Great tool! I used it to quickly solve some small issues with my own site. It&#8217;s also nice that it detects things like the lack of a privacy page. I typically use W3C&#8217;s validator to check the code and accessibility, but this goes into even more detail.&#8221;<br />
- <a href="http://www.tedgoas.com/">Ted Goas</a></p>
<p>“A great tool to check the accessibility of your website. I&#8217;m not talking about stuff that you find on usual websites that claim to provide results. This one really goes deep.”<br />
- <a href="http://www.roscripts.com/Top_developer_tools_of_the_month-132.html">Romeo Mihalcea</a>
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/truwex-testimonials/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>New in Truwex 2.0 (updated)</title>
		<link>http://www.erigami.com/blog/truwex-2-0-new/</link>
		<comments>http://www.erigami.com/blog/truwex-2-0-new/#comments</comments>
		<pubDate>Fri, 04 May 2007 10:53:05 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Truwex News</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/truwex-2-0-beta/</guid>
		<description><![CDATA[We are pleased to announce the second version of Truwex! It features new exciting functionality and many improvements.]]></description>
			<content:encoded><![CDATA[<p>With the second release Truwex software product received a set of exciting new features. Web accessibility validation is even more detailed now. New reports deliver detailed data about websites. Truwex 2.0 connects to search engines APIs and receives website information from external sources. Scan speed is up to 50% higher. Truwex 2.0 consumes much less database disk space. Many bugs were fixed. We appreciate the community members, who tried Truwex and provided their feedback.</p>
<p><a href="http://www.erigami.com/download.html">Download Truwex 2.0 trial</a> version.</p>
<h3>Web accessibility validation module updated</h3>
<p>The Accessibility module was improved: new issues and many manual checks (warnings) were introduced into Truwex to cover all Section 508 and WCAG 1.0 priority 1 and 2 requirements as far as possible.Luminosity contrast formula was updated to comply with the latest WCAG 2.0 guidelines. Many bugs were fixed according to user feedback.</p>
<h3>Website redirects tracking</h3>
<p>Truwex 2.0 detects all types of redirects on a website. Truwex considers a web page as redirected when it opens one URL, but a browser displays another URL. Truwex detects two types of redirects: server side and client side.</p>
<p><em>Server side redirect  </em>is a correct way to inform website visitors (including search engines) that a web page is moved to another location. The most popular redirect codes are: 301 - Moved permanently and 302 – Moved temporarily.</p>
<p><em>Client side redirect  </em>happens in a user’s browser. It is executed by dynamic functionality like a JavaScript. The client side redirect is not transparent for search engines. It is used often by web sites to forward internet users onto a web page they do not expect, sometimes pointing to spyware or other malware. Client side redirects are not recommended for moving users to different content.</p>
<p>Truwex also reports multi-step redirects, when the target URL is reached through a number of redirects. Redirects information is available in the Inventory section (Websites &#038; Reporting > My Websites &#038; Results, select any task’s report > Inventory) and in issues from the SEO issues group.</p>
<p><img alt="redirect table in Truwex" title="redirect table in Truwex" src="http://www.erigami.com/blog-images/redirects.png" /></p>
<h3>Website inventory reports are completely redeveloped</h3>
<p>The new <em>Key Pages Report</em> gives an idea, which pages are the most important on a website. It lists all web pages from a website by their depth and by their internal and external incoming links. The number of incoming links is collected from the Yahoo search engine API. The report is available at: Websites &#038; Reporting > My Websites &#038; Results, select any task’s report > Inventory page.</p>
<p><img alt="Key pages from a website by internal and external linking" title="Key pages from a website by internal and external linking" src="http://www.erigami.com/blog-images/key-pages.png" /></p>
<p>The new <em>Linked Domains Report</em> summarizes all domains used in website’s hyperlinks. This report helps to identify the direction of external links. The report is available at: Websites &#038; Reporting > My Websites &#038; Results, select any task’s report > Inventory.</p>
<p><img alt="the list od domains, linked from a website" title="the list od domains, linked from a website" src="http://www.erigami.com/blog-images/domains.png" /></p>
<p>Other reports:<br />
• Broken and Suspicious Links report lists all broken hyperlinks and ones, which could be broken, found on a website&#8217;s pages.<br />
• Website Forms Summary report.<br />
• Cookies Report lists all cookies found on a website. Cookie data include cookie’s domain, path, is cookie persistent or session, is it third- or first-party, cookie name and value.<br />
• Web Beacons Report lists all third party objects found on a website. It helps with verifying web analytics solutions and third party content on a web site.<br />
• Pages with Frames report lists all pages with frames along with frame data such as frame name, title, source URL.</p>
<h3>Retrofit workload estimate</h3>
<p>Truwex 2.0 features a new report which help web developers evaluate their website improvement workload. The more bugs per page a website has, the more efforts it takes to redevelop. This report shows the number of pages with 0, 1, 2, 3, and more bugs per page on a chart. The report is available as all issues summary for the entire website (select in the Truwex menu: Websites &#038; Reporting > My Websites &#038; Results, select any task’s report > Home), and separately for accessibility, privacy and other issue categories (Websites &#038; Reporting > My Websites &#038; Results, select any task’s report > Issues, then expand “Issue charts” section).</p>
<p><img alt="Truwex chart shows pages and number on issues on them " title="Truwex chart shows pages and number on issues on them " src="http://www.erigami.com/blog-images/workload.png" /></p>
<h3>Website compliance for top pages</h3>
<p>If you plan to redevelop a website, it is practical to start from the top level pages. Truwex 2.0 shows compliance on 1, 2, and 3 levels deep in your website. This functionality helps to prioritize web developers’ work. If a “Depth 0-3” selected, the issue report is updated to show bugs detected only on web pages with depth up to 3. The depth 3 means a web page can be reached in three clicks from a home page. The charts along with the issues table are updated when the depth level changes (Websites &#038; Reporting > My Websites &#038; Results, select any task’s report > Issues page).</p>
<p><img alt="Truwex updates report depends on page depth selected" title="Truwex updates report depends on page depth selected" src="http://www.erigami.com/blog-images/depth.png" /></p>
<h3>Issues and warnings</h3>
<p>Truwex 2.0 classifies all website quality issues as errors or warnings. The errors are considered to be non-compliance problems to be fixed. Warnings just inform about possible problems. Errors and warnings are handled separately in all reports and statistics. A user can change status of every issue according to website’s standards.</p>
<p><img alt="Every issue can be assigned warninig or error status" title="Every issue can be assigned warninig or error status" src="http://www.erigami.com/blog-images/error-warning.png" /></p>
<h3>Search Engine Optimization</h3>
<p>Truwex 2.0 includes a number of validations to improve website visibility in search engines. The most important parameter is web page indexing by a search engine.</p>
<p>SEO validations in Truwex 2.0 include: • Indexed and unindexed pages by Yahoo and MSN • Incoming links by Yahoo • Duplicated pages detection on a website • Server Side and multi-step Redirects tracking • Client side dynamic redirects tracking to internal and external pages. • Meta data validation for duplicated and long HTML titles and descriptions • Robots.txt file analyses • Detection of links to websites which distribute spyware and malware</p>
<h3>Improved usability</h3>
<p>We try to make Truwex interface easier to use and the reports simpler to understand.<br />
• Now a user can easily select specific accessibility standard to validate: Section 508, or WCAG 1.0 Priority 1 or Priority 1 and 2 issues; or to enable or disable accessibility warnings (manual checks).<br />
• Web page properties were improved and linked to the visual Map report.<br />
• The visualization Map has an option to select all issues of a single type.<br />
• All reports have headers.<br />
• Some reports, as broken links, received additional data to make them more explanatory.</p>
<h3>Login to Web Forms</h3>
<p>Truwex checks password protected web applications with login pages. It executes JavaScript every visit on defined login page, and then keeps the authentication session during website scan.</p>
<p><img alt="Authentication to password protected web sites with login page" title="Authentication to password protected web sites with login page" src="http://www.erigami.com/blog-images/script-login.png" /></p>
<p>Using custom modules Truwex go though complex login processes, like RSA banking authentication.</p>
<h3>About Truwex</h3>
<p>Truwex 2.0 is a software product, which helps corporate users and web development agencies with creating high quality and compliant websites. Truwex uses an Internet Explorer browser to load and validate web pages. It means a level of accuracy that can’t be achieved with other tools. Truwex Results Visualization increases web developer productivity, a key success factor in large scale website retrofitting projects. Scalable Reporting delivers measurable results to management, website owners, and developers. Truwex validates the following web standards:<br />
• Web Accessibility: US ADA Section 508, W3C WGAG 1.0 and the standards based on it as UK DDA PAS78, Germany BITV<br />
• Web site quality: broken links, JavaScript errors<br />
• Online privacy rules COPPA, PII, privacy policy, cookies, web analytics usage, third party content<br />
• Website Search compliance and visibility in search engines.</p>
<p><a href="http://www.erigami.com/download.html">Download Truwex 2.0 beta trial</a> version.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/truwex-2-0-new/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>New functionality in Truwex Online Validation Tool.</title>
		<link>http://www.erigami.com/blog/new-truwex-online-tool/</link>
		<comments>http://www.erigami.com/blog/new-truwex-online-tool/#comments</comments>
		<pubDate>Wed, 21 Feb 2007 15:59:28 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Truwex News</category>
	<category>Web Accessibility</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/new-truwex-online-tool/</guid>
		<description><![CDATA[We are presenting a new updated version of the Truwex Validation Tool. Our main desire is to make it convenient for users. This Tool will be a part of a new release of Truwex product, version 2.0 due in the end of March, 2007. We are happy to hear your feedback to improve Truwex for your needs. ]]></description>
			<content:encoded><![CDATA[<p>We are presenting a new updated version of the <a href="http://checkwebsite.erigami.com/accessibility.html">Truwex Online Validation Tool</a>. Our main desire is to make it convenient for users. This Tool will be a part of a new release of Truwex product, version 2.0 due in the end of March, 2007. We are happy to hear your feedback to improve Truwex for your needs.</p>
<h3>Home Page Accessibility Selectors</h3>
<p>Truwex validation results presentation was improved to better display a web page compliance with two most common accessibility standards: the US Section 508 of rehabilitation act and W3C WCAG, version 1. A user can select a web accessibility standard to validate: (1) Section 508 or WCAG Priorities 1 and 2. Accessibility checkbox (2)  triggers all accessibility checks.. Report warnings checkbox (3) enables warnings for manual inspection. It can be disabled to work only with automatically detected issues.</p>
<p><img alt="Truwex Online home page, Section 508, WCAG checkboxes" title="Truwex Online home page, Section 508, WCAG checkboxes" src="/blog-images/truwex-home.png" /></p>
<p>The validation results page now displays compliance summary on all checks. The first column (1) reports a web page status on automatic checks. The second column (2) shows number of detected issues and warnings for manual inspection.</p>
<p><img alt="Truwex online validation results, compliance summary" title="Truwex online validation results, compliance summary" src="/blog-images/validation-results.png" /></p>
<p>Truwex validates other accessibility issues (beyond the Section 508 and WCAG priorities 1, 2) and points for manual checks. To manage them expand Accessibility category.</p>
<h3>WCAG 2.0 Luminosity Contrast Formula</h3>
<p>Truwex automatically validates text/background color contrast and brightness on web pages using WCAG 1.0 formula and <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/Overview.html#visual-audio-contrast-contrast">WCAG 2.0 luminosity contrast formula</a>. Comparing results of WCAG 1 and 2 formulas, we discovered that Erigami.com website is  compliant with the WCAG 1 requirement. However not all color/background combinations fit the WCAG 2 requirement!</p>
<p><img alt="sample of not contrast text" title="sample of not contrast text" src="/blog-images/wcag2-contrast.png" /></p>
<p>However there are color/background combinations, which are compliant with WCAG 2.0 but not compliant with WCAG 1.</p>
<h3>Improved Web Page Map</h3>
<p>Web page Map displays issues on a web page screenshot. We upgraded Web Page Map functionality to make the tool more user friendly:<br />
• The Issue tab provides links (1) to select eligible issues and warnings on Map.<br />
• New “All” option (2) highlights all issues of the same type on a web page map.<br />
• All Issues and Warnings on the left pane are sorted according to the tool home page order.</p>
<p><img alt="Truwex web page map screenshot" title="Truwex web page map screenshot" src="/blog-images/truwex-map.png" /></p>
<h3>New type of validation result: Warnings.</h3>
<p>The new Truwex Online Tool includes Warnings, points for manual checks. All validation checks are separated now into Errors and Warnings. It is hard coded in the Online version. However Truwex product version 2.0 will provide a choice (1): every quality check can be assigned Error or Warning status. That helps to prioritize action items.</p>
<p><img alt="Truwex issue warnings selector" title="Truwex issue warnings selector" src="/blog-images/issue-warning.png" /></p>
<h3>Thank you for the feedback!</h3>
<p>We express our respect to <a href="http://tosg.org.uk/">Cecil Ward</a>, who provided very useful feedback for Truwex. We incorporated it into the new Truwex version.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/new-truwex-online-tool/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Meet Erigami at the Innovation &#038; Investment Forum in Northern Virginia, March 27-28, 2007.</title>
		<link>http://www.erigami.com/blog/virginia-forum/</link>
		<comments>http://www.erigami.com/blog/virginia-forum/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 18:13:25 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Partnership</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/virginia-forum/</guid>
		<description><![CDATA[Erigami will present our website quality and compliance product Truwex to US investors, companies and entrepreneurs at The Innovation &#038; Investment Forum in Northern Virginia.
Northern Virginia area businesses will preview new market-ready technologies from 12 of the leading technology companies from Russia, Ukraine and other Eurasian countries. These companies and their projects were selected from [...]]]></description>
			<content:encoded><![CDATA[<p>Erigami will present our website quality and compliance product Truwex to US investors, companies and entrepreneurs at <a href="http://www.innovationforums.org/virginia/">The Innovation &#038; Investment Forum in Northern Virginia</a>.</p>
<p>Northern Virginia area businesses will preview new market-ready technologies from 12 of the leading technology companies from Russia, Ukraine and other Eurasian countries. These companies and their projects were selected from many others through open competition. The Innovation Forum in Northern Virginia is an opportunity for inventors and local businesses to enter into mutually beneficial collaborations that will stimulate growth for all involved.</p>
<p>The Forum is organized by the <a href="http://www.crdf.org/">U.S. Civilian Research &#038; Development Foundation (CRDF)</a>. The Forum is co-sponsored by the CRDF, the <a href="http://www.nvtc.org">Northern Virginia Technology Council (NVTC)</a> and the <a href="http://www.fasie.ru/eng/">Russian Foundation for Assistance for Small Innovative Enterprises (FASIE)</a>.</p>
<p>If you are interested in investment or cooperation with Erigami, come to the Northern Virginia at March 27-28, 2007. <a href="http://www.erigami.com/contacts.html">Contact us</a> to schedule a meeting on the Forum.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/virginia-forum/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>What if Truwex found issues on a webpage, which are not issues (at least not for me)?</title>
		<link>http://www.erigami.com/blog/truwex-online-customization/</link>
		<comments>http://www.erigami.com/blog/truwex-online-customization/#comments</comments>
		<pubDate>Wed, 22 Nov 2006 15:58:16 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Truwex News</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/truwex-online-customization/</guid>
		<description><![CDATA[Truwex can be customized for a particular website. Find out how to remove not necessary issues from Truwex reports. ]]></description>
			<content:encoded><![CDATA[<h3>Option A: Disable unnecessary checks</h3>
<p>A user may choose a set of quality checks in the Truwex online tool. To do this, expand categories on the Truwex online tool, and choose rules to validate a webpage. For example, if a web page does not need a skip link, you may uncheck it.</p>
<p><img width="453" height="292" alt="expand Truwex issue category and select issues to check " src="/blog-images/issue-category-expand.png" /></p>
<h3>Erigami approach to website quality and compliance validation</h3>
<p>We assume websites may follow custom compliance standards: national legislation, industry standards, corporate guidelines. There are many ways to make a website accessible and compliant. Addressing this technology diversity, Truwex provides a choice of quality rules for validation both in the online and software product versions.</p>
<p>The Truwex software product goes further than the online tool and provides settings to control quality rules. For example, if a webpage uses Google Analytics to track visitors, Truwex may detect an issue “Web beacon with/without cookies is found”.</p>
<p><img width="454" height="211" alt="Truwex detected web beacon" src="/blog-images/web-beacon-report.png" /></p>
<p>If this beacon is approved for a website (a website uses it to track customers), it can be excluded from results. Therefore this issue which is visible on the Truwex online tool, will be made not to appear in the Truwex software product version.</p>
<p><img width="454" height="211" alt="Provide an exception for approved web beacon" src="/blog-images/web-beacon-exception.png" /></p>
<p><a href="http://www.erigami.com/download.html">Download Truwex trial version</a> and see how it works on your website.</p>
<h3>Option B: Provide your feedback</h3>
<p>If you believe that Truwex has validated your webpage incorrectly, please provide feedback. You may post on this web page (all posts are moderated) or fill out a feedback form. We highly value you opinion. If your advice is valid and can be incorporated into Truwex, we will make a special mention of your name and publish a link to your website on erigami.com.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/truwex-online-customization/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>How to Stop Flash Sound in FireFox</title>
		<link>http://www.erigami.com/blog/disable-sound-firefox-ie/</link>
		<comments>http://www.erigami.com/blog/disable-sound-firefox-ie/#comments</comments>
		<pubDate>Thu, 26 Oct 2006 08:40:03 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Browsers</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/disable-sound-firefox-ie/</guid>
		<description><![CDATA[… and it works also for Internet Explorer. HTML and Flash sounds are OFF in the browsers, QuickTime and Media Player keeps playing, other Windows sounds are ON as well. ]]></description>
			<content:encoded><![CDATA[Everyone knows that FireFox has no sound settings. IE has one, but it blocks only HTML sound. The only way to silence Flash is muting Windows sounds. This is not really convenient for the most of people. However for the blind it is a real accessibility problem, since a web page sound may interfere with a screen reader voice. WCAG 2.0 draft (a new <a target="_blank" href="http://w3c.org/wai/">W3C</a> web accessibility standard) features a <a target="_blank" href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/Overview.html#visual-audio-contrast-dis-audio">requirement</a> to web page sounds.
<p style="padding-bottom: 0pt">The solution:</p>

<ul>
	<li>Open FireFox installation folder. The default path is “C:\Program Files\Mozilla Firefox”.</li>
	<li>Create an empty file in this folder with the name “msacm32.dll”. Use Notepad.</li>
	<li>Close all FireFox windows and open a web page with Flash sound to test it.</li>
	<li>If you wish to return sound back, just rename the file “msacm32.dll”.</li>
</ul>
The IE recipe is the same with only difference of the installation folder path, which is “C:\Program Files\Internet Explorer” by default.

Simple? Yes, as promised.
How it works.

Flash uses Windows DLL msacm32.dll to play sounds. A Windows application starts searching for DLLs it its own folder. If it does not find a library nearby, it goes to the other places as a system folder (C:\WINDOWS\system32). Flash is an ActiveX control. It works in the context of browser’s process. Flash uses browser’s DLL to play sound. Placing an empty file in the FireFox folder, we prevent a browser from accessing the actual sound DLL. Therefore the sound is disabled.We tested this method, and did not encounter problems. If you find one, please post comments. I’m pondering a piece of software, which will block sounds from any Windows application in a user friendly way. If you really need one, leave your comments.

Do not forget to try Erigami <a href="http://checkwebsite.erigami.com/accessibility.html">online checker</a> for web accessibility, privacy, quality and performance.

Read the new acrticle of Vladimir Popov about WCAG 2.0 on <a target="_blank" href="http://evolt.org/can_wcag_2_be_simpler">eVolt</a>.

<em>Invented by Alexander Ignatine.
</em>]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/disable-sound-firefox-ie/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Analyzing WCAG 2.0 examples of user defined colors in browsers</title>
		<link>http://www.erigami.com/blog/wcag-color-user-defined/</link>
		<comments>http://www.erigami.com/blog/wcag-color-user-defined/#comments</comments>
		<pubDate>Mon, 04 Sep 2006 14:26:06 +0000</pubDate>
		<dc:creator>ik</dc:creator>
		
	<category>Web Accessibility</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/analyzing-wcag-20-examples-of-user-defined-colors-in-browsers/</guid>
		<description><![CDATA[Investigation of color contrast failure examples in WCAG 2.0 "F24: Failure of SC 1.4.1 due to specifying foreground colors without specifying background colors or vice versa". Can these HTML examples really make problems to disabled users?]]></description>
			<content:encoded><![CDATA[<p>Investigating common failures in the WCAG 2.0 techniques document, I decided to check the HTML code provided as an example to the Common Failure: <a href="http://www.w3.org/TR/WCAG20-TECHS/Overview.html#F24">&#8220;F24: Failure of SC 1.4.1 due to specifying foreground colors without specifying background colors or vice versa&#8221;</a>. The failure demonstrates a poor technique to the Success Criterion <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/Overview.html#visual-audio-contrast-contrast">&#8220;1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1. (Level 2)&#8221;</a>. The provided HTML examples prevent the browsers from showing user defined color text and background.</p>
<p>I have tested the failure examples in several browsers and discovered that these examples generally do not lead to problems with user-defined styles: 3 sample codes of the 5 have no problems in all tested browsers, and 2 sample codes have problems only in IE 6.0, therefore it is fair to consider this problem an IE bug.</p>
<p><strong>Testing</strong></p>
<p><strong>Browsers:</strong> Internet Explorer 6.0 SP2, Internet Explorer 7.0 beta 3, FireFox 1.5, Opera 9.0.</p>
<p><strong>Workflow:</strong> I created 5 pages with html taken from the failure examples&#8217; code, inserted some comment text and uploaded the pages to the web. Then I adjusted the browsers to show text, background, and links not in the colors specified by the page author, but in my own user-defined colors: text color - yellow, background color - grey, unvisited links color - white, visited links color - pink. Then I opened each page in every browser and examined them carefully, paying special attention to the colors. The goal of testing was to make sure that the pages would display the user-defined colors (i.e. the author-defined colors would be totally ignored in spite of the way they were set in HTML).</p>
<p><strong>To set user-defined colors in a browser:</strong></p>
<ul>
<li><strong>Internet Explorer.</strong> Open menu Tools > Internet Options. In the Internet Options dialog:<br />
<ul style="margin: 0px 0px 0px 26px; padding: 0px">
<li>Press Colors button, and in the Colors dialog uncheck the &#8220;Use Windows colors&#8221; box and set your chosen colors, press Ok to close the dialog.</li>
<li>Press Accessibility button and in the Accessibility dialog check the following 3 boxes under the &#8220;Formatting&#8221; label: Ignore colors specified on Web pages, Ignore font styles specified on Web pages, and Ignore font sizes specified on Web pages. Press Ok to close the dialog.</li>
<li>Press Ok.</li>
</ul>
</li>
<li><strong>FireFox.</strong> Open menu Tools > Options.<br />
<ul style="margin: 0px 0px 0px 26px; padding: 0px">
<li>Select the &#8220;Content&#8221; tab and press the Colors button in the Fonts &#038; Colors section. In the Colors dialog: set colors, uncheck the &#8220;Use system colors&#8221; box, and uncheck the &#8220;Allow pages to choose their own colors, instead of my selections above&#8221; box. Press Ok.</li>
<li>Press Ok.</li>
</ul>
</li>
<li><strong>Opera.</strong> To quickly test pages in this browser, I decided not to look for custom color settings but to use the standard Opera means. On the pane opened by clicking on &#8220;Glasses&#8221; button, I selected User mode instead of Author mode and set High contrast schema: black background, white text and links.</li>
</ul>
<p><strong>Pages to test</strong><br />
<a href="http://www.erigami.com/test/wcag/styles1.html">http://www.erigami.com/test/wcag/styles1.html</a> - HTML code sets background color to white<br />
<a href="http://www.erigami.com/test/wcag/styles2.html">http://www.erigami.com/test/wcag/styles2.html</a> - HTML code sets background color to white<br />
<a href="http://www.erigami.com/test/wcag/styles3.html">http://www.erigami.com/test/wcag/styles3.html</a> - HTML code sets text color to white<br />
<a href="http://www.erigami.com/test/wcag/styles4.html">http://www.erigami.com/test/wcag/styles4.html</a> - HTML code sets text color to white<br />
<a href="http://www.erigami.com/test/wcag/styles5.html">http://www.erigami.com/test/wcag/styles5.html</a> - HTML code sets hyperlink color to red</p>
<p><strong>Test results</strong><br />
The results of my tests are presented in the following table. For every page and browser the table contains a test result: whether the page was displayed with user-defined colors (marked as &#8220;ok&#8221;) or HTML defined (marked as &#8220;Not ok&#8221;). And if not, a description of the discrepancy is provided.</p>
<table width="100%" cellspacing="0" cellpadding="5" border="1">
<tr>
<td style="width: 16%"></td>
<th width="17%" align="center" scope="col"><a href="http://www.erigami.com/test/wcag/styles1.html">styles1</a></th>
<th width="17%" align="center" scope="col"><a href="http://www.erigami.com/test/wcag/styles2.html">styles2</a></th>
<th width="17%" align="center" scope="col"><a href="http://www.erigami.com/test/wcag/styles3.html">styles3</a></th>
<th width="17%" align="center" scope="col"><a href="http://www.erigami.com/test/wcag/styles4.html">styles4</a></th>
<th width="16%" align="center" scope="col"><a href="http://www.erigami.com/test/wcag/styles5.html">styles5</a></th>
</tr>
<tr>
<th align="center" scope="row">IE 6.0</th>
<td>Not ok.<br />
Background color is from the HTML code.</td>
<td>Not ok.<br />
Background color is from the HTML code.</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
</tr>
<tr>
<th align="center" scope="row">IE 7.0</th>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
</tr>
<tr>
<th align="center" scope="row">FF</th>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
</tr>
<tr>
<th align="center" scope="row">Opera</th>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
<td>Ok</td>
</tr>
</table>
<p><strong>Conclusion:</strong> Generally the page colors were those I expected. For example, if I set the browser so that the link color would be white, it was white in spite of any colors set in the page&#8217;s source. It was the same with the other colors, so I always had the desired color contrast. I ran into problems only with the first two samples when I was using the IE 6.0 browser. For some reason IE ignored my background and preferred the background set on the page. This is likely a bug, since it has been worked out with IE 7.0. Other browsers have no problems with showing user-defined colors on all test pages.</p>
<p><em>Written by Irina Kochetova</em>
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/wcag-color-user-defined/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Truwex trial version is available for download</title>
		<link>http://www.erigami.com/blog/truwex-trial-download/</link>
		<comments>http://www.erigami.com/blog/truwex-trial-download/#comments</comments>
		<pubDate>Thu, 31 Aug 2006 13:27:15 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Truwex News</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/truwex-trial-download/</guid>
		<description><![CDATA[We are pleased to announce that Truwex trial version is available for download now. After registration you will receive an email with download link and trial license code. The trial version is an SMB edition and it works with Microsoft SQL Server 2005 Express.
Truwex is a server application. It can be installed on Windows operation [...]]]></description>
			<content:encoded><![CDATA[<p>We are pleased to announce that Truwex trial version is available for <a href="http://www.erigami.com/download.html">download</a> now. After registration you will receive an email with download link and trial license code. The trial version is an <a href="http://www.erigami.com/truwex/license.html">SMB edition</a> and it works with Microsoft SQL Server 2005 Express.</p>
<p>Truwex is a server application. It can be installed on Windows operation systems. Read Truwex <a href="http://www.erigami.com/truwex/software-requirements.html">system requirements</a> for details.<br />
Read Truwex <a href="http://www.erigami.com/truwex/support.html">installation instructions</a>.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/truwex-trial-download/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Truwex version for SMB</title>
		<link>http://www.erigami.com/blog/truwex-smb/</link>
		<comments>http://www.erigami.com/blog/truwex-smb/#comments</comments>
		<pubDate>Thu, 31 Aug 2006 13:18:31 +0000</pubDate>
		<dc:creator>Vladimir Popov</dc:creator>
		
	<category>Truwex News</category>
		<guid isPermaLink="false">http://www.erigami.com/blog/truwex-smb/</guid>
		<description><![CDATA[We pleased to announce the new small business edition of Truwex. This product has a very attractive price $390 with a special discount until the 30th of November.. This version shares the same reach functionality as the enterprise Truwex edition. Differences are:
• Single server deployment
• Simplified installation procedure
• Truwex for SMB mode works only with [...]]]></description>
			<content:encoded><![CDATA[<p>We pleased to announce the new small business edition of Truwex. This product has a very attractive price $390 with a special discount until the 30th of November.. This version shares the same reach functionality as the enterprise Truwex edition. Differences are:<br />
• Single server deployment<br />
• Simplified installation procedure<br />
• Truwex for SMB mode works only with the SQL Server 2005 Express</p>
<p>Truwex for SMB is dedicated to organizations with websites up to 2000 web pages.</p>
<p>Download <a href="http://www.erigami.com/download.html">Truwex trial</a>.<br />
Read <a href="http://www.erigami.com/truwex/support.html">Truwex installation guides</a>.
</p>
]]></content:encoded>
			<wfw:commentRSS>http://www.erigami.com/blog/truwex-smb/feed/</wfw:commentRSS>
		</item>
	</channel>
</rss>
