Tags |
|
|
Links |
|
|
Added for You - The Future of Web Accessibility
More people are turning away from watching TV and following other pursuits. In a recent report, it was stated that in the USA, the viewing figures for news channels ABC, CBS, NBC and Fox had dropped by 2.5 million, compared to the previous year, 2006.The internet is one of the places that people are going to for their entertainment and enjoyment of their leisure time. In an edition of Internet Business News, it was reported that in the UK, 70% of people in the 16-20 age group would rather surf the internet than watch early evening TV.From the period 2000 to 2006, the number of people on the internet has doubled to one billion people (source: budd.com.au). Further growth will be at a slower rate, as people wait for the implementation of broadband in their
* Alternative accessible versions will become the norm - Historically speaking, separate accessible versions were frowned on for both ethical and business reasons (see Separate text-only version? No thanks! for more on this ( http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/text-only.shtml )). However, for the first time usability and accessibility are coming head-to-head with each other and rich interactive interfaces often can't be made fully accessible. In this instance, a separate version will have to be provided (but only after all other routes have been exhausted).
* User generated content is likely to offer poor accessibility - Content created by users is becoming more and more commonplace on the web. This kind of content is being created at such a rapid rate that it's going to be impossible to police it for accessibility.
* JavaScript, PDF & Flash will no longer be thought of as 'evil' - In WCAG 1.0, web managers and developers were basically told that their websites shouldn't rely on any of these three technologies. WCAG 2.0 on the other hand doesn't st
One of the most misunderstood aspects about small business loans is how long they take to arrange. There are some types of commercial financing which can be obtained in just a few days while other small business loans are likely to take up to 60 days or more.SMALL BUSINESS LOANS: COMMERCIAL MORTGAGEThe primary example of small business loans that are likely to take the longest to arrange is a commercial real estate loan. Even with the quickest variation of a commercial mortgage, small business owners should expect this to take 45 to 60 days (up to nine months is a possibility with some traditional banks for certain commercial mortgages). One aspect that causes this type of business loan to take so long is the requirement for a real estate
It's been seven years since the W3C released the first version of the web content accessibility guidelines (WCAG 1.0). Since then, accessibility has slowly but surely turned up on the radar of web managers in most large organisations.
The benefits of accessibility are pretty well known too - a quick Google search for web accessibility benefits returns over 37 million results! Because of this, more and more large profile websites have offered better and better accessibility as the years have gone by. There's still a long way to go but the progress over the past few years is highly visible and indeed positive.
Web 2.0
Web 2.0 refers to the ‘next generation’ of websites and online applications. Websites using Web 2.0 technologies have started to spring up all over the Internet, and are likely to exponentially increase in number over the next few years. Although the term itself, Web 2.0, has become a bit of a buzzword, there's no doubt that Web 2.0 is here and is becoming more and more commonplace.
Two characteristics of Web 2.0 include AJAX and user generated content. Many websites are beginning to embrace these two concepts, causing never-before seen accessibility issues...
1. AJAX
AJAX, or Asynchronous JavaScript and XML isn't actually a technology in itself. Rather, it's a technique for using a number of existing technologies to create highly interactive web applications.
AJAX-based web pages require support for JavaScript, but most assistive technologies can now support (some types of) JavaScript. The main accessibility concern isn't therefore the use of JavaScript, but rather the way in which JavaScript is used to cause on-the-page changes.
The Amazon diamond search ( http://www.amazon.com/gp/gsl/search/finder/104-8020741-7498364?ie=UTF8&productGroupID=loose%5Fdiamonds ), for example, showcases a great example of using AJAX to create an interactive and highly useful interface. It basically uses click-and-drag sliders to allow users to broaden and narrow a wide range of filtering criteria. The page then automatically updates to show how many results conform to the users' selected criteria.
The Amazon application offers fantastic usability for many web users. But it's totally impossible for screen reader and keyboard-only users to use, and very difficult for any screen magnifier user to use. The solution? A separate simplified accessible version, which Amazon have actually provided (ironically, this separate version hasn't been built to high levels of accessibility, although it could easily have been).
2. User generated content
Another concept of Web 2.0 is content generated by users. Blogs and wikis are becoming more and more commonplace, as stand-alone websites or within an organisation's website. Currently, many large organisations struggle to control the accessibility of their content due to the large number of content editors - how are they going to cope with users contributing content as well as employees of the organisation?
Websites such as Blogger, Flickr and YouTube are totally reliant on user generated content, in the form of blogs, photos and videos respectively. How can these websites control the accessibility of their content? Content is created at such a rapid speed that it wouldn't be reasonable (or even possible) for any of these websites to police that content for accessibility.
Image- and photo-driven websites, such as Flickr, could request users insert alternative descriptions, either of their own or other people's photos. Ensuring this actually happens across the site though will be difficult to impossible to achieve.
Other websites, including those of large organisations, are attempting to build up communities by allowing users to upload images, post comments and generally interact with each other and the site. Will the website owners provide a mechanism to ensure this content is produced accessibly? Can they?
WCAG 2.0
The second version of the web content accessibility guidelines (WCAG) from the W3C is currently in final working draft and is soon to be released officially.
One of the main differences between version 2.0 and 1.0 of the guidelines is that WCAG 2.0 is technology-neutral. This means that the guidelines themselves are far more vague and open to interpretation than previously.
Predictions
There are three major factors that will shape web accessibility in the future: AJAX, user generated content and WCAG 2.0. The increased prominence of these factors could lead to some of the following:
* Accessibility will become less and less guideline-driven - With the advent of new technology (such as AJAX), and the technology-neutral and vague nature of the new W3C guidelines (WCAG 2.0), accessibility is becoming less and less guideline driven. This means that employing accessibility experts is going to become more and more important for organisations as interpreting these guidelines correctly will become more and more difficult.
* Alternative accessible versions will become the norm - Historically speaking, separate accessible versions were frowned on for both ethical and business reasons (see Separate text-only version? No thanks! for more on this ( http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/text-only.shtml )). However, for the first time usability and accessibility are coming head-to-head with each other and rich interactive interfaces often can't be made fully accessible. In this instance, a separate version will have to be provided (but only after all other routes have been exhausted).
* User generated content is likely to offer poor accessibility - Content created by users is becoming more and more commonplace on the web. This kind of content is being created at such a rapid rate that it's going to be impossible to police it for accessibility.
* JavaScript, PDF & Flash will no longer be thought of as 'evil' - In WCAG 1.0, web managers and developers were basically told that their websites shouldn't rely on any of these three technologies. WCAG 2.0 on the other hand doesn't st
I’ve been a designer and advertising consultant for over 35 years. I’ve seen my share of business cards and I have a few words addressed to those companies that might benefit from my expertise. I’m not talking to those professionals that are categorized by attorneys, physicians, dentists, insurance agents and accountants. You’ve seen their cards that are traditional black raised print on a white uncoated cover stock paper. They probably also contain a tastefully, understated logo, or credential, of their profession. To those of you I say, that’s barely adequate.Instead, I’m speaking to the average company that has a basic logo and spent between $50 and $100 on a thousand stock cards that a local ‘Quick Print,’ provides. They often have a plethora of sample borders, back
1. AJAX
AJAX, or Asynchronous JavaScript and XML isn't actually a technology in itself. Rather, it's a technique for using a number of existing technologies to create highly interactive web applications.
AJAX-based web pages require support for JavaScript, but most assistive technologies can now support (some types of) JavaScript. The main accessibility concern isn't therefore the use of JavaScript, but rather the way in which JavaScript is used to cause on-the-page changes.
The Amazon diamond search ( http://www.amazon.com/gp/gsl/search/finder/104-8020741-7498364?ie=UTF8&productGroupID=loose%5Fdiamonds ), for example, showcases a great example of using AJAX to create an interactive and highly useful interface. It basically uses click-and-drag sliders to allow users to broaden and narrow a wide range of filtering criteria. The page then automatically updates to show how many results conform to the users' selected criteria.
The Amazon application offers fantastic usability for many web users. But it's totally impossible for screen reader and keyboard-only users to use, and very difficult for any screen magnifier user to use. The solution? A separate simplified accessible version, which Amazon have actually provided (ironically, this separate version hasn't been built to high levels of accessibility, although it could easily have been).
2. User generated content
Another concept of Web 2.0 is content generated by users. Blogs and wikis are becoming more and more commonplace, as stand-alone websites or within an organisation's website. Currently, many large organisations struggle to control the accessibility of their content due to the large number of content editors - how are they going to cope with users contributing content as well as employees of the organisation?
Websites such as Blogger, Flickr and YouTube are totally reliant on user generated content, in the form of blogs, photos and videos respectively. How can these websites control the accessibility of their content? Content is created at such a rapid speed that it wouldn't be reasonable (or even possible) for any of these websites to police that content for accessibility.
Image- and photo-driven websites, such as Flickr, could request users insert alternative descriptions, either of their own or other people's photos. Ensuring this actually happens across the site though will be difficult to impossible to achieve.
Other websites, including those of large organisations, are attempting to build up communities by allowing users to upload images, post comments and generally interact with each other and the site. Will the website owners provide a mechanism to ensure this content is produced accessibly? Can they?
WCAG 2.0
The second version of the web content accessibility guidelines (WCAG) from the W3C is currently in final working draft and is soon to be released officially.
One of the main differences between version 2.0 and 1.0 of the guidelines is that WCAG 2.0 is technology-neutral. This means that the guidelines themselves are far more vague and open to interpretation than previously.
Predictions
There are three major factors that will shape web accessibility in the future: AJAX, user generated content and WCAG 2.0. The increased prominence of these factors could lead to some of the following:
* Accessibility will become less and less guideline-driven - With the advent of new technology (such as AJAX), and the technology-neutral and vague nature of the new W3C guidelines (WCAG 2.0), accessibility is becoming less and less guideline driven. This means that employing accessibility experts is going to become more and more important for organisations as interpreting these guidelines correctly will become more and more difficult.
* Alternative accessible versions will become the norm - Historically speaking, separate accessible versions were frowned on for both ethical and business reasons (see Separate text-only version? No thanks! for more on this ( http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/text-only.shtml )). However, for the first time usability and accessibility are coming head-to-head with each other and rich interactive interfaces often can't be made fully accessible. In this instance, a separate version will have to be provided (but only after all other routes have been exhausted).
* User generated content is likely to offer poor accessibility - Content created by users is becoming more and more commonplace on the web. This kind of content is being created at such a rapid rate that it's going to be impossible to police it for accessibility.
* JavaScript, PDF & Flash will no longer be thought of as 'evil' - In WCAG 1.0, web managers and developers were basically told that their websites shouldn't rely on any of these three technologies. WCAG 2.0 on the other hand doesn't st
PPC publishing means that you are improving the chances of getting more traffic but one part of it also deals with what you are going to do with that traffic. It is a general assumption that traffic that flows through a search engine is targeted and that the visitors already know what they are looking for. Yet the reality is that most people have only a vague idea of what they wish to buy when they are searching for information on the internet. For example, a search for "basketball" could mean anything from the ball itself to any accessory or personality associated with that sport. So what happens if such a vague search creates more traffic for you?Your first task is to ensure this traffic is not wasted. That is why even a pure ecommerce site must have some good content
2. User generated content
Another concept of Web 2.0 is content generated by users. Blogs and wikis are becoming more and more commonplace, as stand-alone websites or within an organisation's website. Currently, many large organisations struggle to control the accessibility of their content due to the large number of content editors - how are they going to cope with users contributing content as well as employees of the organisation?
Websites such as Blogger, Flickr and YouTube are totally reliant on user generated content, in the form of blogs, photos and videos respectively. How can these websites control the accessibility of their content? Content is created at such a rapid speed that it wouldn't be reasonable (or even possible) for any of these websites to police that content for accessibility.
Image- and photo-driven websites, such as Flickr, could request users insert alternative descriptions, either of their own or other people's photos. Ensuring this actually happens across the site though will be difficult to impossible to achieve.
Other websites, including those of large organisations, are attempting to build up communities by allowing users to upload images, post comments and generally interact with each other and the site. Will the website owners provide a mechanism to ensure this content is produced accessibly? Can they?
WCAG 2.0
The second version of the web content accessibility guidelines (WCAG) from the W3C is currently in final working draft and is soon to be released officially.
One of the main differences between version 2.0 and 1.0 of the guidelines is that WCAG 2.0 is technology-neutral. This means that the guidelines themselves are far more vague and open to interpretation than previously.
Predictions
There are three major factors that will shape web accessibility in the future: AJAX, user generated content and WCAG 2.0. The increased prominence of these factors could lead to some of the following:
* Accessibility will become less and less guideline-driven - With the advent of new technology (such as AJAX), and the technology-neutral and vague nature of the new W3C guidelines (WCAG 2.0), accessibility is becoming less and less guideline driven. This means that employing accessibility experts is going to become more and more important for organisations as interpreting these guidelines correctly will become more and more difficult.
* Alternative accessible versions will become the norm - Historically speaking, separate accessible versions were frowned on for both ethical and business reasons (see Separate text-only version? No thanks! for more on this ( http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/text-only.shtml )). However, for the first time usability and accessibility are coming head-to-head with each other and rich interactive interfaces often can't be made fully accessible. In this instance, a separate version will have to be provided (but only after all other routes have been exhausted).
* User generated content is likely to offer poor accessibility - Content created by users is becoming more and more commonplace on the web. This kind of content is being created at such a rapid rate that it's going to be impossible to police it for accessibility.
* JavaScript, PDF & Flash will no longer be thought of as 'evil' - In WCAG 1.0, web managers and developers were basically told that their websites shouldn't rely on any of these three technologies. WCAG 2.0 on the other hand doesn't st
Athletes get top dollars because they use coaches. So can you who want to write a book to get the good word out to help others, to illustrate you are the savvy expert in your field, and to create ongoing monthly income that boosts your speaking or coaching business. Number 1-10 on a separate piece of paper. On a scale from 1 to 10, 10 being high rate each of the following statements: Not applicable 5 Don't agree 1 2 3 Somewhat agree or 5 for not applicable 4 5 6 7 8 Totally agree 9 10 Score 1 to 10 on each point below. Then add them up to see if you are ready for Bookcoaching. __1. I will learn the latest from a book coach professional on self-publishing that frees me from assuming it'
WCAG 2.0
The second version of the web content accessibility guidelines (WCAG) from the W3C is currently in final working draft and is soon to be released officially.
One of the main differences between version 2.0 and 1.0 of the guidelines is that WCAG 2.0 is technology-neutral. This means that the guidelines themselves are far more vague and open to interpretation than previously.
Predictions
There are three major factors that will shape web accessibility in the future: AJAX, user generated content and WCAG 2.0. The increased prominence of these factors could lead to some of the following:
* Accessibility will become less and less guideline-driven - With the advent of new technology (such as AJAX), and the technology-neutral and vague nature of the new W3C guidelines (WCAG 2.0), accessibility is becoming less and less guideline driven. This means that employing accessibility experts is going to become more and more important for organisations as interpreting these guidelines correctly will become more and more difficult.
* Alternative accessible versions will become the norm - Historically speaking, separate accessible versions were frowned on for both ethical and business reasons (see Separate text-only version? No thanks! for more on this ( http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/text-only.shtml )). However, for the first time usability and accessibility are coming head-to-head with each other and rich interactive interfaces often can't be made fully accessible. In this instance, a separate version will have to be provided (but only after all other routes have been exhausted).
* User generated content is likely to offer poor accessibility - Content created by users is becoming more and more commonplace on the web. This kind of content is being created at such a rapid rate that it's going to be impossible to police it for accessibility.
* JavaScript, PDF & Flash will no longer be thought of as 'evil' - In WCAG 1.0, web managers and developers were basically told that their websites shouldn't rely on any of these three technologies. WCAG 2.0 on the other hand doesn't st
In part 1 of this article series, we described the staging area and the ETL process of a data warehouse architecture. In the present and following article we shall describe the presentation area of the data warehouse. The term presentation is used to denote the fact that this is the area, where data are presented to its Customers (the business analysts). There is no globally acceptable standard on the development of the data warehouse presentation area. Two major approaches have prevailed:· the dimensional datawarehouse approach (proposed by R. Kimball)· the corporate information factory (CIF) approach (proposed by B. Inmon) Kimball approach According to the Kimball approach, the presentation area is made of a number of
* Alternative accessible versions will become the norm - Historically speaking, separate accessible versions were frowned on for both ethical and business reasons (see Separate text-only version? No thanks! for more on this ( http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/text-only.shtml )). However, for the first time usability and accessibility are coming head-to-head with each other and rich interactive interfaces often can't be made fully accessible. In this instance, a separate version will have to be provided (but only after all other routes have been exhausted).
* User generated content is likely to offer poor accessibility - Content created by users is becoming more and more commonplace on the web. This kind of content is being created at such a rapid rate that it's going to be impossible to police it for accessibility.
* JavaScript, PDF & Flash will no longer be thought of as 'evil' - In WCAG 1.0, web managers and developers were basically told that their websites shouldn't rely on any of these three technologies. WCAG 2.0 on the other hand doesn't stipulate this, and rightly so as most assistive technologies can now support these technologies.
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.added4u.com/article/86658/added4u-The-Future-of-Web-Accessibility.html">The Future of Web Accessibility</a>
BB link (for phorums):
[url=http://www.added4u.com/article/86658/added4u-The-Future-of-Web-Accessibility.html]The Future of Web Accessibility[/url]
Related Articles:
Obtaining a Private Investigator License
Sometimes You Have To Spend To Earn
Increase Sales With eCommerce 2.0
Bookmark it:
|