SortSite is a popular desktop software for testing of web applications for broken links, browser compatibility, accessibility and common spelling errors. It is also available as a web application known as “OnDemand“.
You can generate a free sample test of your website at:
I’ve done a lot of accessibility testing and development work over my career. One of the many free tools that I use in that role is FireEyes. Deque also has some commercial packages for developer use.
FireEyes adds a new tab on the Firebug tab bar and adds the ability to analyze a web site for WCAG 2.0 Level A and AA and Section 508 accessibility violations. The Stand-Alone version of FireEyes is a browser plugin to the FireFox browser. It requires that the FireBug plugin already be installed
- Firefox 31-41
As of 2015aug21, the current version of the extension is NOT signed and will not execute on later versions. [See my later post on this topic]
- FireBug 2.x – Do NOT install Firebug v3 alpha as the tab will not show.
NOTE: should be on Firebug tab labeled “Worldspace Fireyes”, but does not seem to be available in Firebug3.
NOTE: if you try to download in MSIE, you must rename the .zip to .xpi, and then open with Firefox.
I wrote about P3P a very long time ago, and have implemented it on several websites. Some history, the W3C crafted the P3P policy.
Microsoft introduced P3P support in IE6 (in 2001) and it remains implemented in all current versions of the browser. The primary intended use is to block 3rd party cookies within the browser on behalf of the user.
Interesting enough, Microsoft has had been a bit of a struggle with Google and Facebook, which send the following HTTP response headers.
P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."
P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p"
After moving or updating WordPress, later plugin updates may start asking for FTP and/or SSH credentials. This can be easily avoided by setting the following:
- In wp_config.php
- Verify file ownership permissions, on Ubuntu, this is typically:
sudo chown -R www-data:www-data YOURFOLDER