What if Truwex found issues on a webpage, which are not issues (at least not for me)?
del.icio.us
digg November 22nd, 2006
Option A: Disable unnecessary checks
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.
Erigami approach to website quality and compliance validation
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.
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”.
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.
Download Truwex trial version and see how it works on your website.
Option B: Provide your feedback
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.
Entry Filed under: Truwex News
3 Comments
1. Gill | March 11th, 2007 at 12:23 pm
Hi Vladimir, I said I’d do some more testing for you and here’s an example.
The page above uses a red heading ff0000 on a white background ffffff. According to the Accessibility colour wheel at http://gmazzocato.altervista.org/colorwheel/wheel.php this combination is fine and gives a big OK but your validator gives me an error. [WCAG2 1.4 (2)] Low-contrast text is found.
I’ve run the page through Vischeck and through colorfilter.wickline.org and it’s fine.
So either the WCAG limits are too strict or your checker is wrong or the colour wheel is.
I’ve also noticed that it seems impossible to use orange on a page. I’ve tried various shades and various backgrounds but I can’t get anything to validate.
2. Alberto | April 5th, 2007 at 6:39 am
Validation does not handle the [NOSCRIPT] tag correctly. Looking at the DHTML source, it is always reported empty ([NOSCRIPT][/NOSCRIPT]) even if it is not.
This problem causes the side-effect that the error “Script based link is found” is always presented even if a NOSCRIPT alternative has been inserted.
NOTE: I have posted the message again replacing “” with “]” because I have seen the blog CMS removes tag
3. ik | April 6th, 2007 at 7:42 am
Hello, Alberto,
Thank you for the feedback. We are going to fix this in the release version of Truwex.
Irina Kochetova,
Erigami.
Trackback this post