Monday, December 11, 2006

P3P- (2)

What's P3P??
At its most basic level, P3P is a machine-readable vocabulary and syntax for expressing a Web site´s data management practices. Taken together, a site´s P3P policies present a snapshot summary of how the site collects, handles and uses personal information about its visitors. P3P-enabled Web browsers and other P3P applications will read and understand this snapshot information automatically, compare it to the Web user´s own set of privacy preferences, and inform the user when these preferences do not match the practices of the Web site he or she is visiting.

What's the use of it?
P3P enhances user control by putting a Web site´s privacy policies where Web users can find them automatically, in a form users can easily understand, and, by using a common vocabulary, allows users to compare the privacy policies of the different Web sites they visit. Most importantly, this enables Web users to act on the privacy policy information they receive. In short, the P3P-enabled Web communication can bring ease, transparency and consistency to Web users wishing to decide whether and under what circumstances to disclose personal information. User confidence in online transactions can increase as they are presented with meaningful information and choices about Web site privacy practices.

Monday, November 14, 2005

P3P - (1)

What's P3P?
What's the use of it?
How it works?
P3P on action


P3P is; Platform for Privacy Preferences Project policy, a protocol designed to give the users more control of their personal information when browsing the Internet websites.

P3P developed by (W3C) World Wide Web Consortium, officially recommended on April 2002
In the mid-1990s, the W3C recognized the potential problems arising from this issue and began developing the Platform for Privacy Preferences. A primary goal of P3P is to increase user trust and confidence in the Web through technical empowerment. The P3P specification provides a simple, automated way for visitors to learn more about and gain more control over the use of their personal information on Web sites they visit. P3P has been designed to be flexible and support a diverse set of user preferences, public policies, service provider polices, and applications.

References:
http://www.p3ptoolbox.org/guide
http://en.wikipedia.org

Tuesday, July 12, 2005

What’s in it For You?


Your satisfaction is the core of our studies in finding out the proper procedures for structuring and designing a website or any solution interface to meet your expectations and to help you finding your targeted piece of information.

Since you are our user, the main role is to wear your shoes and set closer to you watching your moves for understanding your behavior and analyzing it, hoping that this may give us the chance to expect your needs in the future, if we are lucky we could hear it from you..

WHAT DO YOU EXPECT? WHAT DO YOU WANT?
WHAT MAKE YOU SATISFIED?


Our interaction with you makes our life easer in understanding before we start designing, so when you feel you have some time, it might be useful if you drop some notes in a simple post, and let’s meet here through those lines to figure out how it could work, and remember:

“YOUR SATISFACTION IS OUR GOAL”

Monday, June 20, 2005

Usability Testing in Practice

  • What's your information regarding the usability testing?
  • Does any of you proceed a usability testing in his/her organization?
  • What kind of testing? (paper prototype/operational prototype/ functional website (if internet websites) / else.

    Kindly share your experience and tell us more, let's discuss it together and find out its benefits.

    Go a head and post your comments .. :)

Sunday, June 19, 2005

Usability Testing Highlights

  • You have to clarify: we are here to test the solution interface not the user and here you have to encourage the user to talk aloud as much as possible
  • You usually want to answer questions like these..
    - Do users complete a task successfully?
    - If so, how fast do they do each task?
    - Is that fast enough to satisfy them?
    - What paths do they take in trying?
    - Do those paths seem efficient enough to them?
    - Where do they stumble? What problems do they have? Where do they get confused?
    - What words or paths are they looking for that are not now on the site?
  • Types of Questions to Ask..
    - Do users realize, without being told, whose site they are working with just from looking at the home page?
    - Do users click through pages or do they use search?
    - What words do they try in search?
    - What do they choose from the search results?
    - How do they react to the download time for specific pages?
    - If they abandon a shopping cart before buying, when do they stop and why?
  • Iterative Testing Works Best: Usability testing is an iterative process that involves testing the site and then using the test results to change the site to better meet users' needs. The best process is to try out a prototype with a few users, fix it, and test it again.

Monday, June 06, 2005

Why Internationalization is Important?


What's internationalization?
To Improve the quality and the usability of a solution in international markets- if website- the effort to make the website available to everyone regardless the location.
By the following:

  • Use the proper language
    -Character encoding (Unicode is a standard character encoding for all languages that’s now widely adapted)
    -Facilitating multilingual web pages and websites.
    >bi-directional text
    >ruby annotation (character annotations used to clarify the pronunciation often added to ideographic scripts such as Japanese)
    >number formatting
  • Localization consideration
    -cultural sensitivity in graphics and text
    -flexible forms that allow different address and naming conventions
    -political sensitivities
  • Visual design based on the new technology and most recent style to match the most recent designing standards
  • Usability testing methods
  • Register in well known search engines and directories

Thursday, June 02, 2005

The Meaning of Accessibility


Accessibility in the context of the web means building a web that everyone is able to access, regardless of their level of physical or mental ability.
  • Consider users with motor deficiencies or cognitive disabilities or blindness
    -Motor deficiencies: keyboard navigator (shift-tap-enter) and access keys which are keyboard shortcuts that replace the need to use the mouse for navigation in browsers that support them. In Internet Explorer on Windows, you can press ALT + an access key (on Macintosh, you can press Control + an access key). Then press Enter to activate the link.

    -Cognitive disabilities: clear simple layout not relying too greatly on the user memorizing thing (Usability)
    -Blind users:
    >Screen magnifier
    >Common assistive technology called “screen readers’ which are browsers read the content of a website word-by-word

    Note: Flash in its last 2 versions can make its content accessible to use screen readers and keyboard navigator
  • Images, using alts for the most images are using in the website, Images used for headings are applied using style sheets – since the heading exists as text behind the graphic, alt attributes are unnecessary.
  • Colors, the site's font and background color combinations should be checked against the different color blindness conditions and ensured that all information is still clear.
  • Font sizes, should be able to change the size of the webpage to the user’s preference through his browser:
  • In Internet Explorer, from the browser’s tool: view / text size / and then preferred size.
  • In Netscape from the browser’s tool: view / text zoom / and then preferred percentage size.
    » Notes and References could be used in websites as standards grantee (Standards compliance): Level A compliance as specified by the Web Content Accessibility Guidelines. The majority of Level AA and AAA requirements are also met.
    All pages validate as XHTML 1.0 Transitional and use structured semantic markup. The CSS also validates.

Tuesday, May 31, 2005

Useful Definitions About Information Design

What’s Information Architecture?
It is the process of organizing, labeling, designing information and navigation system that help people find and manage information more successfully.


Labeling: The way you represent the concepts

  • Be careful about the words you use (clear and telling)
  • If you like to use images in labels be sure they add value and increase the communication with the user, and adding some text to the Image is preferable

Navigation: The way we find what we’re seeking

  • Well-designed site has to provide intelligent labels, intuitive paths, readability, and clear conceptual model of the site.
  • Users want to know where they are, what are the choices from here, how to get where they want to go and how to come back once they are there.

What's Usability?
It’s the measure of the quality of a user’s experience when interacting with a website. (How long it takes user to find info. And how long it takes him to learn how to use the site?)

Usability Factors:

  • Ease of learning
  • Efficiency of use
  • Memorability
  • Error frequency and severity
  • Subjective satisfaction

Why is Usability important?

  • Most of research agencies found that:
  • People cannot find the info. they seek on a website about 60% of the time
  • 50% of potential sales are lost from a site as users can not find data
  • 62% of websites shoppers have gave up looking for their wanted items

What’s Layout?
Key pages with black and white boxes and guidelines, to describe how the window will appear to the users, write up the read, editorial, and functionality requirements for each page. Also include some specifications like page resolution, each area size and place, also no. of levels .
Each shows the major functional areas (Body, Menu, Ads. + Logo)

Design for Weblications (1)


The fundamental purpose of all web applications is to facilitate the completion of one or more tasks. Unlike visitors to traditional, content-centric websites, users of web applications invariably arrive with specific goals, tasks, and expectations in mind. Of course, that’s not to say that visitors to content-based websites don’t also arrive with certain goals and expectations, but rather that the motivations for using a web application are almost always explicit and precise.

Main Deference between a Web Application (Weblication) and a Traditional Website.
It is important to establish an objective means of differentiating between a web application and a traditional website.


  • One-to-one relationship – Web applications establish a unique session and relationship with each and every visitor. Although this behavior is fundamental to Web applications it is not present in either content-based websites or desktop applications. A web application such as Hotmail knows who you are in a way that Cnet or even Photoshop doesn’t.
  • Ability to permanently change data – Web applications allow users to create, manipulate, and permanently store data. Such data can take the form of completed sales transactions, human resources records, or email messages to name but a few. This contrasts with web services like Google that allow users to submit information but do not allow them to permanently store or alter information.
  • And the Web applications (Weblications) are deferent in many other ways like:
    References:

- More interactive and requiring constant user action and reaction
- Complex interaction than in the traditional websites
- More likely to be used more intensively and more frequently than traditional web sites
- Its users are willing to invest more time in learning the functionality of it for the payoff of increased productivity.

Monday, May 30, 2005

Design for Weblications (2)


Design Considerations:

  1. Visited Links: No need to change its colors, it’s preferable to specify the same color for the visited and unvisited links (user might fill out the same form many times).
  2. Hyperlinks and Buttons: You can include both hyperlinks for navigating to locations and command buttons for carrying out actions.
  3. Frames: You may use it, the case not sensitive like in content websites.
  4. Searching: web-applications are rarely involved searching except in the online help.
    Page Title: It might be the same page title on every page, perhaps indicating the page application name and version.
  5. Hypertext Linear Tasks: The users perform tasks, which may require linear paths. This requires a design that focuses on navigation among tasks rather than hypertext among pages of content.
  6. Scrolling: If moving from page to page requires lots of background application processing and the pages take a while to download, users may prefer one long form.
  7. Cross-Browser Considerations: Designers can specify a required browser, much like they specify the required hardware or operating system environment to give them more freedom of design.
  8. Browser Button: It’s preferable to hide them and the designer could provide alternative navigation method.
  9. Pull-down Navigation Menus: Not recommended in form pages to prevent the users to leave before completing the forms.
  10. Home Page: Contains the main menu, Product over view, splash screen contained a product graphic and version level also the copyright information and system statistics.
  11. Help: It’s more like the online help for (non-web-based) application.
    Open Browser In Full Screen: To eliminate the browser confusion where reoriented toward delivering a real application.
  12. Minimize the Use of Windows
  13. Use Rollovers: Revealing alternate choices or presenting additional information as it is needed and avoid user confusion by not presenting too many options at once.
    References:
  14. Use Alt-Overs: When the immediacy of a roller is not needed.
  15. Use Auto-complete: (WebDAV Technology) WebDAV notifications use UDP packets to notify the client that the Exchange store detected a subscribed event. The subscription command specifies the UDP port on which Exchange will contact the client computer. The client application must have a UDP listener running on the port specified on the subscription, so that the events will be received. Note that normal firewall configuration blocks UDP packets, so WebDAV notifications typically only work within an intranet, or over a PPTP tunnel.
  16. Use Login / Logout: Use login page and logout link throw the application
  17. Web applications with a Flash interface use the same applications (ColdFusion, Active Server Pages, or JavaServer Pages) to generate dynamic content, but the Flash movie can be updated seamlessly—no page loading is necessary. You can combine the power of the Web application scripting language with the power of ActionScript to change and update your Flash movies.