1.1 Issue category: Accessibility.
1.1.1 [508 (A)] [WCAG 1.1 (1)] Alt is missing
1.1.2 [508 (A)] [WCAG 1.1 (1)] Object without alternative inner text
1.1.3 [508 (A)] [WCAG 1.1 (1)] Clickable image without alt
1.1.4 [508 (A)] [WCAG 1.1 (1)] Bad alt text
1.1.5 [508 (A)] [WCAG 1.1 (1)] Alt exists, but empty
1.1.10 [508 (F)] [WCAG 9.1 (1)] Server-side image map is found
1.1.11 [508 (G),(H)] [WCAG 5.1,5.2 (1)] Data table without headers is found
1.1.12 [508 (I)] [WCAG 12.1 (1)] Frame has no 'title'
1.1.13 [508 (I)] [WCAG 12.1 (1)] Frames with the same title are found
1.1.14 [508 (J)] Flicker rate must be in the specified limits
1.1.15 [508 (K)] [WCAG 11.4 (1)] Text-only web page shall only be provided as a last resort method
1.1.16 [508 (L)] Clickable image with JavaScript link has no 'alt' or 'title'
1.1.17 [508 (M)] Link to plug-in used by page must be provided
1.1.18 [508 (N)] [WCAG 12.3 (2)] Long list of form controls without grouping is found
1.1.19 [508 (N)] [WCAG 12.3 (2)] Long list of options without grouping is found
1.1.20 [508 (N)] [WCAG 12.4 (2)] Form control without explicit label is found
1.1.21 [508 (O)] [WCAG 13.6 (3)] Page without skip link
1.1.22 [508 (P)] Page requiring timed response must allow user to get more time
1.1.23 [WCAG 1.1,6.3 (1)] NOSCRIPT tag required on a page
1.1.24 [WCAG 1.3 (1)] Multimedia presentation requires auditory description
1.1.25 [WCAG 2.2 (2)] Low-contrast text is found
1.1.26 [WCAG 2.2 (2)] Images must have sufficient contrast
1.1.27 [WCAG 3.1 (2)] Use markup instead of images where possible
1.1.28 [WCAG 3.2 (2)] Doctype missing
1.1.29 [WCAG 3.2 (2)] Document must be valid
1.1.30 [WCAG 3.3 (2)] Do not use presentation elements
1.1.31 [WCAG 3.3 (2)] Use style sheets to control layout and presentation
1.1.32 [WCAG 3.3,3.5 (2)] Do not use headers and other structural markup only for visual effects
1.1.33 [WCAG 3.4 (2)] Fixed sizes are found
1.1.34 [WCAG 3.4 (2)] Fixed fonts are found
1.1.35 [WCAG 3.5, 12.3 (2)] Hardly reachable text for voice reader is found
1.1.36 [WCAG 3.5 (2)] Use header elements to convey document structure
1.1.37 [WCAG 3.6 (2)] Mark up lists
1.1.38 [WCAG 3.7 (2)] Mark up quotations
1.1.39 [WCAG 4.1 (1)] Changes in the natural language must be clearly identified
1.1.40 [WCAG 4.3 (3)] Document language markup is missing
1.1.41 [WCAG 5.3 (2)] Do not use tables for layout if they can not be linearized properly
1.1.42 [WCAG 5.4 (2)] Do not use data table markup for layout tables
1.1.44 [WCAG 6.3 (1) ,6.5 (2)] Script based link is found
1.1.45 [WCAG 6.4, 9.3 (2)] Device-dependent event handler is found
1.1.46 [WCAG 6.4 (2)] If objects use event handlers, they must be accessible without a mouse too
1.1.47 [WCAG 6.5 (2)] Noframes for frameset required
1.1.48 [WCAG 7.1 (1); 7.2,7.3 (2)] Blink text is found
1.1.49 [WCAG 7.1 (1); 7.2,7.3 (2)] Avoid flickering, blinking and movement in pages
1.1.50 [WCAG 7.4,7.5 (2)] Refresh meta is found
1.1.51 [WCAG 8.1 (1)] Programmatic elements must be directly accessible
1.1.52 [WCAG 9.2 (2)] Object interface must be accessible without a mouse too
1.1.53 [WCAG 9.3 (2)] Inaccessible select menu
1.1.54 [WCAG 10.1 (2)] New browser window is detected
1.1.55 [WCAG 10.1 (2)] Popup dialog window is detected
1.1.56 [WCAG 10.2 (2)] Implicit labels must be properly positioned
1.1.57 [WCAG 11.1 (2)] Use the latest W3C technologies available whenever possible
1.1.58 [WCAG 11.2 (2)] Avoid deprecated language features
1.1.59 [WCAG 12.2 (2)] Provide additional information for framesets
1.1.60 [WCAG 13.1 (2)] Link name/destination clash
1.1.61 [WCAG 13.1 (2)] Non-meaningful link name is found
1.1.62 [WCAG 13.2 (2)] Metadata are missing
1.1.63 [WCAG 13.3,13.4 (2)] Provide clear and consistent navigation
1.1.64 [WCAG 14.1 (1)] The clearest and simplest language must be used
1.1.65 [WCAG 14.3 (3)] Inline styles are found
1.1.66 [WCAG-2 1.4 (2)] Low luminosity contrast text is found
1.2 Issue category: Privacy compliance
1.2.1 Privacy policy link is missing
1.2.2 Web beacon with cookies is found
1.2.3 Web beacon without cookies is found
1.2.4 Third-party cookies are found
1.2.5 Third party links are found
1.2.6 Long-life persistent cookie is found
1.2.7 Cookie restricted by IE6 is found
1.2.8 Cookie blocked by IE6 is found
1.2.10 Form with method GET is used
1.2.11 P3P policy reference file is missing
1.2.12 P3P policyref must be in double quotes
1.2.13 P3P compact policy must be in double quotes
1.2.15 PII: Page collects age data
1.2.16 PII: Page collects age revealing information
1.2.17 PII: Page collects PII and opt-in/opt-out inputs are missing
1.2.18 PII: Page collects PII and has prechecked opt-in/opt-out inputs
1.2.19 PII: COPPA: Page collects PII and contains inputs collecting forbidden PII
1.2.20 PII: COPPA: Page collects PII and does not ask parent email
1.2.21 PII: COPPA: Page collects PII and has no kids privacy policy link
1.2.22 PII: No COPPA: Page collects PII and age data
1.2.23 PII: No COPPA: Page collects PII and age revealing information
1.2.24 PII: No COPPA: Page collects PII and is oriented towards children
1.2.25 PII: No COPPA: Page collects PII and contains disclaimers
1.2.26 PII: No COPPA: Page collects PII and does not contain disclaimers
1.3 Issue category: Search Engine Optimization
1.3.1 A web page is not indexed in MSN
1.3.2 A web page is not indexed in Yahoo
1.3.3 A web page is referenced by dynamic hyperlink only
1.3.4 A web page is blocked by robots.txt file
1.3.5 A web page is blocked by robots meta tag
1.3.6 A web page is linked through rel=nofollow attribute
1.3.7 A web page is linked from page with robots meta 'nofollow'
1.3.8 Multi-step redirect link to internal web page
1.3.9 Client side redirect link to external website
1.3.10 Client side redirect to external website
1.3.11 A web page is loaded by client side redirect
1.3.14 A web page with many parameters in its URL
1.3.16 Non relevant words in HTML title
1.3.18 Non relevant words in HTML keywords
1.3.20 Duplicated HTML descriptions
1.3.21 Page has too many links.
1.3.22 Dynamic links are found
1.3.23 Link to improper web content
1.3.24 Web pages with the same content
1.3.25 Different URLs to the same web page
1.4 Issue category: Web site quality
1.4.3 HTML keywords: default value
1.4.4 HTML keywords: repetitive
1.4.5 HTML description: missing
1.4.6 HTML description: default value
1.4.7 HTML character set: missing
1.4.9 Broken source URLs are found
1.4.14 Script error popup is detected
1.5 Issue category: Interactive behavior
1.5.1 New browser window is detected
1.5.2 Popup dialog window is detected
1.6 Issue category: Google Analytics
1.6.1 Google Analytics JavaScript file is in Head section
1.6.2 Google Analytics Account variable value is incorrect
1.6.3 Google Analytics Account variable value can not be detected because page script contains error
1.6.4 Google Analytics Event Tracking detected, but does not work
1.6.5 Google Analytics JavaScript file is not downloaded
1.6.6 Google Analytics Account variable is not found
1.6.7 Google Analytics WebBeacon is not detected
1.6.8 Google Analytics Cookie is not detected
1 Truwex Quality Issues
All issues are gathered into several issue categories depending on their purpose to facilitate reporting. Truwex can report on overall website compliance within selected issue category. For example, how a website is compliant with accessibility requirements.
Issue name is placed to the header. It appears as stated in Truwex.
Issue description clarifies its purpose.
Issue ID is a Truwex identifier to reference the issue.
Issue detailed description provides additional technical information how Truwex detects an issue, including HTML samples, or gives advice how to fix the issue.
Some issues have settings. They serve to fine tune reports to corporate requirements.
Parameter name is the name of issue setting as it appears in Truwex.
Setting type
- Exception is a string to be excluded from the data to report an issue on. For example, Truwex generates "an image without ALT is found" error. Having an exception "http://example.com/image.gif", Truwex will not detect the issue even if this image has no ALT. Exception could be of the predefined values. In this case it can be applied or disabled via checkbox.
- Pattern is a string to compare with the explored data. In case of match Truwex generates the corresponding issue. Pattern could be of the predefined values. In this case it can be applied or disabled via checkbox.
- Threshold is a value to compare with the mined data. It can be editable or predefined (enabled by checkbox). Example: page depth has a threshold value. If this parameter is higher than a threshold, Truwex triggers an issue.
- Option is a setting to Truwex, which defines how it checks a particular issue. Example: IE security level parameter defines the algorithm of cookies related issues.
Errors and warnings
With Truwex 2.0, Truwex has two statuses for quality issues: Error and Warning. Errors are considered as non-compliance problems to be fixed. Warnings just inform about possible problems. Every issue can be set as a warning or an error upon a user choice.
Applicability notes: Issues settings and errors/warning options are not available in Truwex Online Web Page Check Tool. They are for full Truwex version only. In the Online Truwex version issues have pre-defined default settings. Issues also have default error/warning statuses; the statuses are not visible on the start page, but you can see them in reporting.
1.1 Issue category: Accessibility.
All accessibility issues have prefix, which looks like "[508 (A)] [WCAG 1.1 (1)]" or one of the brackets. This text references the section 508 of the US Rehabilitation Act and the Web Content Accessibility Guidelines (WCAG) 1.0 by W3C respectively. For example, [508 (G),(H)] references provisions (G) and (H) of the section 508. [WCAG 5.1,5.2 (1)] references paragraphs 5.1 and 5.2 of WCAG, where "(1)" means the first priority. Clicking on the links behind references opens a web page with specified requirements. Some issues may reference the same provision of the section 508 and WCAG. It helps in issue customization for corporate guidelines.
DISCLAIMER. The fact that Truwex detects no accessibility issues on checked web page does not bring a guarantee that this web page is compliant with the Section 508 or WCAG requirements in general or in particular provision. Truwex is designed to facilitate creating and keeping web pages compliant with the Section 508 and WCAG requirements and it does not eliminate a need for manual audit of web pages.
1.1.1 [508 (A)] [WCAG 1.1 (1)] Alt is missing
Issue description: Alt is missing (image, applet)
Issue ID: 601
Issue detailed description: Check if the following elements have no any alt: IMG, APPLET
1.1.2 [508 (A)] [WCAG 1.1 (1)] Object without alternative inner text
Issue description: OBJECT element contains no alternative content. Alternative content is text equivalent, image equivalent or any other elements inside Object tag, which provide alternative representations of Object's information. Alternative content is useful when user's browser does not support the object - inner content of Object tag is rendered instead.
Issue ID: 604
Issue detailed description: Provide alternative representation (e.g. text or image equivalent) inside OBJECT element.
1.1.3 [508 (A)] [WCAG 1.1 (1)] Clickable image without alt
Issue description: Clickable image without alt is found: image inside anchor tag without inner text, input image, map area. All these clickable images must have non-empty alt text.
Issue ID: 605
Issue detailed description: Clickable IMG, clickable INPUT type="image", or clickable AREA element has no alt or its alt is empty. Clickable images are the most sensitive to missing ALTs, since it is not clear where its link goes.
1.1.4 [508 (A)] [WCAG 1.1 (1)] Bad alt text
Issue description: Alt text should not be too long or too short. Maximum and minimum of allowable length is set in settings (150 and 2 are the defaults). Alt text should be meaningful, e.g. 'Image' is a bad alt (elements: image, map area, applet, object). All bad alts are listed in settings.
Issue ID: 609
Issue detailed description: 1) Alt text is too short: its length is less than 2 symbols. 2) Alt text is too long: its length is more than 150 symbols. 3) Compare 'alt' attribute with the specified list of "bad" alts. Affected elements: IMG, INPUT type="image", OBJECT, APPLET, AREA. Comparison is case-insensitive, beginning and ending spacers are trimmed.
Issue settings
Parameter name: Bad alt patterns
Setting type: Pattern
Setting description: List of "bad" alt attributes. Truwex compares provided patters with ALT attributes and if some matches ALT value, it reports an error.
Setting sample: "image", "spacer", "logo"
Parameter name: Minimum allowable alt text length (planned)
Setting type: Threshold
Setting description: Short alt length threshold
Setting sample: 2
Parameter name: Maximum allowable alt text length (planned)
Setting type: Threshold
Setting description: Long alt length threshold
Setting sample: 150
1.1.5 [508 (A)] [WCAG 1.1 (1)] Alt exists, but empty
Issue description: Manual check. Alt exists, but empty (image, applet). Exceptions can be set for small or design images, for images or applets with specific source URLs.
Issue ID: 602
Issue detailed description: Check if the following elements have empty alt: 1) APPLET; 2) non-clickable IMG. This check is a warning by default.
Issue settings
Parameter name: Small images may have empty (null) alt
Setting type: Exception
Setting description: Non-clickable images (IMG elements) whose size is less than 100 bytes are not reported on this issue.
Setting sample: enabled (checked)
Parameter name: Design images may have empty alt
Setting type: Exception
Setting description: Design images are non-clickable IMG elements whose height or width is less or equal to 1px. They are not considered.
Setting sample: enabled (checked)
Parameter name: Src exception list
Setting type: Exception
Setting description: Source URL ('src' attribute) exception list for non-clickable IMG and APPLETs. Images, which begin from the specified URLs are not considered for this issue.
Setting sample: "http://example.com/image.gif"
1.1.6 [508 (B)] [WCAG 1.4 (1)] Multimedia presentation and its equivalent alternatives must be synchronized
Issue description: Manual check. Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
Issue ID: 637
Issue detailed description: Manually check OBJECTs, EMBEDs, and APPLETs.
1.1.7 [508 (C)] [WCAG 2.1 (1)] The use of color must not be a single method for indicating important information on a web page
Issue description: Manual check. Ensure that all information conveyed with color is also available without color, for example from context or markup.
Issue ID: 638
Issue detailed description: Manually check a web page.
1.1.8 [508 (D)] [WCAG 6.1 (1)] Documents must be organized so they are readable without requiring user agent support for style sheets
Issue description: Manual check. 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.
Issue ID: 640
Issue detailed description: This warning appears when Truwex detects that page uses CSS styles. Manually check a page in a browser with CSS styles disabled.
1.1.9 [508 (E)] [WCAG 1.2 (1)] For server-side image map regions redundant text links must be provided
Issue description: Manual check. Provide redundant text links for each active region of a server-side image map.
Issue ID: 635
Issue detailed description: Server-side image map is found. Manually check that redundant text links are provided on a page.
1.1.10 [508 (F)] [WCAG 9.1 (1)] Server-side image map is found
Issue description: Provide client-side image maps instead of server-side image maps
Issue ID: 628
Issue detailed description: Server-side image map is found.
1.1.11 [508 (G),(H)] [WCAG 5.1,5.2 (1)] Data table without headers is found
Issue description: Data table should have row- and column-headers markup.
Issue ID: 617
Issue detailed description: Find data tables and check whether they have row- or column-headers markup or not. Minimal markup requirements: TH is presented, or TD with scope="col" attribute, or two TD paired by id (<TD id="name"> and <TD headers="name">).
Issue settings
Parameter name: (planned)
Setting type: parameter
Setting description: [Custom settings that help distinguish data tables from layout tables]
Setting sample:
1.1.12 [508 (I)] [WCAG 12.1 (1)] Frame has no 'title'
Issue description: FRAME or IFRAME element without 'title' attribute is found. Frames shall be titled with text that facilitates frame identification and navigation
Issue ID: 633
Issue detailed description: Find FRAME or IFRAME elements without 'title' attribute.
1.1.13 [508 (I)] [WCAG 12.1 (1)] Frames with the same title are found
Issue description: FRAME and IFRAME elements should have title that facilitates frame identification and navigation. Do not use the same 'title' for different frames.
Issue ID: 634
Issue detailed description: Find FRAME or IFRAME elements with the same titles.
1.1.14 [508 (J)] Flicker rate must be in the specified limits
Issue description: Manual check. Page shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Check gif images and objects, applets, embed elements.
Issue ID: 647
Issue detailed description: OBJECTs, EMBEDs, APPLETs, or gif images are found. Manually check them.
1.1.15 [508 (K)] [WCAG 11.4 (1)] Text-only web page shall only be provided as a last resort method
Issue description: Manual check. 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.
Issue ID: 699
Issue detailed description: This issue appears when Truwex detects at least one accessibility issue or warning.
1.1.16 [508 (L)] Clickable image with JavaScript link has no 'alt' or 'title'
Issue description: Clickable image with JavaScript link: image needs 'alt', anchor tag needs 'title'
Issue ID: 621
Issue detailed description: Find anchor tags (A elements) whose 'href' attribute starts with "javascript:" and who has nested IMG element and has no inner text. Error fires if such anchor has no 'title' attribute, or if image inside it has no alt.
1.1.17 [508 (M)] Link to plug-in used by page must be provided
Issue description: Manual check. Web page which provides content such as Real Audio or PDF files also must provide a link to a plug-in that will meet the software provisions.
Issue ID: 645
Issue detailed description: Page has links to .mp3, .wav, .pdf, or .wma files. Manually check that page also contains links to accessible plug-ins.
1.1.18 [508 (N)] [WCAG 12.3 (2)] Long list of form controls without grouping is found
Issue description: Logical groups of form controls should be broken into separate sections using FIELDSET groups and labeled using LEGEND tags
Issue ID: 630
Issue detailed description: Count form controls (with the exception of hiddens) inside every FIELDSET element. And, if field sets are missing, in every FORM element. Compare this number with the defined threshold. If field sets are used, they should contain LEGEND tag with non-empty description of controls in this set.
Issue settings
Parameter name: Max number of non-grouped controls in FORM element (planned)
Setting type: Threshold
Setting description: If the number of controls not separated by FIELDSET exceeds the threshold, Truwex reports this issue.
Setting sample: 30 (by default)
1.1.19 [508 (N)] [WCAG 12.3 (2)] Long list of options without grouping is found
Issue description: SELECT element should use OPTGROUP for long lists of options
Issue ID: 624
Issue detailed description: Count OPTION elements inside every SELECT or OPTGROUP. Compare this number with the defined threshold.
Issue settings
Parameter name: Max number of non-grouped options in SELECT element
Setting type: Threshold
Setting description: If the number of options not separated by OPTGROUP exceeds the threshold, Truwex reports this issue.
Setting sample: 10
1.1.20 [508 (N)] [WCAG 12.4 (2)] Form control without explicit label is found
Issue description: Form control should have non-empty explicit label, or at least non-empty title. Explicit label is a label tied with input by 'for'/'id' attributes.
Issue ID: 622
Issue detailed description: For every form control find its explicit label, i.e. LABEL element with 'for' attribute equal to control's 'id' attribute. If this label is not found, the error fires. Affected form controls: INPUT, TEXTAREA, SELECT (except of INPUT elements with type="hidden", "image", "submit", "reset" or "button").
Issue settings
Parameter name: Do not report control without explicit label if it has 'title' attribute specified
Setting type: Exception
Setting description: Form controls with non-empty 'title' attribute will be skipped from checking.
Setting sample: enabled (checked)
1.1.21 [508 (O)] [WCAG 13.6 (3)] Page without skip link
Issue description: A 'skip link' is one of the methods in providing a mechanism for users of assistive technologies to skip repetitive navigational links. Keyboard users also fully take advantages of this method. E.g. assume a page with navigation links at its top, and the links are coded in HTML before the page's main content. And if before the navigation bar a 'jump to main content' link will be provided, it will be very simple for users to access page content, in browser using TAB key or in screen reader.
Issue ID: 608
Issue detailed description: Check if the page has at least one skip link: find paired anchors (<A href="PageUrl#name"> and <A name="name">, where PageUrl is the URL of the analyzed page itself), if such pair is not found, the warning fires.
1.1.22 [508 (P)] Page requiring timed response must allow user to get more time
Issue description: Manual check. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Issue ID: 646
Issue detailed description: Manually check a page.
1.1.23 [WCAG 1.1,6.3 (1)] NOSCRIPT tag required on a page
Issue description: Manual check. Page contains JavaScript. If it adds information or important functionality to the page, the page needs meaningful NOSCRIPT tag to describe script function or provide alternative content
Issue ID: 614
Issue detailed description: Check if page has SCRIPT element but has no NOSCRIPT element with non-empty content.
1.1.24 [WCAG 1.3 (1)] Multimedia presentation requires auditory description
Issue description: Manual check. Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
Issue ID: 636
Issue detailed description: OBJECT, APPLET, or EMBED is found.
1.1.25 [WCAG 2.2 (2)] Low-contrast text is found
Issue description: Text color and its background color are too close: color difference should be no less than 400 and brightness difference should be no less than 125. Note: Contrast calculations here are based on colors specified via HTML markup. If colors you see by your eyes are in good contrast but Truwex says they are not, try to open your page in a browser with switched off images (set "Don't load images" option in FireFox or in Opera). It is possible that you use background images that make good contrast but without them the contrast is not good.
Issue ID: 610
Issue detailed description: Consider all visible elements with meaningful text (i.e. text containing at least one letter or digit). Get its text and background colors, calculate their brightness difference and color difference based on the formula from http://www.w3.org/TR/2000/WD-AERT-20000426#color-contrast. Note that W3C recommends 125 and 500 values as minimal brightness and color difference ranges correspondingly. However Truwex follows less tight restriction on color difference limit 400.
Issue settings
Parameter name: Color difference threshold (planned)
Setting type: Threshold
Setting description: Color difference threshold.
Setting sample: 400
Parameter name: Brightness difference threshold (planned)
Setting type: Threshold
Setting description: Brightness difference threshold.
Setting sample: 125
Parameter name: Valid text- and background-color combination (planned)
Setting type: Exception
Setting description: Valid text color and background color combination.
Setting sample: 0,0,0 vs. 1,1,1
1.1.26 [WCAG 2.2 (2)] Images must have sufficient contrast
Issue description: Manual check. Ensure that foreground and background color combinations on images provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
Issue ID: 648
Issue detailed description: Image is found in page's content, which seems to be not for decoration only (its size is more than 100 bytes).
1.1.27 [WCAG 3.1 (2)] Use markup instead of images where possible
Issue description: Manual check. When an appropriate markup language exists, use markup rather than images to convey information. For example, use MathML to mark up mathematical equations, and style sheets to format text and control layout. Also, avoid using images to represent text -- use text and style sheets instead.
Issue ID: 649
Issue detailed description: Image is found.
1.1.28 [WCAG 3.2 (2)] Doctype missing
Issue description: Include a document type declaration at the beginning of a document that refers to a published DTD (e.g., the strict HTML 4.0 DTD). !DOCTYPE statement is missing.
Issue ID: 620
Issue detailed description: !DOCTYPE statement is not found in the document.
1.1.29 [WCAG 3.2 (2)] Document must be valid
Issue description: Manual check. Create documents that validate to published formal grammars. Validate your document to the grammar specified in DOCTYPE.
Issue ID: 650
Issue detailed description: Document has !DOCTYPE statement. Manually check that document is valid to the specified grammar.
1.1.30 [WCAG 3.3 (2)] Do not use presentation elements
Issue description: The B and I elements should not be used; they are used to create a visual presentation effect. Instead use EM and STRONG for emphasis and style sheets for visual effects. Use 'text-align: center' instead of the deprecated CENTER element.
Issue ID: 643
Issue detailed description: CENTER, B, or I tag is found.
1.1.31 [WCAG 3.3 (2)] Use style sheets to control layout and presentation
Issue description: Manual check. Use style sheets to control layout and presentation. No STYLE tag or linked CSS file were found for the page.
Issue ID: 651
Issue detailed description: A page detected as not using styles.
1.1.32 [WCAG 3.3,3.5 (2)] Do not use headers and other structural markup only for visual effects
Issue description: Manual check. Use header elements according to specification. Do not use them only for presentational effects, e.g., for bold text. Do not use BLOCKQUOTE element for indents only. Do not use emphasis elements such as EM and STRONG for font effects only.
Issue ID: 653
Issue detailed description: H1-H6 tag, BLOCKQUOTE, EM, or STRONG tag is found on a page.
1.1.33 [WCAG 3.4 (2)] Fixed sizes are found
Issue description: Fixed sizes other than font-size property are found. This includes absolute units of measure in frame sizes and in inline styles of HTML buttons and other text containers
Issue ID: 632
Issue detailed description: Find cm, mm, in, pt, pc, px in sizes of frames, HTML buttons and other text containers.
1.1.34 [WCAG 3.4 (2)] Fixed fonts are found
Issue description: Use relative rather than absolute units in markup language attribute values and style sheet property values
Issue ID: 615
Issue detailed description: Find cm, mm, in, pt, pc, px font size units in styles of the visible page elements.
1.1.35 [WCAG 3.5, 12.3 (2)] Hardly reachable text for voice reader is found
Issue description: Percent of text, reachable by voice reader within a specified time limit, is less than the defined threshold. I.e. our estimation shows that less than 75% of page's text is reachable in 90 sec (these are the default values). In other words, it may take a long time for a user with screen reader software to reach certain parts of a web page. Consider using hierarchical headers H1, H2 etc. and skip links to create shortcuts for users of screen readers. Note: the Map shows only 10 the most hardly reachable text fragments.
Issue ID: 616
Issue detailed description: Text reaching time is calculated for the following elements: text node, image, form controls (form, select, input, text area). Intra-page skip links and headers are considered for finding the shortest route to the element. The length of the text in a text node and image's alts are considered. The share of content reachable within the specified threshold is calculated to detect the issue.
Issue settings
Parameter name: Time limit, sec
Setting type: Threshold
Setting description: Voice reader text reaching time limit, sec. The time below this parameter considered as good.
Setting sample: 90
Parameter name: Reachable text percent threshold
Setting type: Threshold
Setting description: Voice reader percent threshold for texts reachable within specified amount of time.
Setting sample: 75
1.1.36 [WCAG 3.5 (2)] Use header elements to convey document structure
Issue description: Manual check. Use header elements to convey document structure. Header H1 was not detected on this page.
Issue ID: 652
Issue detailed description: H1 tag is not found on a page.
1.1.37 [WCAG 3.6 (2)] Mark up lists
Issue description: Manual check. Mark up lists and list items properly. If your page contains logical lists, mark up them with UL for unordered list, OL for ordered list, DL for definition list and LI for list item. Do not use tables with bullet images to imitate unordered lists. Do not use numbers in text for ordered lists: e.g., a line contains '1.1 Chapter' text and the next line contains '1.2 Next chapter' text.
Issue ID: 654
Issue detailed description: Manually check a page.
1.1.38 [WCAG 3.7 (2)] Mark up quotations
Issue description: Manual check. Mark up quotations with Q and BLOCKQUOTE elements.
Issue ID: 655
Issue detailed description: Manually check a page.
1.1.39 [WCAG 4.1 (1)] Changes in the natural language must be clearly identified
Issue description: Manual check. Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions)
Issue ID: 639
Issue detailed description: Manually check a page.
1.1.40 [WCAG 4.3 (3)] Document language markup is missing
Issue description: Identify the primary natural language of a document: set the 'lang' attribute on the HTML element
Issue ID: 631
Issue detailed description: <HTML> tag has no 'lang' attribute.
1.1.41 [WCAG 5.3 (2)] Do not use tables for layout if they can not be linearized properly
Issue description: Manual check. 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).
Issue ID: 656
Issue detailed description: Warning for tables, recognized as layout ones and having no data table markup.
1.1.42 [WCAG 5.4 (2)] Do not use data table markup for layout tables
Issue description: Manual check. If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
Issue ID: 657
Issue detailed description: Warning for tables, recognized as layout ones yet having data table markup.
1.1.43 [WCAG 6.2 (1)] Equivalents for dynamic content must be updated when the dynamic content changes
Issue description: Manual check. Ensure that equivalents for dynamic content are updated when the dynamic content changes.
Issue ID: 641
Issue detailed description: Manually check OBJECTs, APPLETs, EMBEDs, SCRIPTs, FRAMEs, and IFRAMEs.
1.1.44 [WCAG 6.3 (1) ,6.5 (2)] Script based link is found
Issue description: Script based links become not accessible with scripts turned off. Avoid using script links or provide a text equivalent with the NOSCRIPT element, or provide an alternative accessible page.
Issue ID: 619
Issue detailed description: Select links with 'href' attributes starting with "javascript:". Check if this link has corresponding NOSCRIPT element with alternative link inside it.
1.1.45 [WCAG 6.4, 9.3 (2)] Device-dependent event handler is found
Issue description: Elements with specified mouse event handlers should also have paired keyboard event handlers. E.g. 'OnClick' and 'OnKeyPress', 'OnMouseOver' and 'OnFocus' etc.
Issue ID: 618
Issue detailed description: Select all elements with 'onclick', 'onmousedown', or 'ondblclick' mouse event handlers (except of A elements with 'onclick'). Check if these elements also have non-empty paired keyboard event handler 'onkeydown' or 'onkeypress'. Check if elements with OnMouseUp, OnMouseOver, or OnMouseOut event handler also have OnKeyUp, OnFocus, OnBlur event handlers correspondingly. Find elements with OnMouseMove or OnDrop attributes specified - no paired keyboard event handlers exist for these mouse event handlers.
1.1.46 [WCAG 6.4 (2)] If objects use event handlers, they must be accessible without a mouse too
Issue description: Manual check. For scripts and applets, ensure that event handlers are input device-independent.
Issue ID: 658
Issue detailed description: Manually check OBJECs, APPLETs, and EMBEDs.
1.1.47 [WCAG 6.5 (2)] Noframes for frameset required
Issue description: Ensure that dynamic content is accessible or provide an alternative presentation or page. E.g., provide NOFRAMES for each FRAMESET tag.
Issue ID: 660
Issue detailed description: FRAMESET without NOFRAMES inside it found.
1.1.48 [WCAG 7.1 (1); 7.2,7.3 (2)] Blink text is found
Issue description: BLINK or MARQUEE elements or 'TEXT-DECORATION: blink' style is found
Issue ID: 611
Issue detailed description: Find BLINK or MARQUEE elements, or visible elements with 'TEXT-DECORATION: blink' style. Blinking text may cause problem for people with certain disabilities.
1.1.49 [WCAG 7.1 (1); 7.2,7.3 (2)] Avoid flickering, blinking and movement in pages
Issue description: Manual check. 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). Until user agents allow users to freeze moving content, avoid movement in pages. Check objects, applets and scripts.
Issue ID: 659
Issue detailed description: Manually check OBJECTs, APPLETs, EMBEDs, and SCRIPTs.
1.1.50 [WCAG 7.4,7.5 (2)] Refresh meta is found
Issue description: Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. Example of auto-redirecting code: META http-equiv='refresh' content='5;URL=http://www.example.com/newpage'. Example of auto-refreshing code: META http-equiv='refresh' content='60'
Issue ID: 661
Issue detailed description: Warning for non-empty refresh meta found: <META http-equiv='refresh' content=' some_value'>
1.1.51 [WCAG 8.1 (1)] Programmatic elements must be directly accessible
Issue description: Manual check. Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
Issue ID: 642
Issue detailed description: Manually check OBJECTs, APPLETs, EMBEDs, and SCRIPTs.
1.1.52 [WCAG 9.2 (2)] Object interface must be accessible without a mouse too
Issue description: Manual check. Ensure that any element that has its own interface can be operated in a device-independent manner. Check objects and applets.
Issue ID: 663
Issue detailed description: Manually check OBJECTs, APPLETs, and EMBEDs.
1.1.53 [WCAG 9.3 (2)] Inaccessible select menu
Issue description: Do not code OnChange event on SELECT element for reload page or navigate to a new page: this drop-down list will be virtually unusable for keyboard users (relates to 'open' select menu only, not to pu