Why Web Access

We delight our customers. The President and CEO of Web Access is the Customer delight Champion. For more information of how we delight our customers please visit Customer Delight.

Software designed and developed by Web Access is effective. Software effectiveness refers to the actual usage of the software without operational and technical glitches over a period of time. The effectiveness rate at Web Access measured over 100 projects delivered in the last 6 years is at an extremely high rate of 91%, the highest in the industry. For more thoughts on the Software Effectiveness please visit .

We cater to human errors in software usage. We keep our software simple, simple to us and not necessarily simple to design. In fact most simple to use software are highly complex in design. More on human technology is available at Human Technology.

Our philosophy is to keep the software simple for users. Our thoughts on simple software are available at http://blog.nasscom.in/emerge/category/usability/

We provide free technical support for 3 to 6 months after final delivery. Thereafter the technical support is optional to the customer. In most cases very little or no support is required due to simple to use software that has been designed with human factor.

We are not cheap and do not much appreciate labor arbitrage. We would rather provide value for money than cheap labor.

Ten commandments our developers follow to designing simple software with a human factor

1.	Identify the purpose. Find a simple solution. Simple for the user. Not you.
2.	Identify and design for the minimum input required from the user. And ensure common inputs are required just once.
3.	Identify and design for all the different outputs required from the system. Allow the user to customize and save. And then available at 1 click.
4.	Design a prototype with the user interface. And get the user to check and test it. Observe the use. And listen carefully to what she says. And also to what she doesn’t.
5.	Ensure that no matter what the user does, she can’t mess up. The system protects her and her data. Also allow rollbacks.
6.	Create a visually pleasing and appealing interface. Sexy models aren’t the only pretty things people love to see.
7.	Use everyday analogies in the design. If you want to indicate a book, show a book spine. Better still, iconize it.
8.	Make the interaction intuitive. To the user. Not you. Check this extensively by observing first time users. And listen to their questions carefully.
9.	Have different interaction methodologies for first time users and power users. The power user controls can be hidden. But make sure they’re there.
10.	Listen to user feedback. Interpret their responses. And implement whenever possible