TAW Logo
TAW 3.0 (2/9/10 2:12 PM) Validation conform to WAI guidelines, W3C Recommendation 5 May 1999
Testing outcome: https://etsiit.ugr.es/apps/foro/index.php?idhebra=1628
Go to the Fundación CTIC website
Test summary outcome
AutomaticHuman review
Priority 11046
Priority 2266
Priority 3025
1. Human review2. Human review3. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review2. Automatic

ETS de Ingenierías Informática y de Telecomunicación

1. Automatic1. Human review2. Human review 3. Human review1. Automatic1. Human review2. Human review

3. Human review
2. Human review 2. Human review2. Human review 2. Human review

Foros

Índice de Foros >> Escuela
La ETSIIT finalista de la Microsoft Imagine Cup 2007 Mensajes: 7 Lecturas: 1387 Último post: 18 de abr de 2007 15:23 Tags destacados:
Por: 2. Human review1. Automatic2. Human review mahoma@turing 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 09 de abr de 2007 13:37

La Escuela va a estar representada este Jueves día 12 en la final Española de la Imagine Cup 2007 (que se celebra en Sevilla) por tres alumnos becarios del Departamento de Lenguajes y Sistemas Informáticos.

El concurso de Microsoft busca este año proyectos en base a la siguiente idea: "Imagina un mundo donde la tecnología facilite el acceso a la educación a todo el mundo".

El grupo ha participado con el sistema Sc@ut (2. Human reviewhttp://www.ugr.es/local/scaut), que tiene como finalidad mejorar la capacidad comunicativa del colectivo de personas con necesidades educativas especiales.

Se trata de la primera vez que alumnos de la Escuela participan en la final de este concurso. Escribimos para informar a nuestros compañeros y a los miembros del club .NET de Granada.

Esperamos tener suerte, informaremos de lo que ocurra.
1. Human review2. Human reviewEnlace permanente Por: 2. Human review1. Automatic2. Human review (x) 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 12 de abr de 2007 22:38

Que ha pasao?



2. Human reviewintelli2. Human review3. Human reviewgenia2. Human review3. Human review::Blog
1. Human review2. Human reviewEnlace permanente Por: 2. Human review1. Automatic2. Human review link@turing 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 13 de abr de 2007 21:35

Se ha ganado 1. Automatic1. Human review2. Human review

1. Human review2. Human reviewEnlace permanente Por: 2. Human review1. Automatic2. Human review timokotipelto 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 14 de abr de 2007 14:46

Enhorabuena ^_^
1. Human review2. Human reviewEnlace permanente Por: 2. Human review1. Automatic2. Human review mahoma@turing 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 18 de abr de 2007 12:13

Sí, hemos ganado la final de España y ahora vamos a Korea a ver si podemos hacer algo en la final Internacional (que va a ser que no jeje).

La verdad es que se le ha dado poca importancia al hecho en sí, es la primera vez que la Escuela se presenta a un concurso así y va y se gana. Deberíamos hacer pegatinas jejeje.

Gracias a los compañeros que nos han apoyado y/o felicitado.
1. Human review2. Human reviewEnlace permanente Por: 2. Human review1. Automatic2. Human review L 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 18 de abr de 2007 13:21

Enhorabuena por vuestra victoria (y espero que aparte de participar el de corea disfruteis mucho del viaje), si quereis poneros en contacto con los del club para lo que querais mandame un mail a granadadotnet@hotmail.com (nos enteramos de que participabais casi cuando ganasteis [estabamos liados con el papeleo para darnos de alta como asociacion], siento que no haber sido de ayda.)

" Si no lo consigues a la primera, llámalo versión 1.0."
" Microsoft: Vosotros tenéis las preguntas, nosotros los clips que bailan."
1. Human review2. Human reviewEnlace permanente Por: 2. Human review1. Automatic2. Human review link@turing 3. Human review1. Human review2. Human reviewEnviar mensaje Publicado el: 18 de abr de 2007 15:23

Hola

La verdad es que ha sido muy triste no haber contado con el apoyo del club de Granada, ya que existe uno. Todos los demás grupos iban con su legión de fans, sus pancartas, camisetas y sus compañeros del club...

Pero que se le va a hacer, si habéis estado tan liados poco hubieseis podido hacer.

Solo espero que esta victoria, inexistente y carente de interés para la mayoría de esta Escuela, os ayude un poco en vuestros quehaceres día a día como club de .NET y que para la siguiente vez, el club esté más cerca de los participantes y sirva de promoción y de ánimo a otros alumnos a presentarse a este tipo de eventos.

Si os interesa cualquier cosa de nosotros ya sabéis donde encontrarnos

Saludos
Índice de Foros >> Escuela
1. Human review2. Human reviewcontactar con equipo web
1. Human review2. Human reviewcontactar con secretaria
2. Automatic

C/Periodista Daniel Saucedo Aranda s/n E-18071 (Granada-Spain) Phone: +34-958242802

1. Human review2. Human reviewlogo ETSIIT
1. Human review2. Human reviewxhtml valid 3. Human review1. Human review2. Human reviewtaw3 valid
1. Human review2. Human reviewcss valid 3. Human review1. Human review2. Human reviewOptimizado para firefox
ETSIIT-Web 2.0 Pinky. Rev. 14902.
2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review 2. Human review1. Human review1. Human review1. Human review2. Human review1. Human review

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. 10 automatically detected problems and 46 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.

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.

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

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.

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

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

11.2 Avoid deprecated features of W3C technologies.

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.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.

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.

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.

9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.

10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.

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

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