Web Accessibility a Universal Goal!

By: Mr. Nidal A. Bousaleh

Introduction:

Over the last decay, an increase number of research were conducted to determine ways Information Technology can assist in meeting special needs to ensure universal accessibility. Findings to date suggest that by being more knowledgeable about accessibility issues, Web designers and developers are able to accommodate end users with special needs.

As we enter the knowledge age, it is no longer acceptable that people with limited or no vision are on their own when it comes to accessing the web, nor those with mobility problems are on their own when it comes to use a hardware. To ignore

website accessibility raises moral, business, and legal issues. It is morally wrong to discriminate

against disabled people on the web simply through lack of thought, consideration, or awareness. Many business web sites designed without considering accessibility issues result in loss of revenue. Some countries, such as the US, UK, and Australia has introduced legislation that requires organizations to adhere to accessibility issues.

In June 1999, the Disability Discrimination Act (1999) has been used to fight for access rights in

Australia. The 2000 Olympic Site Games, jointly developed by Sydney Organizing Committee of the Olympic Games (SOCOG) and IBM was found inaccessible to the blind users, and SOCOG was fined A$ 20,000 [1].

The purpose of this paper is raising awareness among web designers and developers, to achieve universal web accessibility goal. The paper looks at the disability issues and the existing assistive technologies or methods used by disabled users to assist them in accessing the web.

Afterwards, the paper reviews guidelines for good web site design, and provides analysis for designing an accessible website. Furthermore, the paper highlights on the challenges and gaps in the web accessibility area.

Literature Review:

Two years ago, a Conference was held in ?London? and attended by representatives of commerce, industry, government, and the IT Sector aiming to raise awareness of the potential benefits of assistive technology to disabled users. The outstanding number of speakers highlighted through number of cases how technology can transfer lives. ?Sue Bassoon? a Business Development Manager at IBM said: ?IBM?s goal is to have a speech recognition system as good as the human ear by 2010? [2].

The objectives of this literature is two folds: (1) explain how a particular disability (e.g.

visual impairment, mobility restriction, hearing impairment) can impede the use of the web, and what can be done to accommodate special needs; and (2) show how web designers and developers can construct accessible web sites to end users with disabilities, such as visual or hearing impairment.

(1) Disability Issues

The section begins with a descriptive part concerning disabled user functional limitation

and dependence on assistive technologies.

A- Vision Issues:

A web user who has no sight (totally blind) is likely to use the screen reader technology to reads a load the content of the web page. Other web users, with partial or poor sight need to be able to enlarge the text on web page using a screen magnifier.

B- Mobility Issues:

A web user may have mobility problems as a result of an accident or disease such as:(loss of limb, Injury, or aging process). The technologies used by users with mobility problems are:

- Sticky Keys: For users with one finger typing.

- Filter Keys: Ignores repeated strokes for people with hand tremors.

- Mouse Keys: Permits moving pointer with numeric keypad.

- Serial Key: Permits access to alternatives for mouse and keyboard functions such as Foot Mouse.

- Eye gaze: A video camera that racks eye movement as the user look at an on screen keyboard. It is customizable as how long a key must be looked at to be recorded. When system has identified the key looked at the symbol appears and the user look at next key.

C- Hearing Issues:

A web user may be deaf or experiencing problems with hearing due to the natural aging process. To assist those users the audio or video need to be translated to the ASL (American Sign Language) language of the deaf, in which certain signs represent words.

(2) Design for Accessibility

In the above section, the paper provided readers with a general knowledge about disability issues, disabled users, and the existing assistive technologies. This section is intended for web designers and developers, because it provides them with tips and guidelines on ways to design a good and accessible website. There are two main aspects

to take into account:

I- Look and Feel

Web designers need to present a user friendly interface that addresses specific ability needs. The designer should be able to describe ways disabled users interact with a website, and how they move through the pages and how they achieve their goals. Below, are helpful tips that designers need to consider when designing an accessible website.

- Web Designers & Developers; should follow the four principles of visual organization in the process of designing a website which are: Proximity, Alignment, Consistency, and Contrast.

- Web Designers & Developers; must avoid using HTML tables to control the layout, instead use style sheets.

- Web Designers & Developers; should use legible fonts, and font size to allow disabled users to easily change them from the browser interface.

- Avoid poor color contrast in your design, and do not use color for meaningful description.

- Avoid the use of animation, and flash which may affect users with photosensitive epilepsy.

- Avoid using Frames because it can pose problems for technology used by some disabled users.

- Try not to use graphics for menu and button forms.

- Avoid hiding menu items (using DHTML or applets)

II- Content

Web designers should organize content in a way that can provide ease of use and simplicity. Below, are helpful tips that designers need to consider when designing an accessible website:

- Use a clear language, and write short sentences.

For example, a web page should provide blind users with a short summary of what they can find. A Search Functionality is important because a blind person can?t scan the page, and will generally trust first result he/she receives.

- Add Accessible tags and attributes by using rich set of tags to enhance accessibility. For instance, an ALT tag is used to provide a text equivalent for images within a website. The

ALT text description is what the screen reader or talking browser will read to the blind users .

- Use clear link descriptions, and include links that a user can click to skip repetitive regions of the page.

- Ensure the pages are usable when scripts, applets, or style sheets are turned off or not

supported.

- All audio and video content should contain captions, transcription, and descriptive information.

Analysis:

It is estimated that 20% of the population has some kind of disability. The internet opens

a new window of opportunity and independence to disabled users from reading news to banking to conducting business. For example, by using the screen reader technology a blind user can listen to the latest newspaper published electronically. Similarly, a user with mobility problem who can not go out shopping to buy a newspaper, nor use a

keyboard or mouse independently, can rather use the eye tracking software that allow people to use a computer with nothing more than eye movement.

Nowadays, organizations are asking designers to make their web sites accessible and for

good reasons. First of all, the more people who can use a site, the more potential it can

generate. Online stores, in particular have a great deal to gain, since many people with

functional limitation problems, find it much easier to shop online. Most Web designers

are not personally opposed to the concept of making web sites accessible to people with

disabilities. In fact most accessibility errors on web sites are the result of ignorance. A large proportion of web designers and developers have simply never thought about accessibility issues. A small proportion of web designers (4%) do not understand the needs of users with disabilities; another (46%) understand some of the needs of users with disabilities. While only (26%) of designers understand most of the needs of users

with disabilities and can accommodate them [3].

The Challenges and Gaps of Web Accessibility:

In this section, we highlight the challenges and the requirements posed by user needs, to

access the web. We argue the need for a new approach to address accessibility issues, and

include it in each and every web project life cycle.

Web Accessibility a Universal Goal!
Web Accessibility a Universal Goal!By: Mr. Nidal A. Bousaleh Introduction: Over the last decay, an increase number of research were conducted to de...

Web Accessibility a Universal Goal!
Web Accessibility a Universal Goal!By: Mr. Nidal A. Bousaleh Introduction: Over the last decay, an increase number of research were conducted to de...

Web Accessibility a Universal Goal!
Web Accessibility a Universal Goal!By: Mr. Nidal A. Bousaleh Introduction: Over the last decay, an increase number of research were conducted to de...

Begin Your Quest To Find The Best Universal Remote Controls
Begin Your Quest To Find The Best Universal Remote ControlsBy Tony Shipp We live in an era where universal remote controls are a necessity for ...

To See the Network - Anasil Version 3 Released
To See the Network - Anasil Version 3 ReleasedBy Bartosz Lewandowicz Anasil 3 - new functions: analysis of multi-component networks, network ma...

Why is this? Is it the lack of technical solutions to meet their needs ? absolutely not! You will hear today that there are new technological solutions to address even most extreme form of disability. Is it cost?

Again it is not! Some technical solutions, cost nothing at all, and already exist in software. So, What then? Is it that web applications are being developed that present challenges to accessible design? Is it lack of knowledge and skills to meet their needs?

There does seem a general lack of awareness of web accessibility issues. Web Designers and Developers, need to have a better approach to tackle the problem in each phase of the web development process. For example, during the requirement analysis phase a web developer must define the target audience of the site, and should take into account people with a combination of disabilities. In addition to this, during prototyping phase a web designer must have the knowledge to accommodate end users with special needs, and also the skills to meet their expectations.

Moreover, testing the web site using different

technologies is critical for a successful web site, to ensure it meets the accessibility

standards and user requirements [4].

Therefore, in each phase of the web development process, accessibility plays an important role. Accessibility and Usability should be completely embedded in web design and development cycles from beginning to end.

The future looks bright for web accessibility. It promises to educate web designers and developers about accessibility issues, through training courses offered at universities.

Conclusion:

The Internet offers independence and freedom. But, this independence and freedom is limited to certain users. Many websites are not created with accessibility issues in mind.

Whether it is the Web Designer lack of knowledge or ignorance, they exclude a segment of users that in many ways benefit from the internet [5].

In short, designing accessible websites does not require an enormous effort or time. It simply, requires commitment, and accountability, to achieve a universal goal.

Reference:

[1] Duckworth D. (2003).Web Accessibility in Australia. Retrieved June 18, 2005, from

http://www.tonneten.net/mt/blog/archieves/000024.htm

[2] Conference (2003). IT ? The Universal Enabler, London. Retrieved May 28, 2005

from http://www.stcsig.org

[3]Web Accessibility Survey (2003). Retrieved June 24, 2005 from

http://cita.rehab.uiuc.eduu/survey/2002-2003-web-practices.html

[4] Volpon A. (2002). The Life cycle ofWeb Accessibility. Retrieved June 24, 2005 from

http://www.evolt.org/article/The_Lifecycle_of_Web_Accessibility/20/50376/

[5] Bohman P. (2003). Introduction to Web Accessibility. Retrieved June 24, 2005 from

http://www.webaim.org/intro

[6]Mertz D. (2000). Tips: Design for accessible Web sites. Retrieved June 22, 2005 from

http://www-128.ibm.com/developerworks/web/library/w-mertz.htm

Article Source:
http://www.articlecity.com/articles/computers_and_internet/article_4045.shtml

Donate to Phrabatnampu

.

Web 2.0? Or Is It More Like Web 16.0?

By: Stone Julian

It has become difficult to keep up with the meanings of all the new phrases and terms generated by modern technology. One of the most commonly used phrases on the world wide web (www) today is “Web 2.0.” It seems like every web solutions company is using this phrase to sell its stuff. So to the average Joe who’s not a geek, what is “Web 2.0″?

Well according to Wikipedia, the free online encyclopedia?

“[T]he phrase Web 2.0 can refer to a perceived second generation of web-based communities and hosted services ? such as social-networking sites, wikis, and folksonomies [collaborative tagging schemes] ? which aim to facilitate creativity, collaboration, and sharing between users. The term gained currency following the first O’Reilly Media Web 2.0 conference in 2004. Although the term suggests a new version of the World Wide Web, it does not refer to an update to any technical specifications, but to changes in the ways software developers and end-users use webs. According to Tim O’Reilly, ‘Web 2.0 is the business revolution in the computer industry caused by the move to the Internet as platform, and an attempt to understand the rules for success on that new platform.’ Some technology experts, notably Tim Berners-Lee, have questioned whether one can use the term in a meaningful way, since many of the technology components of ‘Web 2.0′ have existed since the early days of the W!

eb.”

There is no doubt the www has advanced significantly since inception, but there really is no new version of the www. It is simply much more useful to the everyday person.

However, if we counted each major innovation as a whole number and each minor revision as a tenth, we would already be into double digits. So why are we calling it “Web 2.0″?

If you have seen the latest Die Hard movie, or ever bought software for your computer, you will understand why we are not in Web 2.0. Even if we call it Die Hard 4.0 or MS Office 2007, it’s still basically the same movie or tool. So what we are really experiencing now is more like Web 16.0.

If you have an in-depth, honest conversation with your web designers, they will tell you that Web 2.0 is a myth. So to explain how we got to Web 16.0, here’s a history of the most significant events on the www.

WEB 0.1 — 1958 ? SAGE ? Radar systems are first networked

WEB 0.2 — 1960 ? Packet switching is first created

WEB 1.0 ? EMAIL ? “A New Way to Send Unsolicited Mail Is Born”

Although the exact history of Email is a tad murky, it is generally accepted that it appeared in 1965, and was created so that people accessing a mainframe could communicate with each other. This was the first step in the interconnection of people, facilitating almost instant communication at no cost to the user.

WEB 1.1 — 1967 ? Markup language is created

WEB 1.2 — 1969 ? ARPA ? A link is established between computers

WEB 1.3 — 1696 ? ARPA Net ? First packet-switched network created

WEB 2.0 ? WYSIWYG ? “What You See Is What You Get (sometimes)”

With the invention of WYSIWYG in 1970, users could now be presented with a basic display of what their finished product would look like, as they were working on it. This removed the need to memorize complex code.

WEB 2.1 — 1970 ? ASP ? First Application Service Provider (SAAS)

WEB 2.2 — 1970 ? Style sheets are created

WEB 2.3 — 1971 ? @ is created to separate hosts and users

WEB 2.4 — 1973 ? TCP/IP is created to simplify networking

WEB 2.5 — 1973 ? First connection to another country established

WEB 2.6 — 1974 ? The term “Internet” is adopted

WEB 2.7 — 1976 ? X.25 ? The first network standard is approved

WEB 2.8 — 1978 ? International packet switching service created

WEB 3.0 ? USENET? “The Black Market of the Internet”

Usenet was established in 1980 to offer mail and file transfers as well as give personal users access to news. Usenet is in fact a large network of servers all in communication with each other; a user posts something to the local server and that item is passed along to the other servers. Usenet was a major turning point because users could finally have an open conversation with anyone on the net, without needing to specifically know the user (unlike Email). The downside is that with a sometimes un-policed net capable of file transfers, the Usenet of today is a haven for piracy of all types, where anything you can imagine is accessible.

WEB 3.1 — 1979 ? Email is made available to personal computer users, millions of Nigerian Princes suddenly need public help

WEB 4.0 ? REAL TIME CHAT ? Going Outside Deemed “Obsolete”

Real-Time Chat was created in 1980 following users’ frustrations with Usenet articles sometimes taking 24 hours to be updated. This signaled a turning point: online conversations became instant, albeit isolated into segregated groups.

WEB 4.1 — 1980 ? First ISPs created providing dialup internet

WEB 4.2 — 1981 ? TCP/IP becomes a standard

WEB 4.3 — 1981 ? US/Europe/Canada/Hong-Kong/Australia connect

WEB 4.4 — 1983 ? TCP/IP becomes the only standard

WEB 4.5 — 1983 ? First wide area network using TCP/IP operational

WEB 4.6 — 1985 ? FTP ? The File Transfer Protocol is created

WEB 4.7 — 1988 ? IRC ? Internet Relay Chat is created

WEB 4.8 — 1988 ? Bulletin Board Systems and Forums created

WEB 5.0 ? HTML/HTTP/Web Pages ? “It Has Begun?”

Around 1980, many researchers were using the internet, but they had no single way to create/display “documents” (web pages). Physicist Tim Berners-Lee and his colleagues needed a simple system for creating/displaying documents, but found that existing systems were too commercial, platform-specific or complicated for the average user. So they created their own relatively simple system, consisting of browsing software called “WorldWideWeb,” a protocol for transmitting the information (HTTP) and a document annotation convention called “Hyper Text Markup Language” (HTML). This meant anyone could now create web pages using their simple language.

WEB 5.1 — 1989 ? Images can now be animated, oh the horror!

WEB 5.2 — 1990 ? The network now covers the entire world (publicly)

WEB 6.0 ? Search ? “Did You Mean: Google?”

Before 1990, there was no way to find a page; you had to know the specific location. Around 1991, search engines began indexing (storing) the content they found, giving users the ability to search for a page even if they didn’t know the page’s location.

WEB 6.1 — 1991 ? DNS ? Dynamic Naming System is created

WEB 6.2 — 1991 ? The first text-based browser is created

WEB 7.0 ? DHTML ? “Because Non-Scrolling Text Is Boring”

The web was static until Dynamic HTML (DHTML) was created. DHTML introduced client-side scripting, allowing authors to include code in their web pages that performed an action upon being downloaded onto a user’s computer.

Web Page Design Software
Web Page Design SoftwareBy Kent Pinkerton Web page design software is software applications that help users create a Web site. Web design softw...

Tips For Using Photoshop when Creating a Web Site
Tips For Using Photoshop when Creating a Web SiteBy Gabriel J. Adams Photoshop is a wonderful tool for creating web sites. It allows even a no...

WebPages - What Are They
WebPages - What Are TheyBy Jesse Miller Internet Web pages are an important tool for communicating. Many internet web pages are being added by ...

Benefits of Free Directory Submissions
Benefits of Free Directory SubmissionsBy Kori Smith Have you ever realized the importance of submitting your website to Web directories? Direct...

Finding An Affordable Web Site Hosting Plan
Finding An Affordable Web Site Hosting PlanBy: Cliff Posey Jr Finding an affordable web site hosting plan is a must for new businesses or established ...

It goes a long way to making the web more personalized.

WEB 7.1 — 1993 ? The first graphics based browsers are created

WEB 7.2 — 1993 ? Screen casts are first created

WEB 7.3 — 1994 ? Wikis are created; Britannica begins holding its breath

WEB 7.4 — 1994 ? The World Wide Web Consortium is formed

WEB 7.5 — 1994 ? CSS ? Cascading Style Sheets created

WEB 8.0 ? ONLINE DIARIES ? “Teens Reportedly Misunderstood”

Online diaries were first created in 1994 as a means for people to store their diaries online for personal or public reading. Writers could now reach almost anyone worldwide at practically no cost, and everyone could create editorials on whatever subjects they liked, without fear of censorship.

WEB 8.1 — 1996 ? The first social bookmarking site created

WEB 9.0 ? RANKED RESULTS ? “The Online Popularity Contest”

Search engine results helped find things, but many of the results were useless or had nothing to do with the keywords used. As of 1996, search results started to be ranked based on a multitude of things, like how popular a page is. This made searching faster and easier, and significantly less painful.

WEB 9.1 — 1996 ? Flash is created, whole websites can now be animated

WEB 9.2 — 1997 ? The term “Blog” is adopted

WEB 10.0 ? HIRED BLOGGERS ? “Wow Isn’t Product X Great!”

As of 1997, personal diaries began to evolve to what became known as “blogs.” Many corporate websites and personal homepages had (and still do have) news sections, these were traditionally updated manually in a back-end system. With the advent of blogs, the commercial sector jumped in, seeing a new marketing medium.

WEB 10.1 — 1998 ? The first audio news site is created

WEB 10.2 — 1999 ? The first web-based operating system is created

WEB 11.0 ? RSS ? “Newspapers Deemed Obsolete”

Really Simple Syndication (RSS) was created due to the lack of a universal feed format. The creation of RSS means that users could now “subscribe” to feeds containing video, audio, text, or graphics. Users no longer had to trawl the web for new information, they could “subscribe” to a feed and have it sent to them directly.

WEB 12.0 ? REMOTE SCRIPTING ? “Waiting For 4 Seconds Now History!”

Remote scripting allows scripts running inside a browser to exchange information with a server, so that scripts could be triggered locally, processed remotely and have information returned directly to the browser. This made the web faster and easier to use, and removed the need to refresh the page for simple tasks like sorting.

WEB 12.1 — 2001 ? Blogs evolve from online diaries

WEB 13.0 ? PODCASTING ? “Now Everyone Can Avoid Listening To You By Choice Rather Than Circumstance!”

Podcasting originated as a portmanteau of the iPod® and broadcasting, although “portable on demand broadcasting” has now become the widely-accepted definition. Originally Podcasting was created to allow individuals to distribute their own radio shows, but it has become popular for a wide variety of things, from educational materials to the latest gaming news. Podcasting opens up distribution of audio content to anyone with a server, with users “subscribing” to the RSS feeds that appeal to them.

WEB 13.1 — 2002 ? Folksonomy is created, giving rise to “tags”

WEB 14.0 ? VIDEO PODCASTING ? “Web-Based One-Sided Conversations”

Shortly after Podcasting became popular, video Podcasting was created as a means to send the equivalent of TV episodes to users. Though similar to podcasting, the content was not limited to just “TV episodes”. Video Podcasting opens up the video medium so that making a TV show is possible for anyone.

WEB 15.0 ? VOIP ? “High Tech, Dodgy Sounding Free Calls”

With the Voice Over Internet Protocol, telephone audio is sent over the internet, rather than a traditional phone line. This removes almost all cost involved, and also removes the need to have a physical phone line. What this means for consumers is calling becomes much simpler, easier and significantly cheaper.

WEB 16.0 ? SAAS ? “The Industry Makes a SaaS of Itself.”

Software as a Service (SaaS) is just a new term for a concept that has been around since the dawn of the internet (ASP from 1970). SaaS refers to using a piece of software run/provided through the internet, and instead of paying a large one-off purchase price, you “rent” the software for as long as needed. So while SaaS is the buzzword of the day, the concept is decades old.

..The CONCLUSION?

So if you follow the basic rule that each total upgrade is a new “.0″ then we are nowhere near Web 2.0. The story is really one of falling price, increasing reliability and bandwidth, coupled with ubiquitous access.

Simply put, “Web 2.0″ is just shorthand for the development process outlined above. Bottom line, the web really becoming what the web really always should have been.

Article Source:
http://www.articlecity.com/articles/computers_and_internet/article_4046.shtml

Donate to Phrabatnampu

.