TAW Logo
TAW 3.0 (12/1/07 7:43 PM) Validation conform to WAI guidelines, W3C Recommendation 5 May 1999
Testing outcome: http://gplsi.dlsi.ua.es/congresos/iwwua07/
Anar a la pāgina principal de Fundaciķn CTIC
Test summary outcome
AutomaticHuman review
Priority 1042
Priority 21430
Priority 3620
3. Automatic1. Human review2. Human review3. Human review 2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review 3. Human review3. Automatic2. Human review2. Automatic2. Human review2. Automatic
1. Human review
1st International Workshop on
Web Usability and Accessibility
3. Human review1. Human review3. Automatic3. Human review2. Human review1. Human review1. Human review2. Human review
To be held in conjuntion with the
2. Human review8th International Conference on Web Information Systems Engineering
1. Human review2. Human reviewIWWUA 2007 1. Human review
December 3-7, 2007
Nancy, France
1. Human review
1. Human review2. Human review2. Automatic[WISE'07] 3. Human review3. Automatic3. Human review2. Human review1. Human review1. Human review2. Human review
1. Human review2. Human review2. Automatic[DLSI - UA] 1. Human review2. Human review2. Automatic[UPV] 1. Human review2. Human review2. Automatic[POLIMI]
3. Human review3. Automatic2. Human review2. Human review2. Automatic
3. Human review3. Automatic3. Human review2. Human review1. Human review1. Human review2. Automatic2. Automatic
1. Human review
ˇ About the workshop
1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review
ABOUT THE WORKSHOP
According to recent studies an estimated 90% of Web sites and applications suffer from usability and/or accessibility problems. As user satisfaction has increased in importance, the need for usable Web applications has become more critical. To achieve Web usability for a Web product (e.g., a service, a model, an application, a portal), the Web artifacts' attributes must be clearly defined. Otherwise, assessment of usability is left to the intuition or the responsibility of people who are in charge of the process. In this sense, usability models (describing all the usability sub-characteristics, their attributes and the relationship among them) should be built and Usability Evaluation Methods (UEMs) should be used during requirements, design and implementation stages based on these usability models. Another major challenge in industry today is to make the Web more usable for everybody, including those with disabilities. Since there is no general method for evaluating the usability and accessibility of a Web application in all circumstances, the workshop can contribute to clarify several concerns such as the following: 2. Automatic
  1. What are the shortcomings of existing approaches for Web usability and accessibility evaluation?
  2. How the Web application usability can be decomposed into a set of measurable attributes? For example, the ISO 9126 standard decomposes usability into five sub-characteristics. The standard does not specify how these sub-characteristics can be effectively and efficiently measured.
  3. What is the suitability of existing UEMs to evaluate Web interfaces?
  4. What are the specific usability criteria for Web artifacts? To which extent do they depend on the family of applications under consideration?
  5. How can we broaden accessibility evaluation to involve people with disabilities? Does it provide a more effective solution than merely conforming to accessibility standards?
  6. What are the strengths and weaknesses of tools for automated evaluation? For example, many accessibility tools are based on accessibility guidelines, but vary in their interpretation of guidelines. So these results still require human judgment.

1. Human review
wwwadm [at] dlsi.ua.es   |   Last updated: 09:11 28/05/2007 | Accesses since 2007-05-25: 1. Human review2. Human reviewComptador

Found issues:

Priority 1[WAI] Priority 1 accessibility issues. A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents. No automatically detected problems and 42 problems that require human review have been found.

1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.

2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup.

4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

5.1 For data tables, identify row and column headers.

5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.

6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.

6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.

6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.

8.1a Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies, if functionality is important and not presented elsewhere.

11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.

14.1 Use the clearest and simplest language appropriate for a site's content.

Priority 2[WAI] Priority 2 accessibility issues. A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents. 14 automatically detected problems and 30 problems that require human review have been found.

3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.

3.5 Use header elements to convey document structure and use them according to specification.

7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).

11.2 Avoid deprecated features of W3C technologies.

12.3 Divide large blocks of information into more manageable groups where natural and appropriate.

2.2a Ensure that foreground and background color combinations for images provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.

3.1 When an appropriate markup language exists, use markup rather than images to convey information.

3.2 Create documents that validate to published formal grammars.

3.3 Use style sheets to control layout and presentation.

3.6 Mark up lists and list items properly.

3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).

6.4 For scripts and applets, ensure that event handlers are input device-independent.

7.3 Until user agents allow users to freeze moving content, avoid movement in pages.

8.1b Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.

11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.

13.1 Clearly identify the target of each link.

13.2 Provide metadata to add semantic information to pages and sites.

13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).

13.4 Use navigation mechanisms in a consistent manner.

Priority 3[WAI] Priority 3 accessibility issues. A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents. 6 automatically detected problems and 20 problems that require human review have been found.

4.3 Identify the primary natural language of a document.

5.5 Provide summaries for tables.

2.2b Ensure that foreground and background color combinations for text provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.

4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.

9.4 Create a logical tab order through links, form controls, and objects.

9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.

10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.

11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)

13.5 Provide navigation bars to highlight and give access to the navigation mechanism.

13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.

13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

13.9 Provide information about document collections (i.e., documents comprising multiple pages.).

14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.

14.3 Create a style of presentation that is consistent across pages.

13.10 Provide a means to skip over multi-line ASCII art.