Web 2.0 is about harnessing the potential of the Internet in a more collaborative and peer-to-peer manner with emphasis on social interaction.

Main

December 15, 2010

JetBlue violates disability rules, gets punished

JetBlue is in news again, and this time also not for good reasons. Few weeks back a lawsuit was filed against JetBlue airways for inadequate accessibility of check-in kiosks at the airport in addition to the inaccessibility of their website. This time the reason for the legal action is violation of rules protecting air travelers with disabilities and for failing to disclose when flights sold by the carrier were being operated under a code-sharing arrangement. The airline is being penalized $600,000 for the mistake.

The Department of Transportation ruled that $350,000 of the amount would have to be paid by the carrier, while $250,000 could be used to establish a task force to audit the carrier's handling of passengers with disabilities create a disability customer care center and enhance the carrier's website to improve its information for travelers with disabilities.

This post may appear to be off-topic, but it is not. Though it is not about accessibility it is about violation of rights of disables. My intention to write this post is only to reiterate the need for powerful disability laws and to encourage formation of inclusive society.

If we learn to empathize with our diverse audience, it is not really difficult to realize an inclusive planet.

Shrirang Prakash Sahasrabudhe

Accessibility Specialist- SETLabs

Shrirang_s@infosys.com

 

 

December 6, 2010

BS 8878 is up

First British Standard to promote web accessibility and to facilitate digital Inclusion is a reality now. BSI (British Standards) has developed BS 8878 to facilitate inclusion of everyone in the web innovations. 

BS 8878, the Web Accessibility Code of Practice is based upon the earlier guidance published in 2006. The standard enables both public and private organizations to embrace accessibility of their websites and softwares.

The standard clearly demonstrates how organizational policies and production processes should be designed so that the digital divides can be effectively identified and bridged. The standard promotes active involvement of the target user groups to ensure successful implementation of standards.

 

Shrirang Prakash Sahasrabudhe

Accessibility Specialist- SETLabs

Shrirang_s@infosys.com

 

December 3, 2010

Australian DDA moves ahead

It is good to know that, the Australian Government has taken a step forward in realizing better accessible and inclusive web within Australia. It has now endorsed the Web Content Accessibility Guidelines (WCAG) 2.0 for all government websites. Earlier mandate was compliance with WCAG 1.0.

Early this year the Government Released National Transition Strategy (NTS) that clearly sets out a timetable and implementation plan for achieving compliance wit new guidelines. All government websites which fall within the scope defined by NTS must be upgraded to achieve WCAG 2.0 conformance.

The timelines for the same are:

  • Level A (Single A) by 31 December 2012
  • Level AA (Double A) by 31 December 2014

Websites must fulfill all five WCAG 2.0 conformance requirements In order to be compliant under new guidelines.

The strategy advocates careful and design level planning for accessibility implementation so that different needs of various user groups can be met. Use of standards-based web technologies and best practice content management processes has also been advised to mitigate any potential accessibility challenges. Principle of progressive enhancement has been promoted to ensure smooth transition from WCAG1.0 compliance to WCAG2.0 compliance.

All the best and hope to see more inclusive web in Australia.

Shrirang Prakash Sahasrabudhe

Accessibility Specialist- SETLabs

Shrirang_s@infosys.com

 

 

November 30, 2010

Canadian accessibility ruling: some insights

 

Today Canadian Federal Court gave an important ruling on an accessibility complaint. A blind woman from Canada had filed a suit against  government of Canada. she claimed that the government "violated her rights under section 15(1) of the Canadian Charter of Rights and Freedoms, Part I of the Constitution Act, 1982.

the applicant provided five examples of accessibility barriers faced by her. the evidence of barriers was sufficient to prove that the applicant was discriminated against due to the need to access information and apply for employment via these websites. The Court is allowing the government 15 months to achieve compliance.

Here is the detailed ruling.

 

 

 

 

Here are some insights those I could assimilate from the lawsuit.

  • Do not build for today, build for tomorrow

In today's fast changing world obsolescence is guaranteed and accessibility standards are no exception. One salient element of the ruling is that the court found that the Canadian accessibility standards VIZ Common Look and Feel standard ( CLF ) is utilizing WCAG1.0 ( which is pretty outdated now) and government should update the CLF standard to utilize WCAG 2.0. web designers and developers must keep this in mind while building solutions. And should always aspire for addressing needs in future. I entirely agree that if the standard refers to WCAG1.0 , it is but obvious that we follow that, but wee must keep our knowledge up to date. So that we can go an extra mile to achieve real accessibility and not just the compliance to outdated standards.

  • One size does not fit all

whenever you test for accessibility, make it a point to include multiple assistive technologies. It is practically impossible to test the site with all possible assistive technologies, but assuming that all users having a particular disability utilize a single assistive technology product is incorrect. Use top two most predominant assistive products to ensure better results.

 

  • Design accessible, retrofitting is expensive

This is a well established fact that addressing accessibility during design is  the most cost effective way  to realize accessible website. Accessibility is not atoll a rocket science. Using progressive enhancement approach accessibility can be woven into the website without compromising timelines as well as aesthetics.

Shrirang Prakash Sahasrabudhe

Accessibility Specialist- SETLabs

Shrirang_s@infosys.com

 

November 23, 2010

Can a politician make it to be an effective UX professional?

Can a politician make it to be an effective UX professional?

Sounds absurd, right? But it is not so. After reading the post you would concur with me.

This apparently absurd idea crossed my mind while listening to a conference presentation. The presenter talked about need of understanding user's culture for designing products and solutions for emerging markets. Let's quickly understand what "culture" is.

Though every individual is unique, he or she always cherishes certain common values and beliefs. Culture brings these individuals together to form a group. Culture is a set of behavioral qualities and standard beliefs which distinguish one group from other. Culture operates at cognitive, perceptual and motivational levels. Culture provides us with a set of rules to predict and perceive our interactions with the unpredictable world. It plays vital role in shaping people's perceptions and expectations. Same things mean different to different individuals, like certain symbols which are considered holy in India may be considered offensive in other parts of the planet. Hence understanding the target audience and the cultural norms is essential key to designing interactions, interfaces and any user experience.

And the most competent group of individuals who very well understand and often leverage the cultural nuances is the politicians. Look at their campaigns, election manifestoes, and color and language preferences for the campaign material, colors and symbols used for flags and banners and their costumes too. Being politically neutral, I am not sighting any examples. But readers can easily correlate and sight examples in respective geographies.

It is clearly evident that politicians and political parties make these choices on the basis of the cultural and social status of their constituencies. They possess excellent and effective people skills. They use those skills to understand and analyze the target audience to determine people's nerve. They precisely understand what works and what does not work.

In usability parlance we call this empathizing with users, understanding user expectations and creating memorable experience by connecting with the audience. So I think that as far as cultural design decisions are concerned, politicians can be effective interaction designers. Only word of caution is: if you get them on board, do not let them play politics

 

Shrirang Prakash Sahasrabudhe

Accessibility Specialist- SETLabs

Shrirang_s@infosys.com

 

 

October 20, 2010

JetBlue accessibility lawsuit

In one of the earlier posts I had mentioned about accessibility complaint against Arizona state university. Unlike many past accessibility lawsuits, The trigger for the lawsuit was not inaccessibility of a website but was inadequate accessibility of Kindle reading device.

This time, recently filed lawsuit against JetBlue Airways focuses on accessibility of check-in kiosks at the airport in addition to the inadequate accessibility of their website.

California Council of the Blind and three California residents with visual impairments have together filed the suit in Federal Court for the Northern District of California.

the Unruh Act, the California Disabled Persons Act and the California Unfair Competition Law are the three California laws those form a basis for the suit.

Usually "structured negotiations" Are preferred for resolving accessibility Complaints. It is a collaborative effort towards reaching win-win consensus. Unfortunately JetBlue refused to opt for this litigation free way.

 

Shrirang Prakash Sahasrabudhe

Accessibility Specialist- SETLabs

Shrirang_s@infosys.com

 

 

September 15, 2010

Accessibility Vs Usability

There seems to be lot of confusion between accessibility and usability and what comes first. While working on different web projects we usually emphasize on ease of use. For that we customize our web pages for different types of users such that the users do not have to traverse through several pages to get to the topic of his/her interest.We not only provide the information but we make that a wonderful experience for the user.

For example, I go to canteen everyday and take orange juice. For this I have to stand in queue, place the order and wait for the juice to be delivered. Vendor observes this for few days and one day as soon as he looks at me entering the canteen, he prepares the juice and provides me the glass when I reach the counter. Not only that, he ensures that the juice is presented in such a way every day that I wait to go and have the juice. Vendor does the same thing for all different types of users by observing there behavior over a period of time.  He keeps on refining the process. That is creating a user friendly environment and that is what usability is all about.

Then what is accessibility. Now take a similar example for a user who is not able to go out till canteen to have the juice. Vendor provides the on call delivery to his/her desk. That is how he ensures to make his service accessible to everyone at anytime.

What comes first, accessibility or usability? This can still be debated. But there are now legal implications of not addressing accessibility issues. There are guidelines which need to be followed to ensure that all the web pages are accessible to differently abled users. So every site now has to be accessible as well as usable. Infosys iProwe helps users to address the accessibility issue for their web pages. I always thought that usability was important in this competitive environment and now realize that accessibility is equally important.

 

Neha Ranjeet Ghorpade

Product Manager - Future Web Research Lab, SETLabs

neha_ghorpade@infosys.com

August 20, 2010

Free iProwe Web Accessibility Report


You can now request for a free iProwe Web Accessibility assessment report of your Web page. The reports can check your web page against accessibility guidelines such as WCAG 1.0, WCAG 2.0, Section 508, DDA UK, DDA Australia, BITV Germany.

The URLs for the pages where you can request for the free reports are given below:
 

http://www.infosys.com/offerings/products-and-platforms/iprowe/Pages/index.aspx

http://www.infosys.com/offerings/products-and-platforms/iprowe/Pages/request-accessibility-test.aspx


June 24, 2010

Hyperlinks and accessibility

Use of electronic information has been around since inception of computer technology but proliferation of personal and affordable computers coupled with birth of WWW spurred a huge demand for sharing and interlinking this information. HTML, the language of the web has made interlinking possible by providing anchor tag, popularly known as hyperlink. On any webpage, you will always find at least one hyperlink. There are three types of hyperlinks, link which when clicked opens another web page or document, bookmark link that points to a place on the same web page and command link that initiates some function or action when clicked.

Continue reading "Hyperlinks and accessibility" »

June 7, 2010

HTML forms and labels

Further to the post Machine interactions sans labels, where I talked about importance and necessity of labels for user interface controls, today we will understand different labeling techniques and respective pros and cons. to begin with, let us define the meaning of the term "label" in context of this post. Label is a text, color, image or an audio that indicates the purpose of any control on a webpage. Controls comprise text and password fields; selection boxes and radio buttons; checkboxes and push buttons, and links and clickable items. As text is the most accessible form of information, I am restricting myself to text labels only.

Consider the following code

User Name: <input type="text" id="UID">

This code fragment renders a textbox. The text "User Name:" appears on the left hand side of the textbox. Users who can perceive visual input can visually associate "User Name:" with the text box. For them, this text acts as a label for the text field. But as this association is not programmatically determinable, assistive technologies like screen readers fail to associate appropriate text with the form field. Online forms prior to HTML4.0 had this limitation.  HTML 4.0 overcame this limitation by adding label element. Labels are of two types, implicit and explicit.

Implicit label wraps the corresponding input control within itself. <label> user name: <input type="text" name="uname"> </label>

Explicit label uses "for" and "id" attributes to realize the association. <label for="UID">User Name:</label> <input type="text" id="UID">, The value of "for" attribute of the label matches with The value of "id" attribute of the input. This is the link that connects the label with the form field.

We recommend use of explicit labels because
  • Screen readers can associate appropriate label with form fields
  • If you click on the label the focus moves to the associated field
  • In case of checkboxes it also toggles the checked status of the checkbox
Explicit labels are used with
  • input type="text"
  • input type="password"
  • input type="file"
  • input type="radio"
  • input type="checkbox"
  • textarea
  • select
one more way to label the elements is to use "title" attribute, for example <input type="text" title="enter your first name">. The value of "title" appears as a tool tip on hover of a mouse. This technique should be used in conjunction with label element and not as an alternative to it.

Buttons do not need explicit labels as "value" attributes acts as an implicit label for them. Use "value" attribute of input type="button","reset" and "submit" for labeling the controls. In case of input type="image" use "alt" attribute for labeling the button.

In next post we will understand How to create accessible hyperlinks.

Shrirang Prakash Sahasrabudhe
Accessibility Specialist- SETLabs
Shrirang_s@infosys.com

May 24, 2010

Web accessibility- tips to optimize effort

"I want my website to be accessible but how much would it cost me in terms of both time and money?" this is the most common and obvious question accessibility experts need to answer.

I have seen accessibility requirements taking a back seat due to budget constraints. If we want to see accessibility being welcomed by clients, reducing the cost is essential. Here are some tips to optimize the process and effectively controlling costs.

  • Don't go by guidelines; go by tags
    HTML provides many tags and elements to create and present web content. But web authoring statistics, reveals that not all tags are used equally. Naturally, tags which occur more frequently will contribute more to accessibility problems on the page. In my opinion, if we start analyzing the site's accessibility on the basis of the most frequently used HTML tags, we would be able to quickly pinpoint and remediate the accessibility problems.

    For example if a 100 page site has 1000 informational images, 2000 hyperlinks and, 200 form fields, we can start with assessment of hyperlink accessibility, followed by images and then the form fields. This progressive approach will help cover maximum content in minimum time.

  • Don't test every page, test everything on a page
    Most professional websites today are powered by CMSs and templates. Testing similar pages/screens individually is not a fast track option. Instead, choose unique screens and pages for review. By doing this you preempt the possibility of detecting same defects multiple times.

  • Don't go for user testing before you bridge code level gaps
    Testing with real users is essential and useful, but effectiveness of user's involvement depends on when you involve them in testing. As per my experience, unless all coding issues are fixed, user testing is not very effective. In such a case users tend to report accessibility issues which are caused by missing tags and attributes. Missing tags and attributes can be best uncovered by an automated tester. User testing should essentially reveal usability issues in accessibility implementations.

Shrirang Prakash Sahasrabudhe
Accessibility Specialist- SETLabs
Shrirang_s@infosys.com

May 14, 2010

Update on W3C India Office Opening Event

As mentioned in the previous post, I attended the W3C India Office opening event and a conference on Internationalization and Standardization associated with this event, which was organized by the Technology Development in Indian Language (TDIL) of the Department of Information Technology, GOI on 6th and 7th of May , 2010. While the opening of the India office was an occasion for which several folks from W3C, including the newly appointed CEO Dr. Jeffery Jaffe came to India, the focus of the event was primarily on the standardization and internationalization of the standards pertaining to web, mobile telephony as well as Indian language computing. Details of this conference and event are available at the W3C India site.  What follows is a quick review of the two day proceedings of the conference.

Continue reading "Update on W3C India Office Opening Event" »

May 5, 2010

W3C to inaugurate an India Office on 6th May 2010

World Wide Web Consortium (W3C), the international community that develops standards to ensure long term growth of the Web, will inaugurate an India Office on 6th May 2010 at an event organized by the Technology Development for Indian Languages (TDIL) of the Department of Information Technology, Government of India.

TDIL will be hosting the W3C office in New Delhi. The launch will be a collaborative effort between TDIL and W3C during the "World Wide Web:Technology, Standards and Internationalization Conference" being organized by TDIL in New Delhi on May 6th and 7th, 2010 at The Lalit Hotel. The Manufacturer's Association for Information Technology (MAIT) and NASSCOM have partnered with TDIL for supporting this conference.

The conference will have a keynote by Dr. Jeffrey Jaffe, the CEO of W3C. Several noted speakers from the government department as well as industry leaders will also address the gathering. Detailed schedule of the conference is available here.

I will be representing Infosys at this event and will be speaking on, and chairing a panel discussion on Web Content Accessibility in Indian Languages.

March 29, 2010

PDF Accessibility

PDF is a convenient way to put an existing content in a document on a Website. However the rapid growth in the use of PDFs on Websites has led to increasing concerns about accessibility, particularly for the users of screen reading technology, which converts text into synthetic speech. We need to make PDF files on the web accessible for the same reasons we make other web content accessible.

Before the release of Acrobat 5 in 2001, information presented in PDFs was generally considered inaccessible. However, the release of Acrobat 5 was a significant step in improving the accessibility of PDF documents. Version 5 and later allowed content to be tagged in a similar way to HTML documents. We can add XML-like tags to give structure to a PDF. What makes PDFs robust and accessible is the structure. A PDF is probably accessible if it is tagged. Screen readers had to be upgraded to understand these PDF tags. Whereas mere presence of tags does not guarantee accessibility, since they might have been wrongly used, the absence of tags definitely renders the PDF inaccessible.

The World Wide Web Consortium (W3C) does not recognize PDF as a standard format since it requires the Acrobat browser plug-in to access the information contained in the document. Although recent advances have made it possible to create a PDF document that can be accessed by a greater number of people, the Web Content Accessibility Guidelines (WCAG) of the W3C do not yet consider PDF as fully accessible.

In situations where providing accessible PDFs is not possible, some alternative should be provided for users who are unable to access the PDF but would still want the information it contains. The ideal accessible alternative for content provided in a PDF file is an equivalent HTML page that is both valid and accessible.

PDF accessibility is not as straightforward as HTML accessibility. The use of PDFs still causes accessibility problems for some Web users. However, in the next few years, the extent of this problem is likely to reduce as more accessible PDFs are produced and an increasing number of assistive technology users upgrade their devices.

 

Nishtha Srivastava (nishtha_srivastava@infosys.com)

Tarun Prakash Sharma (TarunPrakash_S@infosys.com)

Web 2.0 Research Lab, SETLabs.

March 26, 2010

Web Product Development Challenges

Product development is the most challenging assignment and web 2.0 product developments have its own different set of domain of problems. Creating web 2.0 product needs very imaginative strategies since it deals with virtual world and social interaction, also it needs capability to understand customer requirements deeply to deliver the best possible solution.
There were many challenges during web product development. Some key challenges, and hence success factors are as follows:
Technical challenges:
1. Technical & Architecture level challenges: A key success for any product is its platform independent, flexible, modular, maintainable and cost effective architecture. Product should be architected to manage scalability and flexibility to be deployed across various network topographies. Hence all the components should be oriented to run on web based platform enhancing their capability as independent functions.
For ease of customization and commercialization try  to use open source framework and separate technology with open source as much as possible so that it can be easily replaceable by any other framework in future if required.
2. Faster development speed: Faster development speed is mantra for research based product. Use faster development techniques to get it in market faster. It is advisable to follow modular architecture which helps to develop all modules independently in parallel. Develop modules as web services, separate service layer and use shared resources like database, web servers etc.
3. Distinguish Factors: To stand high between all existing competitors in your product area, it is challenging tasks to build intelligence in your product to distinguish it from other available products. With extensive research in product area, build intelligence in your product by capturing domain specific, technology specific best design practices.
4. Lack of Product development Processes and Methodology: In case of lack of maturity level in product development methodology, try to select right set of people with research background, solid technical background, management background in your team to develop your product end to end.
Business Challenges:
5. Challenges in attracting revenue potential: It is always very challenging to get funds approved for any product development.  One needs to convince management with solid revenue potential with product idea. It is beneficial to conduct research to find out importance of web product in today’s world and prepare solid business case to prove that your product has a potential for repeatable business and continuous demand in future.
6. Lack of early adopter customers: it is always a very challenging to attract customer initially. The amount of business you get is highly proportional to the amount of effort that you put in marketing your business. First it is important to figure out who are right customers for your product and then define a attractive revenue model for customer to buy and serve the needs of customer. It could be license, or license + services, along with support -- there are alternate transaction or revenue share models which have found wide acceptance.


Vidya Sachin Abhyankar
Product Manager- Web 2.0 Research Lab, SETLabs
vidyas_abhyankar@infosys.com

Continue reading "Web Product Development Challenges" »

March 25, 2010

Multimodal accessibility

Humans are usually equipped with 5 senses, and almost 90% of the interactions they engage in involve more than 2 of the senses they possess. Web since its inseption has been always attempting to create interactions which increasingly resemble real human interactions. As result web can not be considered as a place to have unimodal interaction. In fact multi modal interaction possibilities make the web an attractive proposition for diverse communities in diverse situations. Though it all started as a primerilyly text based interface soon graphics and voice found their place in the revolution and web pages started looking more fancy and talkative. On other side of the scene advancements in assistive technologies empowered differently abled users and made web interactions possible for most of the mankind. users want to be online using different access devices like cell phones and web TV. they want to use varied input modalities like hand writing and voice. They expect text, graphic and voice all merged as a single output.

 Any organization aspiring to reach all the customer base can no longer restrict itself to use of uni modal interactions. As a obvious effect, multimodality of any interface we think of is a necessity and not an option.

W3C the parent organization of web is already developing standards for facilitating production of applications having multiple input and output modalities. The initiative is known as Multimodal Interaction Activity. In subsequent posts we will try to understand use cases for multimodal interactions and W3C Multimodal Interaction Framework.

Shrirang Prakash Sahasrabudhe
Accessibility Specialist- SETLabs
Shrirang_s@infosys.com

Continue reading "Multimodal accessibility" »

March 4, 2010

The 25th Annual International Technology & Persons with Disabilities Conference

Attendee registration is open for the 25th Annual International Technology & Persons with Disabilities Conference http://csunconference.org/index.cfm?EID=80000218&p=149. The conference is happening between March 22-27, 2010 at Manchester Grand Hyatt Hotel, San Diego, CA. There are a number of very interesting sessions scheduled for CSUN.

Rakesh Babu, PhD student of the University of North Carolina, Greensboro is conducting a session at CSUN titled Accessibility and Usability of Web-Enhanced Instruction: Blind Student’s Challenges in Online Assessments ( http://csunconference.org/index.cfm?EID=80000218&p=151&page=scheduledetail&LCID=3886&ECTID=0) on March 24th.

February 4, 2010

ISO 23026 -2006

According to an estimate by the WorldWideWebSize there are over 50 billion web pages on the WWW today. Unless these web pages (and in effect websites) are properly engineered, managed and maintained over their life cycle, there are bound to be several frustrated web users out there who are unable to accomplish their goals and objectives when visiting a website.

Continue reading "ISO 23026 -2006" »

September 15, 2009

Web Accessibility

Web Accessibility means providing equal access and hence equal opportunity to the people with physical disabilities. Web, as it has evidently become an important resource in our activities makes it imperative that it remains accessible so that the users with disabilities can use it with same ease as people without disabilities. With governments enjoining new laws and guidelines to make the Web accessible, Web Accessibility is no more a discretion.

W3C’s WAI is one such effort to improve accessibility of the Web. WAI with the help of other interest groups formed guidelines and techniques to help different component of web accessibility. The major components of Web Accessibility are: Web Content (web page or web applications), Authoring (HTML Editors), Content interaction tools (user-agents, screen readers etc.) and Evaluation tools.

The guidelines recommended for these different components are as follows:
1. User Agent Accessibility Guidelines – Provides guidelines for the User Agent developers so that the user agents are accessible.

2. Authoring Tool Guidelines – Provides guidelines for the Authoring Tool Developers to build tools which generate accessible content. For example: ATAG 1.0 , ATAG 2.0

3. Web Content Guidelines – Provides guidelines and solutions for making the Web content more accessible and usable across devices. For example: WCAG1.0, WCAG2.0

4. EARL – provides a standard way for generating test results by the Accessibility evaluation tools.


The guidelines specified are basic, individual countries can have their custom accessibility standards. For example: 508, DDK etc.  

Though these Guidelines, address various issues of Web Accessibility, they all essentially relate to technical specifications (HTML, CSS, SVG, and XML etc.) which are used to develop the Web content.

Vijaya Bhaskar Peddinti
vijayabhaskar_p01@infosys.com
Technical Specialist
Web 2.0 Research Lab - SETLabs

August 27, 2009

AMCIS 2009

The 15th Americas Conference on Information Systems (AMCIS), 2009 was recently held in San Francisco. The conference was themed as 'The Golden Gate to the Future of IS (Information Systems)'. As part of the research group at Infosys, from the Web 2.0 Research Lab Dr. Jai Ganesh and I chaired three mini-tracks in this conference. These were:

  1. Web 2.0 and Collaborative Value Creation
  2. Business Impact of Virtual Worlds and Web 2.0
  3. Web Accessibility - Challenges, Regulation and Reality

The overall conference was replete with variety of parallel tracks including those on Design Theory,  Analytical Modeling and Simulation, Decision Support Systems, diffusion of IT, eBusiness and eCommerce, Enterprise Systems all the way to Social issues of IT.

Continue reading "AMCIS 2009" »

July 21, 2009

Learning from CISTM 2009

I was recently involved in couple of panel discussions on Web Accessibility as well as Web 2.0 and Cloud Computing at the CISTM 2009 held at MDI Gurgaon. Sharing some quick learning from those discussions.

The first discussion focused on whether Web 2.0 poses challenges for web accessibility. The panelist were Rahul Gonsalves, a trained designer and a usability and accessibility enthusiast; Dinesh Kaushal, a lead developer at an accessibility solutions organisation and himself a developer of screen reader enabled for Indian languages; and yours truly. I believe that the topic was interesting for most people attending the conference. I say this because although the discussion started at a late hour and went on till almost 7:30 PM, we had a good audience which was very inquisitive and interacted actively. We primarily discussed what and why of web accessibility, some business considerations for making the web accessible and legal regulations around the world that necessitated equal accessibility for everyone. The participants were so involved in the discussion that we barely touched upon the aspects of Web 2.0 posing a challenge to accessibility.

Continue reading "Learning from CISTM 2009" »

July 15, 2009

Web accessibility lawsuits- some past cases

Further to my post about Accessibility complaint against Arizona state university, Let us walk through some past incidences of accessibility lawsuits.

The accessibility case that introduced me to web accessibility was Sydney Olympics accessibility complaint by Bruce Maguire. This complaint was lodged under Disability Discrimination Act of Australia. The reason for the complaint was poor accessibility of the SOCOG website. SOCOG lost the case, reinforcing that  accessibility is essential and is not a difficult thing to achieve.

America online had to face the lawsuit due to inaccessibility of the client software which was required for accessing AOL services. The case got settled out of court when AOL promised accessibility of the AOL client software

Another lawsuit which made headlines is the complaint by NFB against the famous retailer Target.com. This case is particularly important because it is for the first time any court has formally accepted that the web is a place of public accommodation and Americans with disabilities act (ADA) applies even to websites and web properties. Target lawsuit became a class action suit. According to the NFB, the ruling sets a precedent establishing that retailers must make their Web sites accessible to the blind under ADA.

Web has come way ahead since inception and so are the disability laws, but it is really ironic that lawsuits are required to compel companies to build accessible websites. Laws are means to achieve justice but companies need not wait till someone sues them. Accessibility should neither be an afterthought nor a compulsion, but should come as a natural practice of web software life cycle.

 

Shrirang Prakash Sahasrabudhe
Accessibility Specialist- SETLabs
Shrirang_s@infosys.com

 

July 11, 2009

Web 2.0 and Web Accessibility Panel Discussions in CISTM 2009

The seventh annual Conference on Information Science Technology and Management (CISTM 2009) is being held from 13th until 15th July 2009 at the Management Development Institute, Gurgaon, India. The schedule of the event is available here. We will be chairing two panel discussions at this conference.

Dr. Jai Ganesh will be chairing a discussion on 'Web 2.0 and Cloud Computing'. In this discussion we will explore the complementarities as well as points of intersection between the principles of Web 2.0 and Cloud Computing.  

I will be leading another discussion on "Does Web 2.0 Challenge Accessibility?" This discussion will bring to fore some of the challenges posed by Web 2.0 technologies for people with different abilities and debate the adequacy of regulations as well as technological solutions to address these challenges. Other panelists for this discussion include an independent accessibility consultant as well as a leading technology developer in the field of screen readers.

July 10, 2009

Accessibility law suits, it is not only about websites.

Most of the times web accessibility law suits turn out to be an eye catcher and eye opener for online businesses. But disability laws like American with disabilities act have much wider scope and much deeper penetration than it is usually perceived. Unlike Target and AOL accessibility law suits, recent complaint by NFB against Arizona state university have a flavor of accessibility of devices used by visually challenged users. Plans of the university to deploy Amazon’s Kindle DX electronic reading device as a means of distributing electronic textbooks to its students have triggered the case. Kindle is capable to read aloud the books to users who are blind, but surprisingly enough it lacks necessary accessibility provisions which will allow blind users to access the functionality in first place. The menus on the device are not accessible making it is impossible for blind users to utilize the text to speech capability.

Darrell Shandrow, a blind student pursuing a degree in journalism at ASU, said:
“Not having access to the advanced reading features of the Kindle DX—including the ability to download books and course materials, add my own bookmarks and notes, and look up supplemental information instantly on the Internet when I encounter it in my reading—will lock me out of this new technology and put me and other blind students   at a competitive disadvantage relative to our sighted peers. While my peers will have instant access to their course materials in electronic form, I will still have to wait weeks or months for accessible texts to be prepared for me, and these texts will not provide the access and features available to other students. That is why I am standing up for myself and with other blind Americans to end this blatant discrimination.”

This clearly indicates that accessibility requirements need to be catered end to end. Accessibility features and provisions can be of help only if they are implemented in usable and accessible manner. There is nothing called partly accessible, it is either completely accessible or it is inaccessible.

 

Shrirang Prakash Sahasrabudhe
Accessibility Specialist- SETLabs
Shrirang_s@infosys.com

 

June 5, 2009

National Workshop on Web Accessibility

A National Workshop on Web Accessibility is being organised by the Centre for Internet and Society (www.cis-india.org) from June 5 to 7, 2009 in Bangalore. The workshop is meant for web developers and aims at highlighting the importance of creating accessible web sites.

The workshop intends to educate web developers, from public as well as of private sector organisations, on how to incorporate accessibility features into existing web sites as well as those being newly developed.

The workshop will comprise of conceptual as well as hands-on sessions. The trainers are specialists in various aspects of web accessibility. The main focus will be on WCAG 2.0 guidelines. The participants are expected to have good knowledge of HTML, XML, CSS, etc.

More information on program schedule, speakers and registration details are available at http://www.cis-india.org/events/national-workshop-on-web-accessibility-june-2009

June 4, 2009

Infosys iProwe: Product for Web Accessibility Assessment and Remediation

A few months back, we launched Infosys iProwe, which is a product in the domain of Web Accessibility Assessment & Remediation. Infosys iProwe is a patent pending Web Accessibility Assessment and Remediation Product from the Web 2.0 Research Lab. About 20% of the global population suffers from some form of disability and a large part of the World Wide Web (about 97%) is not accessible to this disabled population.  Disabilities include visually challenges users of screen readers, hearing impaired users, low-vision users, color-blind users, users with a motor disability, and users with cognitive disabilities. iProwe leverages built-in intelligence to automatically analyse the accessibility issues of Websites and recommends remedial measures to make Websites accessible. iProwe provides comprehensive assessment and recommendation at the same time drastically reducing the time, cost, effort as well as errors involved in assessing and fixing Web accessibility issues. iProwe is targeted at enterprises with an online presence and it enables enterprises to achieve enhanced Web accessibility for differently-abled users better, faster and cheaper. iProwe is an enabler for enterprises planning their Web Accessibility strategy from dimensions including legal, economic as well as corporate social responsibility. Accessibility is a requirement from a legal perspective (legal regulations enforcing accessibility requirements), economic perspective (large potential customer base) as well as a corporate social responsibility perspective.

May 12, 2009

Assistive technology- What’s that?

 

“I am 100% blind and I really love programming in c++”, “Internet browsing and reading online books is my favorite pastime; doesn’t matter whether I can move my hands”, “’BLACK’ is the best movie I have ever seen; and you are reading it right; I am visually challenged”.
People get astonished and sometimes they find it hard to believe when they hear/read such statements. The credit goes to the technologies which make all this possible for differently able individuals popularly known as Assistive Technologies (ATs). These technologies comprise hardware, software or combination of both. They assist user to accomplish the tasks which otherwise the user can not perform. They augment the gap between required abilities and abilities which user have. They adapt the system to the constrained operating environment user is living with.
As a concept Assistive technology was always known to us, the most ancient assistive technology Mankind uses is magnification glass. But focus of this note is ATs relevant to human machine interaction.
Here are some examples:
·        screen readers, programs those transform the GUI into stream of audio
·        screen magnifiers, programs to enlarge the information on the screen
·        sip and puff devices to control the mouse movement using breath
·        Voice recognition software to accept spoken input
·        On screen keyboards
·        Touch screens
Usually these products are highly sophisticated and technology intensive.
Author: Shrirang_s@infosys.com

 

 

January 19, 2009

Web Accessibility is a multi component solution- part 2

  1. Web accessibility guidelines: along with advent and proliferation of websites W3C initiated “web accessibility initiative”. Under which they came up with certain guidelines to be followed during creation of websites. "WCAG1.0" was a first set of guidelines. As the web evolved, WCAG1.0 started falling short and W3C came up with “WCAG2.0”, and recently became a world wide accepted standard. WCAG guides developers to incorporate accessibility in the applications they build.

     

  2. Web content: anything that’s available online is a web content. It can range from simple text to highly interactive application. It includes text, graphics, animations, streaming audio, streaming video and documents available for download. HTML, css, java script, flash, are some of the technologies used to create and present the web content. These technologies provide certain intrinsic features to facilitate accessibility. For example HTML specifies “alt” attribute for IMG tag. Developers can convey the purpose or description of the graphical content by providing succinct value to “alt” attribute. It is developer’s responsibility to utilize these features and techniques in most usable way to achieve accessible web presence

     

  3. Authoring tools: they are the tools used to create web Content. WYSIWYG editors for HTML and XML, tools to produce multimedia, softwares to transform content to web formats, site publication and management tools all come under authoring tools umbrella. These tools need to support and facilitate production of accessible content. These tools should encourage and guide the content writer to utilize accessibility features of content creation technologies.

     

  4. User agent: it is a peace of a code responsible for retrieving and rendering content. It includes browsers; plugins for particular media etc. user agent bear the responsibility of supporting accessibility features and standards in a uniform manner. User agents need to facilitate job of assistive technologies by exposing right information about user interface elements and events in real-time.

     

  5. Assistive technologies (AT): they are the hardware, software of combination of both which enable differently able individuals to interface with computer and internet. ATs compensate for user’s disability for example screen reader transforms visual content into audio stream and delivers it to the user through speakers. Braille display renders text information in braille format which can be perceived using touch. voice recognition softwares allow user to interact with computer using voice. These technologies sit between web application and the user. ATs can work effectively if and only if web application exposes required information in a standard way. Content exposes certain information which is accessed by ATs and transformed into a form useful to the user. ATs must upgrade themselves with newer and advance content production formats in order to support respective accessibility APIs.

     

If you carefully look at the tight coupling between the components of accessible web, it is evident that every component must do it’s job in the most effective and efficient manner. If any link in the model is broken the inevitable effect is accessibility problem.

 

Shrirang Prakash Sahasrabudhe

 

shrirang_s@infosys.com

January 9, 2009

Web Accessibility is a multi component solution- part 1

Further to Chandan’s blog post Understanding Web Accessibility, where he has succinctly described the concept of web accessibility, let us try to answer the question How can enterprises can achieve the objective of accessible web for all.

 

Web accessibility is not the sole responsibility of the web designer or developer or user agent. Accessibility is a multi component solution. It is a merger between web accessibility guidelines, web content, authoring technologies/tools, user agent and assistive technologies. Let us understand each component in brief.

 

Shrirang Prakash Sahasrabudhe

shrirang_s@infosys.com

December 6, 2008

Interrelationship between Accessibility and Usability

As mentioned my previous blog posting, Web Accessibility means that people with disabilities can use the Web - they can perceive, understand, navigate and interact with the Web. Usability on the other hand means that products – IT or otherwise – are easy to learn, easy to memorize, can be used without making errors and allow the users to accomplish tasks efficiently.  

Continue reading "Interrelationship between Accessibility and Usability" »

November 30, 2008

Web Accessibility and the Law - EU Part I

Continuing our discussion on the laws dealing with web accessibility around the world, this blog focuses on the legislations and regulations in the European Union (EU). It should be mentioned here that the European countries have been one of the key funding contributors (besides US and Japan) to the Web Accessibility Initiative (WAI) of the Worldwide Web Consortium (W3C). To that extent there is an acceptance of the recommendations of the WAI across the EU. But the efforts are not limited only to passive contribution to the WAI. The EU has independently adopted several recommendations from councils and commissions set up especially to address the issue of an inclusive global information society.

Continue reading "Web Accessibility and the Law - EU Part I" »

November 27, 2008

Web Accessibility and the Law - India

I would really like to thank Vijay Krishnamani for his comment on the previous post. Essentially, because it helped me dedicate this post only for the law in India. Vijay, thanks for your interest in the post and also for your question. Let me start with a short answer – To the best of my knowledge, we do not yet have a law that governs web accessibility in India. The last I know of is that a working group has been set up, in Jan 2007, under the Department of Information Technology, Ministry of Communication and Information Technology. The stated objective of this committee is to formulate “Policy and Procedures for Implementation of Web Accessibility Standards”. This is the only public information available.

Continue reading "Web Accessibility and the Law - India" »

November 25, 2008

Web Accessibility and the Law - UK

Another country that has taken web accessibility and regulations thereof very seriously is UK. The primary regulation there, the Disability Discrimination Act (DDA) dates back to 1995. The Part III of this act that is applicable to websites and requires them to be accessible came into effect on 1st October 1999. In the same year the Disability Rights Commission Act came into effect to set up the Disability Rights Commission (DRC), which was responsible for “elimination of discrimination against disabled persons” besides other tasks. This commission actively promoted the Part III of the DDA 1995.

Continue reading "Web Accessibility and the Law - UK" »

November 23, 2008

Web Accessibility and the Law - Australia

Continuing from the previous post, if the changes in the US regulatory systems have been more visible as a consequence of the Target vs. NFB case, the laws in other parts of the world have actually been in existence for quite some time now.

Australia has particularly taken a lead in institutionalizing regulations / guidelines that make web accessibility a mandatory requirement. This blog lists some of these regulations.

Continue reading "Web Accessibility and the Law - Australia" »

November 22, 2008

Web Accessibility and the Law - US

A few days back Chandan Gokhale’s blog discussed web accessibility and the efforts of the World Wide Web Consortium (W3C) via its Web Accessibility Initiative (WAI). It briefly touched upon the Web Content Accessibility Guidelines (WCAG 1.0 and 2.0 (draft 11)).  While the WCAG is an independent effort being driven by W3C, there are several legal / regulatory efforts being steered in countries around the world. This blog discusses some of these regulatory requirements for web accessibility in the US.

Continue reading "Web Accessibility and the Law - US" »

November 21, 2008

Economics of Web Accessibility - Part 2

The above statistics underline the fact that the size of the market for accessible technology is larger than commonly perceived. This is important because for disabled users, everyday actions can often be completed more quickly and efficiently on the web. Moreover of the 54 million Americans with a disability, 4 in 10 are online and these users tend to spend more time logged on and surfing the Internet than nondisabled users. The number of people with disabilities – and income to spend – is likely to increase as the likelihood of having a disability increases with age, and the overall population is aging. As the world’s population is living longer, there are more older adults using the Internet and physical impairments hamper web usage for users. Moreover over 20% of the EU will be over 65 years of age and the number of people aged 60 or over will double in the next 30 years. This will account for a large section of population which needs effective and efficient access to the Web.

 

November 20, 2008

Economics of Web Accessibility - Part 1

A large part of the World Wide Web is not accessible to a large section of the disabled population (about 18-20% of the global population suffers from some form or disability). About 97% of websites fail to meet the most basic requirements for accessibility. These are rather shocking numbers given the fact that the Web plays an important role and offers significant benefits for people with disabilities. The below statistics highlights the economics behind making the World Wide Web Accessible to the physically challenged population:

 

 

Continue reading "Economics of Web Accessibility - Part 1" »

November 17, 2008

Understanding Web Accessibility

Starting this week, we will be addressing the area of Web Accessibility - organized in multiple blog entries – to address various facets of Web Accessibility.  In this posting, we will look at the big picture, the meaning of Web Accessibility and its relevance for promoting Equal Opportunity.  

Continue reading "Understanding Web Accessibility" »

Subscribe to this blog's feed

Follow us on

Infosys on Twitter