Found issues:

[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 5 problems that require human review have been found.

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

• Check it through the whole document

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

• Check it through the whole document

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

• Check it through the whole document

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.

• Check it through the whole document

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

• Check it through the whole document

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

3.2 Create documents that validate to published formal grammars.

• Missing language identifier for this document

3.3 Use style sheets to control layout and presentation.

• Use style sheets to control layout and presentation

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

• There are no header elements in this document.

7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.

• This pages uses auto-refresh which can make the page difficult to read for some people (1)
• • Line 3: <meta http-equiv="refresh" content="0;url=http://www.uc3m.es/portal/page/portal/inicio">

7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.

• This page uses auto-redirect which can make the page difficult to read for some people (1)
• • Line 3: <meta http-equiv="refresh" content="0;url=http://www.uc3m.es/portal/page/portal/inicio">

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

• There are no header elements "h1-h6" nor paragraph elements "p" in the page.

3.6 Mark up lists and list items properly.

• Verify that all lists are properly marked up ("ul","ol","dl" elements).

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

• Verify that all the quotations have been properly marked up ("q","blockquote" elements).

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

• Verify that there is no blinking content in the page.

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

• Verify whether there is no moving content in the page, or there is a way to freeze the movement.

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

• Check it through the whole document

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

• Check it through the whole document

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

• Check it through the whole document

13.4 Use navigation mechanisms in a consistent manner.

• Check it through the whole document

[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. 1 automatically detected problem and 9 problems that require human review have been found.

4.3 Identify the primary natural language of a document.

• Missing lang attribute: The primary language of this document has not been set (1)
• • Line 1: <html>

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.

• Check it through the whole document

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

• Specify the expansion of each abbrevation or acronym in a document where it first occurs

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

• Check it through the whole document

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

• Check it through the whole document

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

• Check it through the whole document

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

• Check it through the whole document

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

• If the page is part of a document collection, verify that you provide information about the collection.

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

• Check it through the whole document

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

• Verify that a means to skip over multi-line "ASCII art" is provided.