Saturday, October 3, 2015

Accessibility - Checklist and Rule Book

Web Content Accessibility Guidelines (WCAG)
Accessible Rich Internet Applications (ARIA)
Assistive Technology
  • Android Talkback
  • Jaws IE
  • Voice  IOS
The following checklist is based on WebAIM's WCAG 2.0 Checklist. It is intended for training purposes and includes only the Level A and AA success criteria
Vision Australia
AA Compliance Checklist

Friday, September 18, 2015

Sitecore CMS : Client Browser cache Nightmare

If there is a system with CMS and CMS supplies data to non CMS system very frequent changes then one has to keep in mind about the browser cache.

There can be a scenario , your application is hosted in self kiosk mode where it has to get refresh after every 2 mins to reflect right data and don't go into sleep mode. Either you enabled attract screen or get the fresh data from the server to keep it going.

Now imagine a situation where content author has published some content and your browser refresh after 2 mins and content is not changes. BOOO......!

What if, it is browser cache is not clear and we are using angularjs to give the best user experience.

Here is the brute force method of disabling browser client side caching mechanism. This will reduce the efficiency and response time of application before you apply this.


Wednesday, September 2, 2015

Mixed Content Error http vs https


Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure script ''. This request has been blocked; the content must be served over HTTPS

The browser will load with the correct protocol. This goes for images as well. Then if the user comes from http, it will load http, https if https.

 How to Fix the Problem

If the problem appears on regular HTTPS secured pages with content that is being loaded via the insecure HTTP protocol, you can control how the content behaves.
Links with “http://” extensions need to change to contain the “s” part of HTTP protocol (https://) pointing out to an SSL-reserved port. A more elegant way of handling different protocols is to have only slashes where port is expected “//”. so that page can use the protocol used to open the page itself:


Monday, July 20, 2015

Kiosk Website Guideline


To share my experience and help you think proactively for any such application in future , here is the quick know-how.


1.       Disable Zoom in touch screen- This will be disturb UX.

2.       Hide vertical scroll bar.

3.       Disabled left and right touch scroll to avoid back and forward history.

4.       Screen resolution of Kiosk.

5.       Attract Screen, if in case kiosk site is offline. This attract screen should be screen saver. This screen saver is set of content managed screens so that we can display some information about specials or products.

6.       Kiosk refresh after 2 mins. So that it fetch timely feeds from CMS system.

7.       For Kiosk refresh ensure browser cache is disabled. Real Time Data

8.       For Kiosk Refresh mode ensure server side caching is disabled. Real Time Data .need Assessment so as to enable this based on more static or persistent content.

9.       For touch device there is concept called Pinch Zoom and Flicker pen touch. Check the setting for touch device. This comes handy.

10.   Access restriction to Kiosk Application hosted in cloud.


That’s it! J

Wednesday, July 8, 2015


. BottomMarginDiv{
bottom-margin: 20px;


How to Restrict IP to website in ?

This is essential when we want to allow only given set of ip address or domain. This is called white list IP range allow or blacklist IP range deny
  1. Private IP will not work , use public IP
  2. Private IP is machine /device ip
  3. Public IP is internet IP that connects from your computer /device to help you browse website.