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 52 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 (6)
Line 125: <img class="flag" src="./_img_comun/icn_castellano.gif" alt="ES" title="Diseño web Coruña" />- Line 126: <img class="flag" src="./_img_comun/icn_galego.gif" alt="GAL" title="Diseño web Galicia" />
- Line 130: <img src="/_img/ico_xhtml.gif" alt="xhtml 1.0" title="Valido XHTML 1.0" />
- Line 130: <img src="/_img/ico_css.gif" alt="css 2.1" title="Valido CSS 2.1" />
- Line 130: <img src="/_img/ico_wai_aa.gif" alt="WAI AA" title="Accesibilidad WAI - AA" />
- Line 130: <img src="/_img/ico_w3c.gif" alt="W3C" title="W3C" />
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 (4)
- Line 11: <link rel="stylesheet" href="./css/estilos.css" type="text/css" media="screen" />
- Line 58: <a id="close" style="display: none;" class="close" href="#">
- Line 67: <div id="subheader" style="text-align:left;">
- Line 80: <div class="section" style="background-color:#EFEFEF;">
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. (9)
- Line 144: <script type="text/javascript">
- Line 148: <script type="text/javascript">
- Line 153: <script src="./js/jquery-1.3.2.min.js" type="text/javascript">
- Line 154: <script type="text/javascript" src="./js/swfobject.js">
- Line 155: <script src="./js/jquery.infieldlabel.min.js" type="text/javascript">
- Line 156: <script type="text/javascript" src="./js/jquery.prettyPhoto.js">
- Line 157: <script src="./js/pululart.js" type="text/javascript">
- Line 158: <script type="text/javascript">
- Line 174: <script src="./js/resize_no_ie6.js" type="text/javascript">
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. (9)
- Line 144: <script type="text/javascript">
- Line 148: <script type="text/javascript">
- Line 153: <script src="./js/jquery-1.3.2.min.js" type="text/javascript">
- Line 154: <script type="text/javascript" src="./js/swfobject.js">
- Line 155: <script src="./js/jquery.infieldlabel.min.js" type="text/javascript">
- Line 156: <script type="text/javascript" src="./js/jquery.prettyPhoto.js">
- Line 157: <script src="./js/pululart.js" type="text/javascript">
- Line 158: <script type="text/javascript">
- Line 174: <script src="./js/resize_no_ie6.js" type="text/javascript">
- Missing NOSCRIPT element with accessible alternative content for scripts in this page. Verify if it is needed (9)
- Line 144: <script type="text/javascript">
- Line 148: <script type="text/javascript">
- Line 153: <script src="./js/jquery-1.3.2.min.js" type="text/javascript">
- Line 154: <script type="text/javascript" src="./js/swfobject.js">
- Line 155: <script src="./js/jquery.infieldlabel.min.js" type="text/javascript">
- Line 156: <script type="text/javascript" src="./js/jquery.prettyPhoto.js">
- Line 157: <script src="./js/pululart.js" type="text/javascript">
- Line 158: <script type="text/javascript">
- Line 174: <script src="./js/resize_no_ie6.js" type="text/javascript">
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 (9)
- Line 144: <script type="text/javascript">
- Line 148: <script type="text/javascript">
- Line 153: <script src="./js/jquery-1.3.2.min.js" type="text/javascript">
- Line 154: <script type="text/javascript" src="./js/swfobject.js">
- Line 155: <script src="./js/jquery.infieldlabel.min.js" type="text/javascript">
- Line 156: <script type="text/javascript" src="./js/jquery.prettyPhoto.js">
- Line 157: <script src="./js/pululart.js" type="text/javascript">
- Line 158: <script type="text/javascript">
- Line 174: <script src="./js/resize_no_ie6.js" type="text/javascript">
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 65 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 (21)
- Line 68: <img src="./_img_comun/logo_pululart.jpg" width="160" height="58" alt="Pululart" title="Inicio - Pululart" longdesc="/index.asp" />
- Line 68: <img src="./_img/sello_norma_web.jpg" width="90" height="91" alt="Empresa certificada por AENOR" title="Empresa certificada por AENOR" longdesc="/15504-aenor/aenor-certifica-empresa-galicia-coruna-lugo-pontevedra-orense-iso-15504-cmmi.shtml" />
- Line 70: <img src="./_img_comun/soluciones-de-internet.jpg" width="311" height="22" alt="Soluciones de internet - Pululart" title="Soluciones de internet - Pululart" longdesc="./soluciones-de-internet/" />
- Line 71: <img src="./_img_comun/creacion-digital.jpg" width="220" height="28" alt="Creación digital - Pululart" title="Creación digital - Pululart" longdesc="./creacion-digital/" />
- Line 72: <img src="./_img_comun/contacto.jpg" width="136" height="21" alt="Contacto - Pululart" title="Contacto - Pululart" longdesc="./contacto/" />
- Line 87: <img src="./_img_comun/img_estudio_inicio.jpg" width="65" height="21" alt="Nuestro estudio" title="Nuestro estudio" longdesc="./web/estudio.shtml" />
- Line 87: <img src="./_img_comun/img_equipo_inicio.jpg" width="61" height="21" alt="Nosotros" title="Nosotros" longdesc="./web/equipo.shtml" />
- Line 95: <img src="./_img_comun/btn_blog_pululart.jpg" width="88" height="21" alt="El blog de Pululart" title="El blog de Pululart" longdesc="http://www.pulular.es" />
- Line 102: <img src="./_img_trabajos/destacados_kupu.jpg" width="110" height="72" alt="Diseño web - Küpu" longdesc="#" title="Diseño web - Küpu" />
- Line 103: <img src="./_img_trabajos/destacados_elbosque.jpg" width="110" height="72" alt="Diseño web - Discoteca El Bosque" longdesc="#" title="Diseño web - Discoteca El Bosque" />
- Line 105: <img src="../_img_trabajos/destacados_gadis.jpg" width="110" height="72" alt="Diseño web - Gadis" longdesc="#" title="Diseño web - Gadis" />
- Line 106: <img src="../_img_trabajos/destacados_citic.jpg" width="110" height="72" alt="Diseño grafico - Citic" longdesc="#" title="Diseño grafico - Citic" />
- Line 108: <img src="../_img_comun/btn_trabajo_inicio.jpg" width="67" height="21" alt="Nuestros trabajos" longdesc="./web/trabajo.shtml" title="Nuestros trabajos" />
- Line 108: <img src="./_img_comun/btn_cliente_inicio.jpg" width="64" height="21" alt="Nuestros clientes" longdesc="./web/cliente.shtml" title="Nuestros clientes" />
- Line 125: <img class="flag" src="./_img_comun/icn_castellano.gif" alt="ES" title="Diseño web Coruña" />
- Line 126: <img class="flag" src="./_img_comun/icn_galego.gif" alt="GAL" title="Diseño web Galicia" />
- Line 130: <img src="/_img/ico_xhtml.gif" alt="xhtml 1.0" title="Valido XHTML 1.0" />
- Line 130: <img src="/_img/ico_css.gif" alt="css 2.1" title="Valido CSS 2.1" />
- Line 130: <img src="/_img/ico_wai_aa.gif" alt="WAI AA" title="Accesibilidad WAI - AA" />
- Line 130: <img src="/_img/ico_w3c.gif" alt="W3C" title="W3C" />
- Line 132: <img src="/_img/aenor_peque.jpg" alt="Logo AENOR - ISO/IEC 15504" title="AENOR - ISO/IEC 15504" longdesc="/15504-aenor/aenor-certifica-empresa-galicia-coruna-lugo-pontevedra-orense-iso-15504-cmmi.shtml" />
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 11: <link rel="stylesheet" href="./css/estilos.css" type="text/css" media="screen" />
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).
- Header elements (H1-H6) should be used to define headers and should not be used for formatting text (1)
- Line 25: <h2>
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 (3)
- Line 92: "Comienza la liga de fútbol"
- Line 92: "fedegustando.com"
- Line 92: "Presentación de los primeros cinco cuentos de Rodribico"
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 (9)
- Line 144: <script type="text/javascript">
- Line 148: <script type="text/javascript">
- Line 153: <script src="./js/jquery-1.3.2.min.js" type="text/javascript">
- Line 154: <script type="text/javascript" src="./js/swfobject.js">
- Line 155: <script src="./js/jquery.infieldlabel.min.js" type="text/javascript">
- Line 156: <script type="text/javascript" src="./js/jquery.prettyPhoto.js">
- Line 157: <script src="./js/pululart.js" type="text/javascript">
- Line 158: <script type="text/javascript">
- Line 174: <script src="./js/resize_no_ie6.js" type="text/javascript">
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 (9)
- Line 144: <script type="text/javascript">
- Line 148: <script type="text/javascript">
- Line 153: <script src="./js/jquery-1.3.2.min.js" type="text/javascript">
- Line 154: <script type="text/javascript" src="./js/swfobject.js">
- Line 155: <script src="./js/jquery.infieldlabel.min.js" type="text/javascript">
- Line 156: <script type="text/javascript" src="./js/jquery.prettyPhoto.js">
- Line 157: <script src="./js/pululart.js" type="text/javascript">
- Line 158: <script type="text/javascript">
- Line 174: <script src="./js/resize_no_ie6.js" type="text/javascript">
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.
- This anchor element will open a new window that can disorient some users (5)
- Line 130: <a href="./sitemap.asp" title="Sitemap Pululart" target="_blank" class="btnsitemap">
- Line 130: <a href="http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fpululart.com" title="Pululart.com - XHTML 1.0" target="_blank">
- Line 130: <a href="http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww.pululart.com" title="Pululart.com - CSS 2.1" target="_blank">
- Line 130: <a href="http://www.tawdis.net/tawdis/online?url=http%3A%2F%2Fpululart.com" title="Accesibilidad WAI - AA" target="_blank">
- Line 137: <a href="http://twitter.com/pululart" target="_blank" title="Twitter - Pululart" class="btwitter">
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 (4)
- Line 29: <label for="email_newsletter">
- Line 30: <label for="cb_condicion_uso1">
- Line 37: <label for="usuario">
- Line 38: <label for="pass">
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 2 automatically detected problems de tipo automático y 19 problems that require human review que requieren revisión manual.
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.
- This form control is missing placeholder text (2)
Line 29: <input class="field" type="text" name="email_newsletter" id="email_newsletter" value="" size="23" />- Line 37: <input class="field" type="text" name="usuario" id="usuario" value="" size="20" />
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.
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
- If these sequential links do not have separation characters, include non-link printable character between them (5)
- Line 58: <a id="close" style="display: none;" class="close" href="#">
- Line 87: <a href="./web/equipo.shtml" title="Nosotros">
- Line 108: <a href="./web/cliente.shtml" title="Nuestros clientes">
- Line 130: <a href="http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww.pululart.com" title="Pululart.com - CSS 2.1" target="_blank">
- Line 130: <a href="http://www.tawdis.net/tawdis/online?url=http%3A%2F%2Fpululart.com" title="Accesibilidad WAI - AA" target="_blank">
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 (2)
- Line 27: <form class="clearfix" name="newsletter_form" id="newsletter_form" action="#">
- Line 35: <form name="login_form" id="login_form" method="post" class="login" action="http://www.pululart.es/area-cliente/index.php">
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 11: <link rel="stylesheet" href="./css/estilos.css" type="text/css" media="screen" />
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.
0
0
65
2
19
Castellano
Galego
