http://www.danidesaro.com/index.html?design=freak - WCAG 2.0 A

Scan completed: 30/04/2019 3:24:18
Group  All issues
  • Visual checkWCAG 2.0 - Compliance Level A
      The priority set of WCAG 2.0 criteria. Generally these requirements are the most important and will have the widest impact on the accessibility of your site.
    • Visual checkCriterion 1.1.1 [Non-text Content]
        The intent of this Success Criterion is to make information conveyed by non-text content accessible through the use of a text alternative. Text alternatives are a primary way for making information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. Providing text alternatives allows the information to be rendered in a variety of ways by a variety of user agents. For example, a person who cannot see a picture can have the text alternative read aloud using synthesized speech. A person who cannot hear an audio file can have the text alternative displayed so that he or she can read it. In the future, text alternatives will also allow information to be more easily translated into sign language or into a simpler form of the same language.
      • Visual checkF3 Failure of Success Criterion 1.1.1 due to using CSS to include images that co...
          The CSS background-image property provides a way to include images in the document with CSS without any reference in the HTML code. The CSS background-image property was designed for decorative purposes and it is not possible to associate text alternatives with images that are included via CSS. Text alternatives are necessary for people who cannot see images that convey important information. Therefore, it is a failure to use this property to add images to convey important information.
        • Visual checkEnsure that image used in background-url for element is not conveying information
      • PassedF30 Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives t...
          This describes a failure condition for all techniques involving text alternatives. If the text in the "text alternative" cannot be used in place of the non-text content without losing information or function then it fails because it is not, in fact, an alternative to the non-text content. For example the alt text is the same as the item image name is graph.jpg and the alt text is graph.jpg
        • PassedImage has descriptive alt text
      • PassedH2 Combine adjacent image and text links for the same resource
      • PassedH37 Use alt attributes on img elements
      • PassedH44 Use label elements to associate text labels with form controls
          The objective of this technique is to use the label element to explicitly associate a form control with a label. A label is attached to a specific form control through the use of the for attribute. The value of the for attribute must be the same as the value of the id attribute of the form control.
        • PassedLABEL element 'FOR' attribute has unique ID's and matches all controls.
      • N/AF67 Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptio...
          The objective of this technique is to describe the failure that occurs when the long deion for non-text content does not serve the same purpose or does not present the same information as the non-text content. This can cause problems for people who cannot interpret the non-text content because they rely on the long deion to provide the necessary information conveyed by the non-text content. Without a long deion that provides complete information, a person may not be able to comprehend or interact with the Web page.
        • N/AImages were found; however none had a long description attribute.
      • N/AG144 Ensuring that the Web Page contains another CAPTCHA serving the same purpose ...
          The purpose of this technique is to reduce occasions in which a user with a disability cannot complete a CAPTCHA task. Because there are alternate CAPTCHA tasks that use different modalities, a user is more likely to be able to complete one of the tasks successfully.
        • N/ANo CAPTCHA element found.
      • N/AH24 Provide text alternatives for the area elements of image maps
          The objective of this technique is to provide text alternatives that serve the same purpose as the selectable regions of an image map. An image map is an image divided into selectable regions defined by area elements. Each area is a link to another Web page or another part of the current Web page. The alt attribute of each area element serves the same purpose as the selectable area of the image.
        • N/APage has no AREA elements.
      • N/AH27 Provide text and non-text alternatives for object
      • N/AH35 Provide text alternatives on applet elements
          Provide a text alternative for an applet by using the alt attribute to label an applet and providing the text alternative in the body of the applet element. Both mechanisms are required due to the varying support of the alt attribute and applet body text by user agents.
        • N/ANo APPLET elements found.
      • N/AH36 Use alt attributes on images used as submit buttons
          For input elements of type 'image', the alt attribute of the input element is used to provide a functional label. This label indicates the button's function, but does not attempt to describe the image. The label is especially important if there are multiple submit buttons on the page that each lead to different results.
        • N/ANo INPUT image elements found in document.
      • N/AH45 Use longdesc
          The objective of this technique is to provide information in a file designated by thelongdesc attribute when a short text alternative does not adequately convey the function or information provided in the image. The longdesc attribute is a URI, the target of which contains a long deion of the non-text content.
        • N/ANo IMG elements with LONGDESC attribute found
      • N/AH46 When EMBED elements are used, the NOEMBED element is required in the page
      • N/AH53 Use the body of the object element
          The objective of this technique is to provide a text alternative for content rendered using the object element. The body of the object element can be used to provide a complete text alternative for the object or may contain additional non-text content with text alternatives.
        • N/APage does not have OBJECT elements.
      • N/AH65 Use the title attribute to identify form controls when the label element ...
          The objective of this technique is to use the title attribute to label form controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing to display a label. User agents, including assistive technology, can speak the title attribute.
        • N/ANo controls found that require labels
      • N/AH67 Use null alt text and no title attribute on img elements for images that AT s...
    • Visual checkCriterion 1.3.3 [Sensory Characteristics]
        The intent of this Success Criterion is to ensure that all users can access instructions for using the content, even when they cannot perceive shape or size or use information about spatial location or orientation. Some content relies on knowledge of the shape or position of objects that are not available from the structure of the content (for example, "round button" or "button to the right"). Some users with disabilities are not able to perceive shape or position due to the nature of the assistive technologies they use. This Success Criterion requires that additional information be provided to clarify anything that is dependent on this kind of information.
      • Visual checkF14 Failure of Success Criterion 1.3.3 due to identifying content only by its sha...
          The objective of this technique is to show how identifying content only by its shape or location makes content difficult to understand and operate. When only visual identification or location is used, users with visual disabilities may find it difficult to locate content since they cannot see the screen or may perceive only a small portion of the screen at one time. Also, location of content can vary if page layout varies due to variations in font, window, or screen size.
        • Visual checkVerify page does not use shape or location to explain instructions
    • Visual checkCriterion 1.4.1 [Use of Color]
        The intent of this Success Criterion is to ensure that all users can access information that is conveyed by color differences, that is, by the use of color where each color has a meaning assigned to it. If the information is conveyed through color differences in an image (or other non-text format), the color may not be seen by users with color deficiencies. In this case, providing the information conveyed with color through another visual means ensures users who cannot see color can still perceive the information.
      • Visual checkG14 Ensure that information conveyed by color differences is also available in text
          The objective of this technique is to ensure that when color differences are used to convey information, such as required form fields, the information conveyed by the color differences are also conveyed explicitly in text.
        • Visual checkPage references an external style-sheet. Visual check required.
    • Visual checkCriterion 2.3.1 [Three Flashes or Below Threshold]
        The intent of this Success Criterion is to allow users to access the full content of a site without inducing seizures due to photosensitivity.
      • Visual checkG19 Ensure that no component of the content flashes more than three times in any ...
          The objective of this technique is to avoid flashing at rates that are known to cause seizures if the flashes are bright and large enough. Since some users may be using screen enlargers, this technique limits the flashing of any size content to no more than three flashes in any 1-second period.
        • Visual checkPage may contain elements that cause flickering.
    • Visual checkCriterion 2.4.3 [Focus Order]
        The intent of this Success Criterion is to ensure that when users navigate sequentially through content, they encounter information in an order that is consistent with the meaning of the content and can be operated from the keyboard. This reduces confusion by letting users form a consistent mental model of the content. There may be different orders that reflect logical relationships in the content. For example, move through components in a table one row at a time or one column at a time both reflect the logical relationships in the content. Either order may satisfy this Success Criterion.
      • Visual checkH4 Create a logical tab order through links, form controls, and objects
      • N/AC27 Making the DOM order match the visual order
    • Visual checkCriterion 2.4.4 [Link Purpose (In Context)]
        The intent of this Success Criterion is to help users understand the purpose of each link so they can decide whether they want to follow the link. Whenever possible, provide link text that identifies the purpose of the link without needing additional context. Assistive technology has the ability to provide users with a list of links that are on the Web page. Link text that is as meaningful as possible will aid users who want to choose from this list of links. Meaningful link text also helps those who wish to tab from link to link. Meaningful links help users choose which links to follow without requiring complicated strategies to understand the page.
      • Visual checkH30 Providing link text that describes the purpose of a link for anchor elements
          The objective of this technique is to describe the purpose of a link by providing deive text as the content of the a element. The deion lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URI of the destination is generally not sufficiently deive. When an image is the only content of a link, the text alternative for the image describes the unique function of the link. When the content of a link contains both text and one or more images, if the text is sufficient to describe the purpose of the link, the images may have an empty text alternative. (See Using null alt text and no title attribute on img elements for images that assistive technology should ignore.) When the images convey information beyond the purpose of the link, they must also have appropriate alt text.
        • Visual checkConfirm ALT or TITLE attribute text describes the purpose of the link.
          • http://www.danidesaro.com/index.html?design=freak
            • Line 115, column 13, a element, HREF = "http://validator.w3.org/check?uri=referer"
            • Line 118, column 13, a element, HREF = "https://jigsaw.w3.org/css-validator/check/referer"
            • Line 120, column 16, a element, HREF = "docu/http:_www.danidesaro.com - WCAG 2.0 A.html"
            • Line 121, column 16, a element, HREF = "http://www.cynthiasays.com/Pages/Help.aspx#CynthiaTested"
            • Line 122, column 12, a element, HREF = "https://validator.w3.org/nu/?showsource=yes&s...tp%3A%2F%2Fwww.danidesaro.com%2F"
        • Visual checkConfirm anchor element text describes the purpose of the link.
          • http://www.danidesaro.com/index.html?design=freak
            • Line 43, column 29, a element, HREF = "?design=freak"
            • Line 47, column 29, a element, HREF = "?design=clear"
            • Line 93, column 17, a element, HREF = "musica/index.html"
            • Line 96, column 17, a element, HREF = "programacion/index.html"
            • Line 99, column 17, a element, HREF = "contacto/index.html"
            • Line 102, column 17, a element, HREF = "about/index.html"
      • Visual checkH33 Supplement link text with the title attribute
          The objective of this technique is to demonstrate how to use a title attribute on an anchor element to provide additional text describing a link. The title attribute is used to provide additional information to help clarify or further describe the purpose of a link. If the supplementary information provided through the title attribute is something the user should know before following the link, such as a warning, then it should be provided in the link text rather than in the title attribute.
        • Visual checkVerify that title attribute and link text describe purpose of link
      • N/AH24 Provide text alternatives for the area elements of image maps
          The objective of this technique is to provide text alternatives that serve the same purpose as the selectable regions of an image map. An image map is an image divided into selectable regions defined by area elements. Each area is a link to another Web page or another part of the current Web page. The alt attribute of each area element serves the same purpose as the selectable area of the image.
        • N/APage has no AREA elements.
      • N/AH79 Identifying the purpose of a link in a data table using the link text combine...
          The objective of this technique is to identify the purpose of a link from the link in its data table context. This context is the table cell enclosing the link and the cell's associated table header cells. The data table context provides the purpose for an otherwise unclear link when the table cell is the nearest enclosing block-level ancestor element. It lets a user distinguish this link from other links in the Web page that lead to other destinations and helps the user determine whether to follow the link. Note that simply providing the URI of the destination is not sufficiently deive for people with disabilities, especially those with cognitive disabilities.
        • N/APage does not have TD or TH table elements with links.
    • Visual checkCriterion 3.3.1 [Error Identification]
        The intent of this Success Criterion is to ensure that users are aware that an error has occurred and can determine what is wrong. The error message should be as specific as possible. In the case of an unsuccessful form submission, re-displaying the form and indicating the fields in error is insufficient for some users to perceive that an error has occurred. Screen reader users, for example, will not know there was an error until they encounter one of the indicators. They may abandon the form altogether before encountering the error indicator, thinking that the page simply is not functional.
      • Visual checkG83 Provide text descriptions to identify required fields that were not completed
          The objective of this technique is to notify the user when a field that must be completed has not been completed. When users fail to provide input for any mandatory form fields, information is provided in text to enable the users to identify which fields were omitted. One approach is to use client-side validation and provide an dialog box identifying the mandatory fields which were omitted. Another approach, using server-side validation, is to re-display the form (including any previously entered data), with either a text deion at the location of the omitted mandatory field, or a text deion that identifies the omitted mandatory fields.
        • Visual checkVerify that all required fields are exposed to assistive technology.
      • Visual checkSCR18 Provide client-side validation and alert
          The objective of this technique is to validate user input as values are entered for each field, by means of client-side ing. If errors are found, an dialog describes the nature of the error in text. Once the user dismisses the dialog, it is helpful if the positions the keyboard focus on the field where the error occurred.
        • Visual checkIf validation is performed on input verify the information communicated is accessible to assistive technologies
    • Visual checkCriterion 3.3.2 [Labels or Instructions]
        The intent of this Success Criterion is to help users avoid making mistakes when their input is required. To help avoid mistakes it is good user interface design to provide simple instructions and cues for entering information. Some users with disabilities may be more likely to make mistakes than users without disabilities or recovery from mistakes may be more difficult, making mistake avoidance an important strategy for users with disabilities. People with disabilities rely on well documented forms and procedures to interact with a page. Blind users need to know exactly what information should be entered into form fields and what the available choices are. Simple instructions visually connected to form controls can assist users with cognitive disabilities or those accessing a page using a screen magnifier.
      • Visual checkG89 Provide expected data format and example
          The objective of this technique is to help the user avoid input errors by informing them about restrictions on the format of data that they must enter. This can be done by describing characteristics of the format or providing a sample of the format the data should have.
        • Visual checkVerify that instructions are provided for input that requires specially formatted data
      • PassedH44 Use label elements to associate text labels with form controls
          The objective of this technique is to use the label element to explicitly associate a form control with a label. A label is attached to a specific form control through the use of the for attribute. The value of the for attribute must be the same as the value of the id attribute of the form control.
        • PassedLABEL element 'FOR' attribute has unique ID's and matches all controls.
      • N/AH65 Use the title attribute to identify form controls when the label element ...
          The objective of this technique is to use the title attribute to label form controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing to display a label. User agents, including assistive technology, can speak the title attribute.
        • N/ANo controls found that require labels
    • Visual checkCriterion 4.1.1 [Parsing]
        The intent of this Success Criterion is to ensure that user agents, including assistive technologies, can accurately interpret and parse content. If the content cannot be parsed into a data structure, then different user agents may present it differently or be completely unable to parse it. Some user agents use "repair techniques" to render poorly coded content.
      • Visual checkG134 Validate Web pages
          The objective of this technique is to avoid ambiguities in Web pages that often result from code that does not validate against formal specifications. Each technology's mechanism to specify the technology and technology version is used, and the Web page is validated against the formal specification of that technology. If a validator for that technology is available, the developer can use it.
        • Visual checkVerify page has been run through W3C validator
    • PassedCriterion 1.3.1 [Info and Relationships]
        The intent of this Success Criterion is to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes. For example, the presentation format changes when the content is read by a screen reader or when a user style sheet is substituted for the style sheet provided by the author.
      • PassedH42 Use h1-h6 to identify headings
      • PassedH44 Use label elements to associate text labels with form controls
          The objective of this technique is to use the label element to explicitly associate a form control with a label. A label is attached to a specific form control through the use of the for attribute. The value of the for attribute must be the same as the value of the id attribute of the form control.
        • PassedLABEL element 'FOR' attribute has unique ID's and matches all controls.
      • PassedH97 Grouping related links using the nav element
          The objective of this technique is to group navigation links using the HTML5 nav element. The nav element is one of several sectioning elements in HTML5. Use of this markup can make groups of links easier to locate and skip past by users of assistive technology such as screen readers. Using semantic structures allow custom style sheets to be used to change the presentation of groups of links while preserving their relationship. When the nav element is employed more than once on a page, distinguish the navigation groups by using an aria-label or aria-labelledby attribute.
        • PassedNav element contains valid ARIA attribute for describing purpose of element.
      • N/AH39 Use caption elements to associate data table captions with data tables
          The objective of this technique is to programmatically associate captions for data tables where captions are provided in the presentation. The caption for a table is a table identifier and acts like a title or heading for the table.
        • N/ANo tables on page
      • N/AH43 Use id and headers attributes to associate data cells with header cells in ...
          The objective of this technique is to associate each data cell (in a data table) with the appropriate headers. This technique adds a headers attribute to each data cell (td element). It also adds an id attribute to any cell used as a header for other cells. The headers attribute of a cell contains a list of the id attributes of the associated header cells. If there is more than one id, they are separated by spaces.
        • N/APage does not contain complex data tables.
      • N/AH51 Use table markup to present tabular information
          The objective of this technique is to present tabular information in a way that preserves relationships within the information even when users cannot see the table or the presentation format is changed. Information is considered tabular when logical relationships among text, numbers, images, or other data exist in two dimensions (vertical and horizontal). These relationships are represented in columns and rows, and the columns and rows must be recognizable in order for the logical relationships to be perceived.
        • N/ANo tables used on page
      • N/AH63 Use the scope attribute to associate header cells and data cells in data ...
          The objective of this technique is to associate header cells with data cells using the scope attribute. The scope attribute may be used to clarify the scope of any cell used as a header. The scope identifies whether the cell is a header for a row, column, or group of rows or columns. The values row, col, rowgroup, and colgroup identify these possible scopes respectively.
        • N/ANo tables used on page
      • N/AH65 Use the title attribute to identify form controls when the label element ...
          The objective of this technique is to use the title attribute to label form controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing to display a label. User agents, including assistive technology, can speak the title attribute.
        • N/ANo controls found that require labels
      • N/AH73 Use the summary attribute of the table element to give an overview of data ...
          The objective of this technique is to provide a brief overview of how data has been organized into a table or a brief explanation of how to navigate the table. The summary attribute of the table element makes this information available to people who use screen readers; the information is not displayed visually.
        • N/ASummary attribute is not supported in HTML5.
      • N/AH85 Use OPTGROUP to group OPTION elements inside a SELECT
          The objective of this technique is to group items in a selection list. A selection list is a set of allowed values for a form control such as a multi-select list or a combo box. Often, selection lists have groups of related options. Those groups should be semantically identified, rather than simply delimiting the groups with "dummy" list entries. This allows user agents to collapse the options by group to support quicker skimming of the options, and to indicate in what group an option of interest is located. It also helps to visually break up long lists so that users can more easily locate the option(s) they are interested in.
        • N/APage has no SELECT elements
    • PassedCriterion 2.1.1 [Keyboard]
        The intent of this Success Criterion is to ensure that, wherever possible, content can be operated through a keyboard or keyboard interface (so an alternate keyboard can be used). When content can be operated through a keyboard or alternate keyboard, it is operable by people with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as by people who must use alternate keyboards or input devices that act as keyboard emulators. Keyboard emulators include speech input software, sip-and-puff software, on-screen keyboards, scanning software and a variety of assistive technologies and alternate keyboards. Individuals with low vision also may have trouble tracking a pointer and find the use of software much easier (or only possible) if they can control it from the keyboard.
      • PassedSCR2 Using redundant keyboard and mouse event handlers
    • PassedCriterion 2.4.2 [Page Titled]
        The intent of this Success Criterion is to help users find content and orient themselves within it by ensuring that each Web page has a deive title. Titles identify the current location without requiring users to read or interpret page content. When titles appear in site maps or lists of search results, users can more quickly identify the content they need. User agents make the title of the page easily available to the user for identifying the page. For instance, a user agent may display the page title in the window title bar or as the name of the tab containing the page.
      • PassedH25 Pages are required to use the TITLE element
    • PassedCriterion 3.1.1 [Language of Page]
        The intent of this Success Criterion is to ensure that content developers provide information in the Web page that user agents need to present text and other linguistic content correctly. Both assistive technologies and conventional user agents can render text more accurately when the language of the Web page is identified. Screen readers can load the correct pronunciation rules. Visual browsers can display characters and s correctly. Media players can show captions correctly. As a result, users with disabilities will be better able to understand the content.
      • PassedH57 Use language attributes on the html element
          The objective of this technique is to identify the default language of a document by providing the lang and/or xml:lang attribute on the html element.
        • PassedHTML element specifies the LANG attribute.
    • PassedCriterion 3.2.2 [On Input]
        The intent of this Success Criterion is to ensure that entering data or selecting from a control has predictable effects. Changes in context can confuse users who do not easily perceive the change or are easily distracted by changes. Changes of context are appropriate only when it is clear that such a change will happen when a field is selected or a button is pressed.
      • PassedH32 Provide submit buttons
          The objective of this technique is to provide a mechanism that allows users to explicitly request changes of context. The intended use of a submit button is to generate an HTTP request that submits data entered in a form, so it is an appropriate control to use for causing a change of context.
        • PassedAll forms provide submit buttons
      • N/AH84 Use a button with a select element to perform an action
          The objective of this technique is to allow the user to control when an action is performed, rather than having the action occur as a side effect of choosing a value for the select element. The user may inspect the different values of the select element, or may accidentally choose the wrong value, without causing the action to occur. When the user is satisfied with their choice, they select the button to perform the action.
        • N/ANo SELECT elements on page.
    • PassedCriterion 4.1.2 [Name, Role, Value]
        The intent of this Success Criterion is to ensure that Assistive Technologies (AT) can gather information about, activate(or set) and keep up to date on the status of user interface controls in the content.
      • PassedH44 Use label elements to associate text labels with form controls
          The objective of this technique is to use the label element to explicitly associate a form control with a label. A label is attached to a specific form control through the use of the for attribute. The value of the for attribute must be the same as the value of the id attribute of the form control.
        • PassedLABEL element 'FOR' attribute has unique ID's and matches all controls.
      • N/AH64 Using the title attribute of the frame and iframe elements
          The objective of this technique is to demonstrate the use of the title attribute of the frame or iframe element to describe the contents of each frame. This provides a label for the frame so users can determine which frame to enter and explore in detail. It does not label the individual page (frame) or inline frame (iframe) in the frameset. Note that the title attribute labels frames, and is different from the title element which labels documents. Both should be provided, since the first facilitates navigation among frames and the second clarifies the user's current The title attribute is not interchangeable with the name attribute. The title labels the frame for users; the name labels it for ing and window targeting. The name is not presented to the user, only the title is.
        • N/ANo FRAME elements found in document body.
      • N/AH65 Use the title attribute to identify form controls when the label element ...
          The objective of this technique is to use the title attribute to label form controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing to display a label. User agents, including assistive technology, can speak the title attribute.
        • N/ANo controls found that require labels
      • N/AHS4 DEMO: Verifying compliant toolbar
          For all user interface components (including but not limited to: form elements, links and components generated by s), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
        • N/ANo toolbars on page
    • N/ACriterion 1.2.1 [Audio-only and Video-only (Prerecorded)]
        The intent of this Success Criterion is to make information conveyed by prerecorded audio-only and prerecorded video-only content available to all users. Text alternatives used to make information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user.
      • N/AG158 Provide a full text transcript for the audio
      • N/AG159 Provide a full text transcript of the video content
      • N/AH96 Using the track element to provide audio descriptions
          The objective of this technique is to use the HTML5 track element to specify a deions timed text track for a video element. Audio deion timed text tracks contain textual deions of the video component of the media resource, intended for audio synthesis when the visual component is obscured, unavailable, or not usable. The user agent makes the cues available to the user in a non-visual fashion, for instance, by synthesizing them into speech.
        • N/APage does not contain video elements.
    • N/ACriterion 1.2.2 [Captions (Prerecorded)]
        The intent of this Success Criterion is to enable people who are deaf or hard of hearing to watch synchronized media presentations. Captions provide the part of the content available via the audio track. Captions not only include dialogue, but identify who is speaking and include non-speech information conveyed through sound, including meaningful sound effects.
      • N/AG87 Provide closed captions
          The objective of this technique is to provide a way for people who have hearing impairments or otherwise have trouble hearing the dialog in synchronized media material to be able to view the material and see the dialog and sounds - without requiring people who are not deaf to watch the captions. With this technique all of the dialog and important sounds are embedded as text in a fashion that causes the text not to be visible unless the user requests it. As a result they are visible only when needed. This requires special support for captioning in the user agent.
        • N/ANo videos on page
      • N/AH95 Using the track element to provide captions
          The objective of this technique is to use the HTML5 track element to specify a captions timed text track for a video element. Caption timed text tracks contain tranion or translation of the dialogue, sound effects, relevant musical cues, and other relevant audio information, suitable for when sound is unavailable or not clearly audible.
        • N/APage does not contain video elements.
    • N/ACriterion 1.2.3 [Audio Description or Full Text Alternative]
        The intent of this Success Criterion is to provide people who are blind or visually impaired access to the visual information in a synchronized media presentation. This Success Criterion describes two approaches, either of which can be used.
      • N/AG69 Provide a full synchronized media text alternative including any interaction
      • N/AG78 Provide a sound track that includes audio description
          The objective of this technique is to provide an audio (spoken) version of information that is provided visually so that it is possible for people who cannot see to be able to understand audio-visual material better.
        • N/ANo videos on page
      • N/AG8 Create an extended audio description for the synchronized media content
          The objective of this technique is to all additional audio deion to be inserted into a synchronized media presentation when there is not enough time in the gaps int the dialog. This is done by simply freezing the image so that additional audio deion of the video can be played. When the deion is finished, the synchronized media continues.
        • N/APage does not contain video
      • N/AH53 Use the body of the object element
          The objective of this technique is to provide a text alternative for content rendered using the object element. The body of the object element can be used to provide a complete text alternative for the object or may contain additional non-text content with text alternatives.
        • N/APage does not have OBJECT elements.
    • N/ACriterion 1.3.2 [Meaningful Sequence]
        The intent of this Success Criterion is to enable a user agent to provide an alternative presentation of content while preserving the reading order needed to understand the meaning. It is important that it be possible to programmatically determine at least one sequence of the content that makes sense. Content that does not meet this Success Criterion may confuse or disorient users when assistive technology reads the content in the wrong order, or when alternate style sheets or other formatting changes are applied.
      • N/AC27 Making the DOM order match the visual order
      • N/AH56 Use the dir attribute on an inline element to resolve problems with ...
          The objective of this technique is to identify changes in the text direction of text that includes nested directional runs by providing the dir attribute on inline elements. A nested directional run is a run of text that includes mixed directional text, for example, a paragraph in English containing a quoted Hebrew sentence which in turn includes an English phrase. Use of the dir attribute on an enclosing span or other inline element may be necessary because the Unicode bidirectional algorithm can produce undesirable results when mixed directional text contains spaces or punctuation. The concepts used in this technique are described in What you need to know about the bidi algorithm and inline markup.
        • N/AReading direction not specified on page
    • N/ACriterion 1.4.2 [Audio Control]
        Individuals who use screen reading software can find it hard to hear the speech output if there is other audio playing at the same time. This difficulty is exacerbated when the screen reader's speech output is software based (as most are today) and is controlled via the same volume control as the sound. Therefore, it is important that the user be able to turn off the background sound. Note: Having control of the volume includes being able to reduce its volume to zero.
      • N/AG60 Ensure all autostart sounds turns off automatically within three seconds
          The purpose of this technique is to allow authors to play a sound on their Web page but avoid the problem of users not being able to use their screen readers due to interference by the content sound. It also allows the author to avoid putting controls on the Web page to control the sound - and the problem faced by users with screen readers in finding the control (when unable to hear their screen reader).
        • N/ANo audio on page
    • N/ACriterion 2.1.2 [No Keyboard Trap]
        The intent of this Success Criterion is to ensure that that content does not "trap" keyboard focus within subsections of content on a Web page. This is a common problem when multiple formats are combined within a page and rendered using plug-ins or embedded applications.
      • N/AF10 Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combi...
          When content includes multiple formats, one or more user agents or plug-ins are often needed in order to successfully present the content to users. For example, a page that includes XHTML, SVG, SMIL and XForms may require a browser to load as many as three different plug-ins in order for a user to successfully interact with the content. Some plug-ins create a common situation in which the keyboard focus can become "stuck" in a plug-in, leaving a keyboard-only user with no way to return to the other content.
        • N/APage does not contain keyboard handlers
    • N/ACriterion 2.2.1 [Timing Adjustable]
        The intent of this Success Criterion is to ensure that users with disabilities are given adequate time to interact with Web content whenever possible. People with disabilities such as blindness, low vision, dexterity impairments, and cognitive limitations may require more time to read content or to perform functions such as filling out on-line forms. If Web functions are time-dependent, it will be difficult for some users to perform the required action before a time limit occurs. This may render the service inaccessible to them. Designing functions that are not time-dependent will help people with disabilities succeed at completing these functions. Providing options to disable time limits, customize the length of time limits, or request more time before a time limit occurs helps those users who require more time than expected to successfully complete tasks. These options are listed in the order that will be most helpful for the user. Disabling time limits is better than customizing the length of time limits, which is better than requesting more time before a time limit occurs.
      • N/ASCR1 Allow the user to extend the default time limit
          The objective of this technique is to allow user to extend the default time limit by providing a mechanism to extend the time when s provide functionality that has default time limits. In order to allow the user to request a longer than default time limit, the can provide a form (for example) allowing the user to enter a larger default time limit. Making this available as a preference setting allows users to indicate their requirements in advance. If warning the user a time limit is about to expire (see SCR16: Providing a that warns the user a time limit is about to expire (Scripting) ), this form can be made available from the warning dialog.
        • N/APage does not contain timeouts
    • N/ACriterion 2.2.2 [Pause, Stop, Hide]
        The intent of this Success Criterion is to avoid distracting users during their interaction with a Web page.
      • N/AF4 Failure of Success Criterion 2.2.2 due to using text-decoration:blink without...
          CSS defines the blink value for the text-decoration property. When used, it causes any text in elements with this property to blink at a predetermined rate. This cannot be interrupted by the user, nor can it be disabled as a user agent preference. The blinking continues as long as the page is displayed. Therefore, content that uses text-decoration:blink fails the Success Criterion because blinking can continue for more than three seconds.
        • N/ANo usages of text-decoration:blink found on page
    • N/ACriterion 2.4.1 [Bypass Blocks]
        The intent of this Success Criterion is to allow people who navigate sequentially through content more direct access to the primary content of the Web page. Web pages and applications often have content that appears on other pages or screens. Examples of repeated blocks of content include but are not limited to navigation links, heading graphics, and advertising frames. Small repeated sections such as individual words, phrases or single links are not considered blocks for the purposes of this provision.
      • N/AH64 Using the title attribute of the frame and iframe elements
          The objective of this technique is to demonstrate the use of the title attribute of the frame or iframe element to describe the contents of each frame. This provides a label for the frame so users can determine which frame to enter and explore in detail. It does not label the individual page (frame) or inline frame (iframe) in the frameset. Note that the title attribute labels frames, and is different from the title element which labels documents. Both should be provided, since the first facilitates navigation among frames and the second clarifies the user's current The title attribute is not interchangeable with the name attribute. The title labels the frame for users; the name labels it for ing and window targeting. The name is not presented to the user, only the title is.
        • N/ANo FRAME elements found in document body.
    • N/ACriterion 3.2.1 [On Focus]
        The intent of this Success Criterion is to ensure that functionality is predictable as visitors navigate their way through a Any component that is able to trigger an event when it receives focus must not change the context. Examples of changing context when a component receives focus include, but are not limited to:
      • N/AG107 Use "activate" rather than "focus" as a trigger for changes of context
          The objective of this technique is to provide a method for activating things that is predictable by the user. Users with cognitive disabilities and people using screen readers or screen magnifiers may be confused by an unexpected event such as automatic form submission or activation of a function that causes a change of context.
        • N/APage does not use focus to activate content
0
Total 0