As we all are aware that no one is appointed to check the web. The web is an unbolted standard; a web is a place where the person has no limitations on his postings and is free to choose the content of their choice. The web is not restricted to limited people, but everyone is free to use it. The main strength of the web is its decentralization and it openness. But it is unable to work without few types of formats that are used for upgrading the information. That is when the (W3C) the World Wide Web consortium came into existence.
The World Wide Web
Here's a summary of the most recent face to face meeting of
the W3C Multimodal Interaction Working Group.
Summary of the W3C Multimodal Interaction Working Group and
Ink Subgroup Face to Face meetings
December 9-11 (main meeting) 12-13 (ink subgroup meeting)
Washington DC, USA
hosted by Cisco
This was the fourth face to face meeting of the Multimodal
Interaction Working Group. There were 33 attendees from 23 organizations.
This meeting also included a smaller follow-on meeting of the subgroup of
the MMI group which is working on an ink
The W3C Multimodal Interaction (MMI) Working Group [1] held a face to
face meeting in Hawthorne, New York, September 22-24, 2004, hosted by
IBM. There were 33 attendees from 23 organizations. This note
summarizes the results of the meeting.
The MMI meeting was colocated with a meeting of the Voice Browser
Working Group [2]. We took advantage of this to hold a joint meeting
with the Voice Browser group about the evolving Voice Browser V3
architecture and its relationship to multimodal architectures.
The MMI meeting focused on MMI
Now Showing at the YUI Theater: WCAG 2.0 Presentation
Read More
2007-08-16 Learn how the WCAG 2.0 Working Draft differs from WCAG 1.0, get shortcuts for using WCAG 2.0, and hear answers to common questions on W3C WAI's work in Shawn Henry's presentation to the Yahoo! User Interface Developer Network. Shawn also addresses the role of browsers and authoring tools in Web accessibility, and combining standards and usability techniques to optimize accessibility. See video with audio and slides, and text transcript. (2007-08-16)
July 2007 Update on WCAG
When developing web sites, making them as accessible as possible is crucial, both to people with different kinds of disabilities as well as to all kinds of different devices, web browsers and screen readers etc.
Why? Out of respect for the user, while making the web site available to as many users as possible.
You need to be aware of the fact that the web site will not look the same to all visitors, not all UAs handle CSS and other things. The solution isn’t to code in HTML 3.2 and avoid using CSS and JavaScript, since that’s just plain dumb.
Web Content Accessibility Guidelines 2.0 (WCAG 2.0) covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech difficulties, photosensitivity and combinations of these. Following these guidelines will also make your Web content more accessible to the vast majority of users, including some older users.
When the W3C’s Web Accessibility Initiative recently put one of their technical recommendations, a new version of the Web Content Accessibility Guidelines or WCAG 2.0, in Last Call Working Draft status with a deadline of only a few weeks, it caused outrage in the web community. First there was Joe Clark’s article To Hell with WCAG 2.0, soon followed by various other initiatives, and suddenly, the deadline for public review was extended from May 31 to June 22. But don’t consider it a victory, for while we may have more time, there is still no
RSS/XML