|
Today, there is so much competition between web hosting providers. They all pretty much offer the same services and the costs are fairly competitive. Who has the advantage? It depends on which 'top ten' web hosting list that you look at. I haven't found one 'top ten' list that rates a website hosting provider on accessibility and usability. After all, the services that they provide are open to everyone, including those with disabilities and the aging population. Or, are they? In the next few years, the baby boomer generation will consist of people who use computers and are not afraid of technology. Here are SimplyRaydeen.com's picks for the 'Top Ten' web hosting providers, using one easy test for accessibility and usability – the Functional Accessibility Evaluator (FAE). “Following the best practices in developing web resources not only improves accessibility for people with disabilities, but also improves interoperability, giving everyone the benefit of having more options for accessing and using those resources.” -- http://fae.cita.uiuc.edu/about/ Web Accessibility/Usability: Top 10 Web Hosting ProvidersThe Top 10 Web Hosting Providers were rated on 'Navigation & Orientation' and 'Text Equivalents' (% Pass) -- FatCow Hosting is #1-- FatCow cares about its customers, providing navigation tools and orientation information in pages that will maximize web accessibility and usability. .............................................................................................................. Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Almost Complete | 92 | 3 | 3 |
|---|
Text Equivalents | Partially Implemented | 50 | 25 | 25 |
|---|
Scripting | Complete | 100 | 0 | 0 |
|---|
Styling | Partially Implemented | 50 | 0 | 50 |
|---|
HTML Standards | Partially Implemented | 50 | 0 | 50 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 84 | 0 | 15 |
|---|
Text Equivalents | Almost Complete | 50 | 50 | 0 |
|---|
Scripting | Complete | 100 | 0 | 0 |
|---|
Styling | Complete | 100 | 0 | 0 |
|---|
HTML Standards | Complete | 100 | 0 | 0 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 80 | 7 | 11 |
|---|
Text Equivalents | Partially Implemented | 75 | 0 | 25 |
|---|
Scripting | Almost Complete | 75 | 25 | 0 |
|---|
Styling | Complete | 100 | 0 | 0 |
|---|
HTML Standards | Complete | 100 | 0 | 0 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 80 | 7 | 11 |
|---|
Text Equivalents | Partially Implemented | 25 | 50 | 25 |
|---|
Scripting | Almost Complete | 0 | 100 | 0 |
|---|
Styling | Not Implemented | 33 | 0 | 66 |
|---|
HTML Standards | Almost Complete | 50 | 50 | 0 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 80 | 3 | 15 |
|---|
Text Equivalents | Partially Implemented | 25 | 50 | 25 |
|---|
Scripting | Complete | 100 | 0 | 0 |
|---|
Styling | Partially Implemented | 83 | 0 | 16 |
|---|
HTML Standards | Complete | 100 | 0 | 0 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 73 | 11 | 15 |
|---|
Text Equivalents | Partially Implemented | 50 | 0 | 50 |
|---|
Scripting | Complete | 100 | 0 | 0 |
|---|
Styling | Complete | 100 | 0 | 0 |
|---|
HTML Standards | Complete | 100 | 0 | 0 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 73 | 11 | 15 |
|---|
Text Equivalents | Partially Implemented | 25 | 50 | 25 |
|---|
Scripting | Complete | 100 | 0 | 0 |
|---|
Styling | Partially Implemented | 50 | 0 | 50 |
|---|
HTML Standards | Partially Implemented | 0 | 50 | 50 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 69 | 11 | 19 |
|---|
Text Equivalents | Partially Implemented | 25 | 50 | 25 |
|---|
Scripting | Almost Complete | 50 | 50 | 0 |
|---|
Styling | Not Implemented | 33 | 0 | 66 |
|---|
HTML Standards | Partially Implemented | 0 | 50 | 50 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 65 | 11 | 23 |
|---|
Text Equivalents | Partially Implemented | 50 | 25 | 25 |
|---|
Scripting | Complete | 100 | 0 | 0 |
|---|
Styling | Complete | 100 | 0 | 0 |
|---|
HTML Standards | Complete | 100 | 0 | 0 |
|---|
Evaluation Results by Best Practices Main Category Category | Status | % Pass | % Warn | % Fail |
|---|
Navigation & Orientation | Partially Implemented | 65 | 11 | 23 |
|---|
Text Equivalents | Partially Implemented | 50 | 25 | 25 |
|---|
Scripting | Almost Complete | 50 | 50 | 0 |
|---|
Styling | Partially Implemented | 50 | 0 | 50 |
|---|
HTML Standards | Complete | 100 | 0 | 0 |
|---|
Best Practices Rules Summary Used: http://fae.cita.uiuc.edu/about/rules/ Navigation & Orientation Text Equivalents Scripting Styling HTML Standards
2.2 Making Content Understandable and Navigable Content developers should make content understandable and navigable. This includes not only making the language clear and simple, but also providing understandable mechanisms for navigating within and between pages. Providing navigation tools and orientation information in pages will maximize accessibility and usability. Not all users can make use of visual clues such as image maps, proportional scroll bars, side-by-side frames, or graphics that guide sighted users of graphical desktop browsers. Users also lose contextual information when they can only view a portion of a page, either because they are accessing the page one word at a time (speech synthesis or braille display), or one section at a time (small display, or a magnified display). Without orientation information, users may not be able to understand very large tables, lists, menus, etc. Principles - At the top are four principles that provide the foundation for Web accessibility: perceivable, operable, understandable, and robust. See also Understanding the Four Principles of Accessibility.
|