Problemas de accesibilidad de Prioridad 1

Un desarrollador de contenidos de páginas Web tiene que satisfacer este punto de verificación. De otra forma, uno o más grupos de usuarios encontrarán imposible acceder a la información del documento. Satisfaciendo este punto de verificación es un requerimiento básico para que algunos grupos puedan usar estos documentos Web.

Se No automatically detected problems de tipo automático y 21 problems that require human review que requieren revisión manual.

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 (10)
• • Line 16: <img src="../../../archi_portada/logog.gif" alt="Si haces clic vas a la portada del sitio">
  • Line 65: <img src="portada_ico.jpg" alt="Portada toros" width="60" height="60">
  • Line 69: <img src="nino_haroboton.jpg" alt="El niño de Haro" width="60" height="60" >
  • Line 74: <img src="urzay_fotoico.jpg"alt="Ricardo Urzay" width=60 height=60>
  • Line 78: <img src="algabe_riojaico.jpg" alt="Algabeñito" width="60" height="60" >
  • Line 83: <img src="ganaderos_ico.jpg" alt="Ganaderos de la tierra" width=60 height=60 >
  • Line 88: <img src="../../noticias_icotoros.jpg" alt="Madrinas taurinas" width=60 height=60>
  • Line 93: <img src="plaznue_ico.jpg" alt="Plazas de toros de Logroño" width=60 height=60>
  • Line 98: <img src="cartel_ico.jpg" alt="Picador" width=60 height=60 >
  • Line 104: <img src="validador.bmp" alt="Validado XHTML 1.01" width="88" 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 (1)
• • Line 10: <link href="pepita.css" rel="stylesheet" type="text/css">

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

• Verify that equivalents of dynamic content are updated and avaliable as often as the dynamic content. (1)
• • Line 14: <script type="text/javascript" src="nobutton.js">

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.

• Verify that dynamic content is accessible or provide an alternative. (1)
• • Line 14: <script type="text/javascript" src="nobutton.js">
• Missing NOSCRIPT element with accessible alternative content for scripts in this page. Verify if it is needed (1)
• • Line 14: <script type="text/javascript" src="nobutton.js">

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

• Check it through the whole document

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.

• This element may not be accesible to all users. Please ensure there is an accesible interface to this object (1)
• • Line 14: <script type="text/javascript" src="nobutton.js">

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

Problemas de accesibilidad de Prioridad 2

Un desarrollador de contenidos de páginas Web debería satisfacer este punto de verificación. De otra forma, uno o más grupos encontrarán dificultades en el acceso a la información del documento. Satisfaciendo este punto de verificación eliminará importantes barreras de acceso a los documentos Web.

Se No automatically detected problems de tipo automático y 26 problems that require human review que requieren revisión manual.

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 (10)
• • Line 16: <img src="../../../archi_portada/logog.gif" alt="Si haces clic vas a la portada del sitio">
  • Line 65: <img src="portada_ico.jpg" alt="Portada toros" width="60" height="60">
  • Line 69: <img src="nino_haroboton.jpg" alt="El niño de Haro" width="60" height="60" >
  • Line 74: <img src="urzay_fotoico.jpg"alt="Ricardo Urzay" width=60 height=60>
  • Line 78: <img src="algabe_riojaico.jpg" alt="Algabeñito" width="60" height="60" >
  • Line 83: <img src="ganaderos_ico.jpg" alt="Ganaderos de la tierra" width=60 height=60 >
  • Line 88: <img src="../../noticias_icotoros.jpg" alt="Madrinas taurinas" width=60 height=60>
  • Line 93: <img src="plaznue_ico.jpg" alt="Plazas de toros de Logroño" width=60 height=60>
  • Line 98: <img src="cartel_ico.jpg" alt="Picador" width=60 height=60 >
  • Line 104: <img src="validador.bmp" alt="Validado XHTML 1.01" width="88" 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 10: <link href="pepita.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).
• The following text may need to be marked using Q or BLOCKQUOTE (1)
• • Line 39: "La Victoria"

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

• For scripts and applets, ensure that event handlers are input device-independent (1)
• • Line 14: <script type="text/javascript" src="nobutton.js">

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.

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

• This element may not be accesible to all users. Please ensure there is an accesible interface to this object (1)
• • Line 14: <script type="text/javascript" src="nobutton.js">

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

Problemas de accesibilidad de Prioridad 3

Un desarrollador de contenidos de páginas Web puede satisfacer este punto de verificación. De otra forma, uno o más grupos encontrarán dificultades en el acceso a la información del documento. Satisfaciendo este punto de verificación mejorará la accesibilidad de los documentos Web.

Se No automatically detected problems de tipo automático y 12 problems that require human review que requieren revisión manual.

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

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

• There are no keyboard shortcut keys to any of the controls in this document. Verify if they are needed.

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

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 10: <link href="pepita.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.