Many of you would have heard of the Odeon debacle as talked about by Zeldman and Dave Shea, about how Matthew Somerville created an Accessible Odeon site, but was forced to close it down for various reasons including copyright. Well, the twittiness of the Odeon site doesn't even compare to the twittiness and accessibility issues with Share2s.com's product! (Though it is still worthy of a Net Twit award, which I'll write about later)
They've published a few lists of features, which I'll go through now to prove that the script is entirely useless, and point out where they breach guidelines such as the WAI WCAG. Unless explicitly stated, each method of bypassing has been performed using Mozilla, Firefox and Opera.
- Encrypt HTML to hide the source code
document.writestatements that eventually writes the real source code for the document. This violates Guideline 6 of WCAG 1.0.
Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.
In Mozilla, this is easily bypassed. Simply pressing Ctrl+A and then selecing View Selection Source from the context menu reveals the entire source code in the DOM. I could not do this with Opera.
- Disable offline use, prevent Save As… function to save image
I was not able to determine how exactly this is done, however it does mean that any user who wishes to download the page for viewing later offline cannot do so. I could not find any specific guidline that deals with this, but it's quite obvious that this causes unexpected behaviour for the user.
There seems to be some code in there that prevents the page displaying when (I'm assuming) the URI does not match the sites domain. Because I was unable to aquire the source with Opera, this also could not be done.
- Set No Cache
This means that whenever a user revisits the site, the entire page including all text, images and any other content need to be downloaded again. For user's with a slow connection, and especially for sites with relatively large pages, the user has to wait a lot longer to view the page again.
This can be done using the HTTP
Presumably, this was to prevent any user searching the cache for images files or other content.
I didn't bother checking the cache, I'd already, already saved all the files with Mozilla, however I believe that it must use an IE specific meta tag or something, just like everything else in this encrypted page.
- Fully disable the right mouse-click context menu
This disables a feature that the page author should not have any control over. User agents should prevent web page scripts from interacting the the user agent's interface because it interferes with the user's ability to use the application easily. This also applies to preventing the document from being saved as well.
Descent user agents, such as Mozilla and Opera have options to prevent scripts controlling the user interface such as context menus, the status bar and opening or moving windows.
Presumably, this feature was designed to prevent user's from saving images. Even IE can bypass this feature simply by pressing Print Screen on the keyboard, and cutting out and saving the picture with an image editor.
- Disable text and picture highlight select,Disable image Drag drop
Again, this interferes with the user agent's interface and thus the user's expectations and ability to use the application and website are impaired.
This did not work in Mozilla or Opera.
- Disable Image Tools Bar in IE6
Presumeably, this is to prevent the user using the save, and other buttons provided on that toolbar. This also interferes with the application interface, and thus has the same problems as disabling the context menu and secting text.
Need I say more? Who give a crap, they're annoying anyway! This is IE specific, so it doesn't apply to Mozilla or Opera, so there is no need to bypass it.
- Hide display links and address and messages in status bar
The status bar provides valuable information about the link being clicked. Looking at the URI displayed in the status bar for links can indicate to the user that the link is a fragment identifier, a link to an page on the same site or a file, or a link to another resource on another website. Not all users use this, and some choose to hide the status bar.
However for users who do use that feature, their usability of the application will also be impaired as for the 3 previous points.
Again, Mozilla has the option to disable the ability for scripts to change the status bar, and Opera displays the URI in a tooltip text, so it is not affected.
- Disable Smart Tags
- This is another IE specific feature, and I do not exactly know what Smart Tags to on websites, however, this again interferes with the application interface.
This appears to be performed using an IE specific
metaelement, which after saving the source code, can be easily removed and thus opened in IE.
- Disable Web pages printed
This feature did not work in Mozilla or Opera, however this is the easiest feature to by pass. Pressing Print Screen on the keyboard, and creating the page in an image editor will enable printing.
- Compress the Html code before encrypt
Ever heard of deflate, or g-zip compression done on the fly by the server? What a waste of time. This may actually be true, I didn't compare the source code sizes.
Nothing to bypass here… Move along people, move along …
- Bypass any web content Filter and “Fire Wall” and get more visitors to your site
There was no reason to even try to test this, it's a pointless feature.
- Stop junk mail and spam
Not if I ever find your email address! expect to be abused!