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

• Verify that text equivalent for image is useful
• If describing the image will add information, you need to provide a description of the image with a valid longdesc attribute (9)
• • Line 22: <img src="../index_ar/logoberm.gif" alt="Portada web" width="110" height="30" style="margin-left: 70%; margin-top: -5%" />
  • Line 57: <img src="../politica/w340.png" alt="Validado HTML 4.01!" width="54" height="19" />
  • Line 57: <img src="../valid-xhtml11-blue.png" alt="Validada XHTML 1.1" width="54" height="19" />
  • Line 59: <img src="../index_ar/css.jpg" alt="Validado CSS!" width="54" height="19" />
  • Line 62: <img src="a1.jpg" alt="Icono de conformidad con el Nivel A, de las Directrices de Accesibilidad para el Contenido Web 1.0 del W3C-WAI" width="54" height="19" />
  • Line 62: <img src="taw_2_AA.png" alt="Validado por TAW3" width="78" height="19" title="Validado por TAW" />
  • Line 85: <img src="../valid-xhtml11-blue.png" alt="Las p&aacute;ginas con este logo est&aacute;n validadas para XHTML 1.1" width="54" height="19" />
  • Line 85: <img src="../politica/css.png" alt="Validado estilos CSS" width="54" height="19" />
  • Line 85: <img src="../politica/taw_2_AA.png" alt="Validado TAW3" width="78" height="19" />

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

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.

• Ensure this document can be read without style sheets (3)
• • Line 17: <link href="../index_ar/informa_estilos.css" rel="stylesheet" type="text/css" />
  • Line 22: <img src="../index_ar/logoberm.gif" alt="Portada web" width="110" height="30" style="margin-left: 70%; margin-top: -5%" />
  • Line 33: <div class="lateralizq" style="float:left ">

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

12.4 Associate labels explicitly with their controls.

• This form control is not explicitly associated with a label. (1)
• • Line 26: <input name="q" type="text" id="searchField" value="borre y escriba" size="18px" maxlength="400px" />

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.

• Poor visibility between text and background colors (9)
• • Line 22: <img src="../index_ar/logoberm.gif" alt="Portada web" width="110" height="30" style="margin-left: 70%; margin-top: -5%" />
  • Line 57: <img src="../politica/w340.png" alt="Validado HTML 4.01!" width="54" height="19" />
  • Line 57: <img src="../valid-xhtml11-blue.png" alt="Validada XHTML 1.1" width="54" height="19" />
  • Line 59: <img src="../index_ar/css.jpg" alt="Validado CSS!" width="54" height="19" />
  • Line 62: <img src="a1.jpg" alt="Icono de conformidad con el Nivel A, de las Directrices de Accesibilidad para el Contenido Web 1.0 del W3C-WAI" width="54" height="19" />
  • Line 62: <img src="taw_2_AA.png" alt="Validado por TAW3" width="78" height="19" title="Validado por TAW" />
  • Line 85: <img src="../valid-xhtml11-blue.png" alt="Las p&aacute;ginas con este logo est&aacute;n validadas para XHTML 1.1" width="54" height="19" />
  • Line 85: <img src="../politica/css.png" alt="Validado estilos CSS" width="54" height="19" />
  • Line 85: <img src="../politica/taw_2_AA.png" alt="Validado TAW3" width="78" height="19" />

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

• When an appropriate markup language exits, use markup rather than images to convey information.

3.2 Create documents that validate to published formal grammars.

• Verify that the document validates to published formal grammars (HTML-XHTML, CSS).

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

• Verify absolute units of measure are not used on stylesheets (1)
• • Line 17: <link href="../index_ar/informa_estilos.css" rel="stylesheet" type="text/css" />

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

• Verify that all headers are properly marked up ("h1"-"h6" elements).

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.

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.

• Verify that labels are positioned near their corresponding form controls.

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.1 Clearly identify the target of each link.

• Ensure that each link clearly identify its target.

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. No automatically detected problems and 12 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.

• 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

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

• There is no tab order in this document. A tab order makes controls easier to navigate for many users

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

• If this form is used to submit a search, verify that enable a variety of skill levels and preferences (1)
• • Line 24: <form action="http://www.google.com/custom" method="get">

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

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

• Consistent page layout and recognizable graphics benefit all users. In particular, they help people with cognitive disabilities or who have difficulty reading (1)
• • Line 17: <link href="../index_ar/informa_estilos.css" rel="stylesheet" type="text/css" />

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.