TAW Logo
TAW 3.0 (2/9/10 2:10 PM) Validation conform to WAI guidelines, W3C Recommendation 5 May 1999
Testing outcome: http://www.upm.es/institucional
Go to the Fundación CTIC website
Test summary outcome
AutomaticHuman review
Priority 10100
Priority 2071
Priority 3015
1. Human review2. Human review3. Human review1. Human review2. Human review3. Human review1. Human review2. Human review3. Human review1. Human review2. Human review3. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review 1. Human review

Menú Accesibilidad

2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review 2. Human review1. Human review1. Human review2. Human review1. Human review2. Human review
1. Human review1. Human review2. Human review
1. Human review2. Human reviewPolitécnica Virtual
1. Human review2. Human reviewTienda UPM

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 100 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).

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. No automatically detected problems and 71 problems that require human review have been found.

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.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.

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.

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

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).

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.

9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.

10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.

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

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

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. No automatically detected problems and 15 problems that require human review have been found.

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.

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.7 If search functions are provided, enable different types of searches for different skill levels and preferences.

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.