TAW Logo
TAW 3.0 (2/9/10 2:09 PM) Validation conform to WAI guidelines, W3C Recommendation 5 May 1999
Testing outcome: http://www.alhamademurcia.es/index.asp
Go to the Fundación CTIC website
Test summary outcome
AutomaticHuman review
Priority 10160
Priority 2087
Priority 3029
1. Human review2. Human review3. Human review1. Human review2. Human review3. Human review2. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review2. Human review1. Human review
1. Human review1. Human review2. Human reviewalhamademurcia.es la web del ayuntamiento de Alhama de Murcia, imagen de Alhama de Murcia

Ayuntamiento de Alhama de Murcia

1. Human review2. Human reviewAyuntamiento de Alhama de Murcia, www.alhamademurcia.es  3. Human review 
1. Human review2. Human reviewir a inicio 3. Human review1. Human review2. Human reviewemail de contacto 3. Human review1. Human review2. Human reviewmapa de la web 3. Human review1. Human review2. Human reviewvisualización sin CSS 3. Human review1. Human review2. Human reviewvisualización normal 3. Human review1. Human review2. Human reviewvisualización contraste positivo 3. Human review1. Human review2. Human reviewvisualización contraste negativo 3. Human review1. Human review2. Human reviewtamaño de letra normal 3. Human review1. Human review2. Human reviewtamaño de letra mayor
Martes - 9 de febrero 2010

Agenda

1. Human review
1. Human review
3. Human review3. Human review2. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review1. Human review
1. Human review<< febrero 2010 1. Human review>>
L M X J V S D
1. Human review1 1. Human review2 1. Human review3 1. Human review4 1. Human review5 1. Human review6 1. Human review7
1. Human review8 1. Human review9 1. Human review10 1. Human review11 1. Human review12 1. Human review13 1. Human review14
1. Human review15 1. Human review16 1. Human review17 1. Human review18 1. Human review19 1. Human review20 1. Human review21
1. Human review22 1. Human review23 1. Human review24 1. Human review25 1. Human review26 1. Human review27 1. Human review28

Buscador

Boletín de Noticias

Dese de alta

Enlaces de Interés

Turismo en Alhama

1. Human review1. Human review1. Human review2. Human reviewGuia de Alhama 1. Human review3. Human review1. Human review1. Human review2. Human reviewMayos 2009 1. Human review3. Human review1. Human review1. Human review2. Human reviewSemana Santa 1. Human review3. Human review1. Human review1. Human review2. Human reviewSendero de El Berro 1. Human review3. Human review1. Human review1. Human review2. Human reviewVideo Alhama 2009
Video Alhama 2009
2. Human review1. Human review1. Human review2. Human review1. Human review

Actualidad

2. Human review Esta mañana se han presentado las actividades que van a contemplar estos Carnavales 2010.
1. Human review2. Human reviewfoto portada - noticia

1. Human review   (9/2/2010)  

La concejal de Festejos, Mª Elena Marín, informa de la programación prevista para este periodo festivo, donde comenzaremos por los más ...

2. Human review El Ayuntamiento establece un Servicio Municipal de Apoyo Técnico al Catastro para tramitar las afloraciones de unidades catastrales en suelo rústico
1. Human review2. Human reviewfoto portada - noticia

1. Human review   (8/2/2010)  

Con motivo de las actuaciones emprendidas para regularizar la situación de d...
 

2. Human review Abierto el nuevo plazo de matriculación en los Colegios de Alhama de Murcia para los ciclos de Educación Infantil y Educación Primaria
1. Human review2. Human reviewfoto portada - noticia

1. Human review   (8/2/2010)  

Desde hoy lunes 8 de febrero se puede realizar la matricula en todos los Colegios e Institu...

2. Human review El Ayuntamiento de Alhama de Murcia invita a todos los hosteleros a participar en la ruta: “Tapeando por Alhama 2010, Conócela”

1. Human review   (4/2/2010)  

En reunión celebrada el pasado lunes 1 de febrero de 2010 se acordó realizar la Ruta de la Tapa en...

2. Human review Charla audiovisual “El Mundo a Pedales”, por Juan Francisco Cerezo

1. Human review   (4/2/2010)  

El jueves 11 de febrero, a las 20:30 horas, en la Sala Abovedada del Museo Arqueológico Los Baños tendrá lugar la charla audiovisual impartida por el fotógrafo...

[Más noticias]

Tablón de Anuncios

2. Human review( 26/01/2010 )
Un puesto de Auxiliar Administrativo a jornada completa para realizar la Memoria Anual de la Policía Local correspondiente al año 2009.

2. Human review( 02/12/2009 )
ACTA DE LA SESION ORDINARIA DEL JURADO DEL CONCURSO DE IDEAS PARA EL AUDITORIO MUNICIPAL

2. Human review( 25/11/2009 )
CONCURSO DE IDEAS TEATRO AUDITORIO. PUBLICADAS LISTAS PROVISIONALES DE ADMITIDOS Y EXCLUIDOS. RESPUESTAS A CONSULTAS

[Más Anuncios]
1. Human review
1. Human review
© Excmo. Ayuntamiento de Alhama de Murcia 2008. Plaza de la Constitución - 30840 Alhama de Murcia (Murcia, España) · Teléfono: 968 630 000 · info@alhamademurcia.es · Aviso Legal · Accesibilidad · Actualizada a 09/02/2010 · Optimizada a 1024 x 768 para IE, Mozilla, Netscape · Desarrolla: 1. Human reviewAvatar Internet S.L.L. 1. Human review1. Human review2. Human reviewAvatar Internet S.L.L.

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

5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.

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 87 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.3 Use style sheets to control layout and presentation.

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.

5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).

5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.

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.

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.

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

5.5 Provide summaries for tables.

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

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

10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.

10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.

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.