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 15 problems that require human review que requieren revisión manual.

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 (2)
• • Line 48: <link rel="stylesheet" type="text/css" href="/autonomos/export/sites/default/comercio/res/css/comun.css" />
  • Line 88: <link rel="stylesheet" type="text/css" href="/autonomos/export/sites/default/comercio/res/css/interior.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. (2)
• • Line 49: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/eventosOnLoad.js">
  • Line 50: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/restaurar-campos.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. (2)
• • Line 49: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/eventosOnLoad.js">
  • Line 50: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/restaurar-campos.js">
• Missing NOSCRIPT element with accessible alternative content for scripts in this page. Verify if it is needed (2)
• • Line 49: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/eventosOnLoad.js">
  • Line 50: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/restaurar-campos.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 (2)
• • Line 49: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/eventosOnLoad.js">
  • Line 50: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/restaurar-campos.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 31 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 (9)
• • Line 151: <img src="/autonomos/export/sites/default/comercio/res/imgs/logoPortal.png" alt="Logo del portal comercio" />
  • Line 163: <img src="/autonomos/export/sites/default/comercio/res/imgs/raiz.png" alt="Inicio del portal Aut&oacute;nomos y Emprendedores" />
  • Line 168: <img src="/autonomos/export/sites/default/comercio/res/imgs/home.png" alt="Inicio del portal comercio" />
  • Line 173: <img src="/autonomos/export/sites/default/comercio/res/imgs/noticias.png" alt="Noticias" />
  • Line 174: <img src="/autonomos/export/sites/default/comercio/res/imgs/recomienda.png" alt="Recomienda" />
  • Line 175: <img src="/autonomos/export/sites/default/comercio/res/imgs/mapaweb.png" alt="Mapa web" />
  • Line 176: <img src="/autonomos/export/sites/default/comercio/res/imgs/accesibilidad.png" alt="Accesibilidad" />
  • Line 177: <img src="/autonomos/export/sites/default/comercio/res/imgs/contactar.png" alt="Contactar" />
  • Line 392: <img src="/autonomos/export/sites/default/comercio/res/imgs/logo-Consejeria-Industria-Empleo-Asturias.png" alt="Logo de la Consejer&iacute;a de Industria y Empleo del Principado de Asturias" />

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 (2)
• • Line 48: <link rel="stylesheet" type="text/css" href="/autonomos/export/sites/default/comercio/res/css/comun.css" />
  • Line 88: <link rel="stylesheet" type="text/css" href="/autonomos/export/sites/default/comercio/res/css/interior.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 (2)
• • Line 250: 'subscribirse'
  • Line 251: 'Eliminar mi subscripción'

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 (2)
• • Line 49: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/eventosOnLoad.js">
  • Line 50: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/restaurar-campos.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 (2)
• • Line 49: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/eventosOnLoad.js">
  • Line 50: <script type="text/javascript" src="/autonomos/autonomos/comercio/res/js/restaurar-campos.js">

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 this label is positioned close to its corresponding form controls (2)
• • Line 179: <label for="buscador">
  • Line 258: <label for="mail">

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