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 pull-down menu).
Issue ID: 613
Issue detailed description: Find 'open' SELECT element with 'onchange' attribute specified. Make sure that this event handler is not used for navigating to a new page.
1.1.54 [WCAG 10.1 (2)] New browser window is detected
Issue description: 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 page opens a new Internet Explorer browser window.
Issue ID: 664
Issue detailed description: The page opens a new Internet Explorer window without a user intervention.
1.1.55 [WCAG 10.1 (2)] Popup dialog window is detected
Issue description: 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. Popup dialog window is detected.
Issue ID: 665
Issue detailed description: Pop-up window is detected while opening a web page in Internet Explorer. E.g. java script error, java script dialog, active-x or certificate prompts. Look to the page properties and find details about this window in Issues tab.
1.1.56 [WCAG 10.2 (2)] Implicit labels must be properly positioned
Issue description: Manual check. For all form controls with implicitly associated labels, ensure that the label is properly positioned. The label must immediately precedes its control on the same line (allowing more than one control/label per line) or be in the line preceding the control (with only one label and one control per line).
Issue ID: 666
Issue detailed description: The same condition, as for "Form controls without explicit label is found" issue.
1.1.57 [WCAG 11.1 (2)] Use the latest W3C technologies available whenever possible
Issue description: Manual check. Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
Issue ID: 667
Issue detailed description: Manually check the page.
1.1.58 [WCAG 11.2 (2)] Avoid deprecated language features
Issue description: Avoid deprecated features of W3C technologies: e.g., APPLET, BASEFONT, CENTER, DIR, FONT, ISINDEX, MENU, S, STRIKE, U elements, 'font' and 'size' attributes.
Issue ID: 668
Issue detailed description: Deprecated elements are found: APPLET, BASEFONT, CENTER, DIR, FONT, ISINDEX, MENU, S, STRIKE, U.
1.1.59 [WCAG 12.2 (2)] Provide additional information for framesets
Issue description: Manual check. Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. Use 'longdesc' attribute for FRAME. Use NOFRAMES element for alternative content to the FRAMESETs.
Issue ID: 662
Issue detailed description: This warning is reported when page contains FRAMESET tag. Manually check is required.
1.1.60 [WCAG 13.1 (2)] Link name/destination clash
Issue description: Two links with the same text should go to the same page; otherwise their 'title' attributes should differ.
Issue ID: 606
Issue detailed description: Consider links with non-empty names (inner text) and non-empty non-javascript 'href' attributes. Find two links with the same names, different hrefs and without titles or with the same titles. Names comparison is case-insensitive; titles comparison is case-sensitive; hrefs are compared as full valid URLs and are equal when coincided.
1.1.61 [WCAG 13.1 (2)] Non-meaningful link name is found
Issue description: Link text should be meaningful, e.g. 'Click here' is a bad link name
Issue ID: 607
Issue detailed description: Get page links. Consider their names, i.e. texts inside A elements. Compare these names with the specified list of "bad" link names. String comparison is case-insensitive.
Issue settings
Parameter name: Bad links names list
Setting type: Pattern
Setting description: List of "bad" link names. If hyperlink text matches a pattern, Truwex reports this issue.
Setting sample: "click here"
1.1.62 [WCAG 13.2 (2)] Metadata are missing
Issue description: Manual check. Provide metadata to add semantic information to pages and sites: e.g., provide non-empty TITLE, use META, LINK elements.
Issue ID: 669
Issue detailed description: No TITLE or any META tag were found in page's HEAD.
1.1.63 [WCAG 13.3,13.4 (2)] Provide clear and consistent navigation
Issue description: Manual check. Provide information about the general layout of a site (e.g., a site map or table of contents). In describing site layout, highlight and explain available accessibility features. Use navigation mechanisms in a consistent manner.
Issue ID: 670
Issue detailed description: Manually check the page.
1.1.64 [WCAG 14.1 (1)] The clearest and simplest language must be used
Issue description: Manual check. Use the clearest and simplest language appropriate for a site's content.
Issue ID: 644
Issue detailed description: Manually check the page.
1.1.65 [WCAG 14.3 (3)] Inline styles are found
Issue description: Use linked style sheets rather than embedded styles, and avoid inline style sheets
Issue ID: 612
Issue detailed description: Check all visible elements for presence of 'style' attribute. [WCAG requirement]
1.1.66 [WCAG-2 1.4 (2)] Low luminosity contrast text is found
Issue description: Luminosity contrast ratio between text and background behind the text should be equal to or greater than 5:1, except if the text is pure decoration. Larger-scale text (at least 18 point or 14 point bold) can have a contrast ratio of 3:1. This is the WCAG 2.0 priority 2 (AA) requirement and it often gives the result different from WCAG 1.0 color contrast checks. 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: 671
Issue detailed description: This check is similar to WCAG1 color contrast check, except of the algorithm used to compare colors. Refer to http://www.w3.org/TR/2007/WD-WCAG20-20070517/#contrast-ratiodef to see contrast ratio formula.
1.1.67 Frame is detected
Issue description: Use of frames may cause different accessibility problems
Issue ID: 629
Issue detailed description: Find FRAME or IFRAME elements.
1.2 Issue category: Privacy compliance
1.2.1 Privacy policy link is missing
Issue description: Privacy policy link is missing, or has incorrect text, or has incorrect URL. Privacy policy link is a link that refers to a site privacy policy written in a human-readable form. Corporate standards often require this link to be presented on every page of a website. Solution: check a privacy link presence on a web page. If it is missing, add it. If it is present, check issue's settings to detect a privacy link correctly.
Issue ID: 501
Issue detailed description: Truwex looks for a link on a web page that meets all the following set of requirements:
its URL matches the pattern set in the 'Privacy Link: URL' parameter;
its text matches the pattern set in the 'Privacy Link: Text' parameter;
page language code is equal to the 'Privacy Link: Language' parameter;
page country code is equal to one set the 'Privacy Link: Country' parameter.
The first match is considered as a privacy policy link. If it's not found, Truwex detects an error. All these four parameters create a set which define privacy link spelling, text, language, country. This set helps to verify privacy links for multi-lingual websites. To work correctly, language detection module has to be enabled and set up.
For a single language website some of them, like language or country can be omitted.
Issue settings
Parameter name: Privacy Link: URL
Setting type: pattern
Setting description: Regular expression for Privacy policy link URL. Case-insensitive. Obligatory parameter.
Setting sample: (privacy|policy)
\/privacystuff\.html
http://example.com/privacy.html
Parameter name: Privacy Link: Text
Setting type: pattern
Setting description: Regular expression for Privacy policy link text. Case-sensitive. Optional parameter.
Setting sample: (p|P)rivacy\b
Privacy\sStuff
Parameter name: Privacy Link: Language
Setting type: pattern
Setting description: Two-letter ISO language code. Optional parameter.
Setting sample: en
Parameter name: Privacy Link: Country
Setting type: pattern
Setting description: Two-letter ISO country code. Optional parameter.
Setting sample: us
Parameter name: Privacy Link: Values
Setting type: pattern
Setting description: String with comma-separated list combined of parameters specified above.
Setting sample: This string is filled automatically when the user specifies the preceding parameters and clicks 'Add' button:
(privacy|policy),(p|P)rivacy\b,en,us
\/privacystuff\.html,Privacy\sStuff,,
1.2.2 Web beacon with cookies is found
Issue description: Web beacon usually is a small image used to track visitor activity on a web site. Truwex detected an image, which has different domain than a web page and sets a cookie. Possible reasons: (1) your website loads images, scripts or other content from a website with a different domain name, (2) a web page uses online web analytics service from a third party vendor. To fix this problem, find the elements with the detected URLs and (1) remove them, if you do not need these elements, or (2) place detected third party domain to issue's exception lists, if the element is valid. Note: some cookies can be set during JavaScript execution in a browser window; therefore they might me not visible in page's HTML source.
Issue ID: 505
Issue detailed description: Truwex looks for a third-party images (also called 'web beacons') on a page and for each beacon checks if it sets a cookie or not.
Issue settings
Parameter name: Web beacons with cookies URLs exception list
Setting type: exception
Setting description: Truwex will not report an error for a web beacon that sets a cookie if beacon's source URL is started from one of the strings in the exception list.
Setting sample: http://thirdparty.com/mybeacons/
1.2.3 Web beacon without cookies is found
Issue description: Web beacon usually is a small image used to track visitor activity on a web site. Truwex detected an image, which has different domain than a web page and does not set a cookie. Most likely it is a content or design image from a third party server. To fix this problem, find the elements with the detected URLs and (1) remove them, if you do not need these elements, or (2) place detected third party domain to issue's exception lists, if the element is valid.
Issue ID: 504
Issue detailed description: Truwex looks for a third-party images (also called 'web beacons') on a page and for each beacon checks if it sets a cookie or not.
Issue settings
Parameter name: Web beacons without cookies URLs exception list
Setting type: exception
Setting description: Truwex will not report an error for web beacon that does not set a cookie if beacon's source URL is started with some value from the exception list.
Setting sample: http://thirdparty.com/mybeacons/
1.2.4 Third-party cookies are found
Issue description: A web page sets a cookie from a third-party domain. Possible reasons: (1) your website loads images, scripts or other content from a website with a different domain name, (2) a web page uses online web analytics service from a third party vendor. To fix this problem, find the elements with detected URLs and (1) remove them, if you do not need these elements, or (2) place detected third party domain to issue's exception lists, if the element is valid. Note: some cookies can be set during JavaScript execution in a browser window; therefore they might be not visible in page's HTML source.
Issue ID: 513
Issue detailed description: Truwex accepts cookies and their properties: name, value, domain, path, secure, expire date. It compares cookie's domain with the page one. If they have the same minimal level domain, cookie is a first-party one. In the other case it's a third-party cookie.
Issue settings
Parameter name: Third-party cookies domains exception list
Setting type: exception
Setting description: Exception list of cookies domains. Third-party cookie with 'domain' property from this list will not be treated as erroneous.
Setting sample: .example.com; top.example.com
1.2.5 Third party links are found
Issue description: Hyperlink to a web page with a different domain name is found. Corporate privacy standards may restrict the use of third-party links. Some techniques may be required to inform user that she leaves corporate website, i.e. by providing intermediate warning page with two options, to return back or to proceed.
Issue ID: 511
Issue detailed description: The purpose is to detect non-desirable hyperlinks on website. Truwex generates this error if it finds links with domain different from the analyzed page and not listed in the exceptions. Since Truwex analyzes only web pages within the defined website directories, it is the same as a website is linked to another. Example: page hosted at example.com links to pages hosted at thirdparty.com or at example.org.
Issue settings
Parameter name: Third party links exception list
Setting type: exception
Setting description: Truwex will not report an error for third-party link if its URL is started with a string from the exception list.
Setting sample: http://myfriend.com/; http://john.myfriend.com/
1.2.6 Long-life persistent cookie is found
Issue description: Persistent cookie with lifetime period more than specified years number is found
Issue ID: 508
Issue detailed description: This issue compare cookies lifetime with corporate privacy policy. Truwex receives cookies and their properties: name, value, domain, path, secure, expiration date. It calculates cookie lifetime years based on cookie expiration date. Then it compares the result with the predefined parameter.
Issue settings
Parameter name: Cookie lifetime years maximum
Setting type: threshold
Setting description: Maximum of cookie lifetime years. If a cookie with lifetime years exceeds this value, Truwex reports an error.
Setting sample: 30
1.2.7 Cookie restricted by IE6 is found
Issue description: Cookie restricted by IE6 (accepted, but downgraded to a session cookie) is found for privacy level set to X.
Issue ID: 506
Issue detailed description: See the issue 507 description for explanation how Truwex collects cookie data. Restricted cookie means that IE downgraded it:
For High browser security level: cookies can not be downgraded.
For MediumHigh browser security level: cookies can not be downgraded.
For Medium browser security level: first-party persistent cookie with unsatisfactory compact policy.
For Low browser security level third-party cookie can be downgraded if:
It has no compact policy;
It has unsatisfactory compact policy.
Issue settings
Parameter name: Browser security level settings
Setting type: option
Setting description: IE6 security level settings: High, MediumHigh, Medium, or Low.
Setting sample: Medium
Parameter name: Cookies domains exception list
Setting type: exception
Setting description: Exception list for cookies domains. Blocked cookies with domains from this list will not be reported as erroneous.
Setting sample: example.com
1.2.8 Cookie blocked by IE6 is found
Issue description: Cookie blocked by IE6 (rejected) is found for privacy level set to X.
Issue ID: 507
Issue detailed description: Truwex detects cookies set by IE and stores properties: name, value, domain, path, secure, expiration date. Using this information, it concludes whether the cookie is session or persistent, first- or third-party. It finds who sets a cookie: the page itself (e.g. using JavaScript SetCookie function or by page's HTTP response headers), a web beacon, or some other page element (e.g. frame). Truwex checks compact policy for this cookie: if a cookie set by a web beacon, receives compact policy string from beacon's HTTP response headers, for other cookies it gets compact policy string from the page's HTTP response headers.
Basing on this information Truwex models IE6 cookie designation (accept, leash, downgrade, or deny) depending on the browser security level settings parameter. Blocked cookie is the one that was treated as denied:
For high security level it can be any persistent cookie with following problems:
with no compact policy;
with unsatisfactory compact policy;
if the opt-out attribute is present in compact policy.
For MediumHigh security level:
in case of third-party cookie:
with no compact policy;
with unsatisfactory compact policy;
if the opt-out attribute is present in compact policy;
in case of first-party persistent cookie with unsatisfactory compact policy.
For Medium security level it can be third-party persistent cookie with following problems:
no compact policy;
unsatisfactory compact policy.
For Low security level cookies are not denied.
Check the 'Privacy in Internet Explorer 6' technical article in the MSDN library for explanations what is 'unsatisfactory' compact policy, 'opt-out' attribute, 'leash', 'downgrade', etc. It also possible to learn this topic from the presentation: http://www.microsoft.com/winme/01mitt/01may/15364/features/
Issue settings
Parameter name: Browser security level settings
Setting type: option
Setting description: IE6 security level settings: High, MediumHigh, Medium, or Low.
Setting sample: Medium
Parameter name: Cookies domains exception list
Setting type: exception
Setting description: Exception list for cookies domains. Blocked cookies with domains from this list will not be reported as erroneous.
Setting sample: example.com
1.2.9 Mailto link is used
Issue description: Generally there are two situations when mailto links should be avoided. Firstly, if this link is a user email address published on a site, it may violate user's privacy. Secondly, if this mailto link is provided to users as a way of communication with website administration staff, e.g. 'feedback to webmaster john.doe@example.com'. Corporate standards often prohibit such practice for many reasons, e.g. employees may change so the addresses may become obsolete.
Issue ID: 512
Issue detailed description: A link with 'mailto' protocol is found on a page.
Issue settings
Parameter name: Mailto emails exception list. If Truwex finds email, which matches one from exception list, it does not report an issue.
Setting type: exception
Setting description: Exception list of mailto links.
Setting sample: mailto:info@example.com
1.2.10 Form with method GET is used
Issue description: Forms with method GET may cause data leaks from a web page. Use POST instead.
Issue ID: 503
Issue detailed description: Truwex collects all forms with method get and generate an issue with those, which does not match exceptions.
Issue settings
Parameter name: Form with method GET: name exception list
Setting type: exception
Setting description: Exception list of form names ('name' attribute of FORM tag). If a form has name, which matches this parameter, Truwex does not report this issue.
Setting sample: searchForm
Parameter name: Form with method GET: id exception list
Setting type: exception
Setting description: Exception list of form 'id' attribute. If a form has ID, which matches this parameter, Truwex does not report this issue.
Setting sample: searchForm
Parameter name: Form with method GET: action exception list
Setting type: exception
Setting description: Exception list of form 'action' attribute. If a form has action, which name matches this parameter, Truwex does not report this issue.
Setting sample: http://example.com/search
1.2.11 P3P policy reference file is missing
Issue description: P3P policy reference file is not found neither in well-known location on a site, nor in a page's http response header, nor in a link tag on a page
Issue ID: 502
Issue detailed description: First, Truwex checks a well-known location on a web site: the path "/w3c/p3p.xml" at the root directory of a site (e.g. www.example.com/w3c/p3p.xml). If this file is not found or it contains a not-valid XML, it looks to a page's P3P HTTP response header and tries to find URI of a policy reference file in the 'policyref' field. If the URI is not found, it checks <link rel="P3Pv1" href="URI"> element and tries to obtain URI from its 'href' attribute. If policy reference file URI is found, Truwex tries to load this file. If the file contains a valid xml, all is ok. Otherwise the error will be reported. Read more about P3P standard on W3C site: W3C P3P specification
1.2.12 P3P policyref must be in double quotes
Issue description: Policyref string in P3P http-header must be enclosed in double quotes
Issue ID: 510
Issue detailed description: This issue enforces correct syntax for P3P. Truwex receives page's P3P HTTP response header. If it contains policy reference file URI field 'policyref', Truwex checks its content to be in double quotes.
1.2.13 P3P compact policy must be in double quotes
Issue description: Compact policy string in P3P http-header must be enclosed in double quotes
Issue ID: 509
Issue detailed description: Truwex gets page's P3P HTTP response header. If it contains compact policy field 'CP', it checks that its content is enclosed in double quotes.
1.2.14 PII: Page collects PII
Issue description: Form inputs collecting personally identifiable information (PII) are found. E.g. first name, last name, e-mail and other inputs defined in the issue settings.
Issue ID: 514
Issue detailed description:
Issue settings
Settings group: COPPA common - PII inputs settings
Parameter name: Name pattern
Setting type: pattern
Setting description: Regular expression pattern to search in 'name' attributes of form inputs
Setting sample: email
Parameter name: Label pattern
Setting type: pattern
Setting description: Regular expression pattern to search in label text of form inputs.
Setting sample: e-?mail\s
Parameter name: Input text pattern
Setting type: pattern
Setting description: Regular expression pattern to search in default texts of form inputs.
Setting sample: (e-?mail)|@
Parameter name: Surround text pattern (planned)
Setting type: pattern
Setting description: Regular expression pattern to search in text elements situated near form inputs.
Setting sample: e-?mail
1.2.15 PII: Page collects age data
Issue description: Form input collecting age is found. E.g. birth year, age or other related form inputs defined in the issue settings. If the age data is collected together with any personally identifiable information (PII), it's strongly advised to examine COPPA policy implementation on a web page.
Issue ID: 515
Issue detailed description:
Issue settings
Settings group: COPPA common - Age inputs settings
Parameter name: Name pattern
Setting type: pattern
Setting description: Regular expression pattern to search in 'name' attributes of form inputs
Setting sample: dob.*year
Parameter name: Label pattern
Setting type: pattern
Setting description: Regular expression pattern to search in label text of form inputs.
Setting sample: age.*range
Parameter name: Input text pattern
Setting type: pattern
Setting description: Regular expression pattern to search in default texts of form inputs.
Setting sample: birth
Parameter name: Surround text pattern (planned)
Setting type: pattern
Setting description: Regular expression pattern to search in text elements situated near form inputs.
Setting sample: birth
Parameter name: Enable automatic age input detection
Setting type: parameter
Setting description: When enabled, some conditions are checked automatically to find age input. These conditions do not depend on settings. E.g. dropdowns are analyzed if they contain long lists of years or age range lists.
Setting sample: enabled (checked)
1.2.16 PII: Page collects age revealing information
Issue description: Form inputs collecting age revealing information are found. E.g. school grade, education level and other inputs defined in issue settings. If such questions force users to reveal their age and moreover, the site collects any personally identifiable information (PII), it's strongly advised to examine COPPA policy implementation on a web page.
Issue ID: 516
Issue detailed description:
Issue settings
Settings group: COPPA common - Age revealing inputs settings
Parameter name: Name pattern
Setting type: pattern
Setting description: Regular expression pattern to search in 'name' attributes of form inputs
Setting sample: education
Parameter name: Label pattern
Setting type: pattern
Setting description: Regular expression pattern to search in label text of form inputs.
Setting sample: education
Parameter name: Input text pattern
Setting type: pattern
Setting description: Regular expression pattern to search in default texts of form inputs.
Setting sample: high\sschool
Parameter name: Surround text pattern (planned)
Setting type: pattern
Setting description: Regular expression pattern to search in text elements situated near form inputs.
Setting sample: education
1.2.17 PII: Page collects PII and opt-in/opt-out inputs are missing
Issue description: Opt-in/opt-out input is not found on a web page that collects personally identifiable information (PII). Opt-in/opt-out input is required to obtain a recipient agreement to receive a newsletter or other promotions. Opt-in/opt-out input is checkbox, radio button or select and its criteria are defined in the issue settings. PII inputs are defined in settings for personally identifiable information (PII) issues group.
Issue ID: 522
Issue detailed description: Checkboxes, radio buttons and dropdowns are analyzed.
Issue settings:
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Opt-in/opt-out checkboxes settings
Parameter name: Name pattern
Setting type: pattern
Setting description: Regular expression pattern to search in 'name' attributes of form inputs
Setting sample: newsletter
Parameter name: Label pattern
Setting type: pattern
Setting description: Regular expression pattern to search in label text of form inputs.
Setting sample: subscribe.*newsletter
Parameter name: Surround text pattern (planned)
Setting type: pattern
Setting description: Regular expression pattern to search in text elements situated near form inputs.
Setting sample: subscribe.*newsletter
1.2.18 PII: Page collects PII and has prechecked opt-in/opt-out inputs
Issue description: Pre-checked opt-in/opt-out input is found on a page that collects PII. Opt-in/opt-out input is required to obtain a recipient agreement to receive a newsletter or other promotions. Pre-selecting opt-in/opt-out input is a not a good practice, since a visitor may subscribe by mistake. Opt-in/opt-out input is checkbox, radio button or select and its criteria are defined in the issue settings. PII inputs are defined in settings for personally identifiable information (PII) issues group.
Issue ID: 523
Issue detailed description:
Issue settings:
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Opt-in/opt-out checkboxes settings - the same settings as in the previous issue 'PII: Page collects PII and opt-in/opt-out inputs are missing' (522).
1.2.19 PII: COPPA: Page collects PII and contains inputs collecting forbidden PII
Issue description: Form inputs collecting forbidden PII from children are found on page that collects PII. Forbidden inputs are defined in issue settings and personally identifiable information (PII) inputs are defined in PII issues group general settings. This issue is useful if the site is known to be oriented to children under 13 and site internal policies prohibit to collect some PII from children prior the parental consent will be received.
Issue ID: 525
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Forbidden PII inputs settings:
Parameter name: Name pattern
Setting type: pattern
Setting description: Regular expression pattern to search in 'name' attributes of form inputs
Setting sample: address
Parameter name: Label pattern
Setting type: pattern
Setting description: Regular expression pattern to search in label text of form inputs.
Setting sample: address
Parameter name: Input text pattern
Setting type: pattern
Setting description: Regular expression pattern to search in default texts of form inputs.
Setting sample: address
Parameter name: Surround text pattern (planned)
Setting type: pattern
Setting description: Regular expression pattern to search in text elements situated near form inputs.
Setting sample: address
1.2.20 PII: COPPA: Page collects PII and does not ask parent email
Issue description: Parental e-mail form input is not found on page that collects personally identifiable information (PII). Email input is defined in issue settings. If a web site chooses COPPA strategy, i.e. it's oriented for children under 13, it must ask for parental consent of child registration.
Issue ID: 524
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Parent email inputs settings:
Parameter name: Name pattern
Setting type: pattern
Setting description: Regular expression pattern to search in 'name' attributes of form inputs
Setting sample: parent.*email
Parameter name: Label pattern
Setting type: pattern
Setting description: Regular expression pattern to search in label text of form inputs.
Setting sample: parent.*e-?mail\s
Parameter name: Input text pattern
Setting type: pattern
Setting description: Regular expression pattern to search in default texts of form inputs.
Setting sample: parent.*e-?mail
Parameter name: Surround text pattern (planned)
Setting type: pattern
Setting description: Regular expression pattern to search in text elements situated near form inputs.
Setting sample: parent.*e-?mail
1.2.21 PII: COPPA: Page collects PII and has no kids privacy policy link
Issue description: Children privacy policy link is not found on a page that collects PII. Link is defined in issue settings and personally identifiable information (PII) inputs are defined in PII issues group general settings. This issue belongs to COPPA strategy issues group (i.e. it means that the page is known to be oriented to children under 13) and states that page collecting PII should have special kids privacy policy link.
Issue ID: 526
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Children privacy policy link settings:
Parameter name: URL
Setting type: pattern
Setting description: Regular expression for Privacy policy link URL. Case-insensitive. Obligatory parameter.
Setting sample: (privacy|policy)
Parameter name: Privacy Link: Text
Setting type: pattern
Setting description: Regular expression for Privacy policy link text. Case-sensitive. Optional parameter.
Setting sample: [Kk]ids.*[Pp]rivacy\b
Parameter name: Privacy Link: Language
Setting type: pattern
Setting description: Two-letter ISO language code. Optional parameter.
Setting sample: en
Parameter name: Privacy Link: Country
Setting type: pattern
Setting description: Two-letter ISO country code. Optional parameter.
Setting sample: us
Parameter name: Privacy Link: Values
Setting type: pattern
Setting description: String with comma-separated list combined of parameters specified above.
Setting sample: This string is filled automatically when the user specifies the preceding parameters and clicks 'Add' button:
(privacy|policy),[Kk]ids.*[Pp]rivacy\b,en,us
1.2.22 PII: No COPPA: Page collects PII and age data
Issue description: Form input collecting age data is found on a page that collects personally identifiable information (PII). The issue belongs to "No COPPA" strategy: if a web site plans not to fall under the COPPA requirements, it should not gather personally identifiable information (PII) from children under 13. Inputs are defined in PII issues group general settings.
Issue ID: 521
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Age inputs settings: see 'COPPA common - age inputs settings' group in description of issue 'PII: Page collects PII' (515)
1.2.23 PII: No COPPA: Page collects PII and age revealing information
Issue description: Form input collecting information, which may reveal user's age is found on a web page that collects personally identifiable information (PII). The issue belongs to "No COPPA" strategy, i.e. if a web site plans not to fall under the COPPA requirements by not gathering PII from children under 13, it should not ask for age in direct or indirect ways. Age related inputs are defined in PII issues group general settings.
Issue ID: 517
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Age revealing inputs settings: see 'COPPA common - age revealing inputs settings' group in description of issue 'PII: Page collects PII' (516)
1.2.24 PII: No COPPA: Page collects PII and is oriented towards children
Issue description: Page falls under children-oriented pages URLs list and collects PII. Therefore COPPA is applicable to this page while the site chooses No COPPA strategy. The list of URLs is defined in issue settings.
Issue ID: 520
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Children pages settings:
Parameter name: Children pages starting URLs
Setting type: exception
Setting description: URLs of pages oriented towards children
Setting sample: http://www.example.com/forkids.html
1.2.25 PII: No COPPA: Page collects PII and contains disclaimers
Issue description: Disclaimer text is found on a page that collects personally identifiable information (PII). Disclaimer text is defined in issue settings. For example, it may be "You must be 13 years of age or older to use this site" - this text may encourage a user to falsify her/his age.
Issue ID: 518
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Disclaimer settings:
Parameter name: Disclaimer text pattern
Setting type: pattern
Setting description: Disclaimer text to find and report.
Setting sample: You must be 13 years of age or older to
1.2.26 PII: No COPPA: Page collects PII and does not contain disclaimers
Issue description: Disclaimer text is not found on page that collects personally identifiable information (PII). Disclaimer texts are defined in issue settings. It may be some assurance statement, e.g. "E-mail entered here will be used only for the purpose of delivering subscriptions.
Issue ID: 519
Issue detailed description:
Issue settings
PII inputs settings: see 'COPPA common - PII inputs settings' group in description of issue 'PII: Page collects PII' (514)
Disclaimer settings: the same settings as in the previous issue 'PII: No COPPA: Page collects PII and contains disclaimers' (518)
1.2.27 Language detection
Truwex detects page country and language using the following methods:
- Language by html document character set
- Country by language if possible
- Language and country by lang attribute of html or body tags
- Language and country by custom meta tag
- Language and country by page url
- Language and country by specified custom rule
A user can check any number of these methods. By default only the first three methods are selected.
First, Truwex subsequently (in the order specified above) applies selected methods for language detection. If on some step it succeeds, or if all steps are passed by, Truwex repeats the same procedure, this time for country detection. The detailed description of each method and its parameters is provided below.
1) By html document character set
Description: Truwex uses some correlation between charset and language. If only one language matches this particular charset (retrieved from the page's meta information), the language is found.
2) Country by language if possible
Description: This works when the page language is already detected. Truwex uses some correlation between language and possible countries. If only one country matches this particular language, the country is found.
3) By lang attribute of html or body tags
Description: Parse "lang" attribute of HTML or BODY tag as having the following format: lang="ll" or lang="ll-cc", where ll - 2-letter language code, cc - 2-letter country code, both codes are case insensitive. Example: <html lang="en-US">, <html lang="ru">. Thus language and (or) country may be detected.
4) By custom meta tag
Description: Find meta tag with the name specified in parameter. Parse it to find language and (or) country. HTML code samples: <meta name="Example.Language" content="en-US" />, <meta name="Example.Country" content="US" />.
Settings
Parameter name: Language meta name
Setting type: parameter
Setting description: Find META tag with "name" attribute equal to specified value. Parse its "content" attribute as having the following format: content="ll" or content="ll-cc", where ll - 2-letter language code, cc - 2-letter country code, both codes are case insensitive.
Setting sample: Example.Language
Parameter name: Country meta name
Setting type: parameter
Setting description: Find META tag with "name" attribute equal to specified value. Parse its "content" attribute as having the following format: content="cc", where cc - 2-letter country code, which is case insensitive.
Setting sample: Example.Country
5) By page url
Description: Parse page URL according to pattern specified in parameter to find language and (or) country.
Settings
Parameter name: Page URL pattern
Setting type: parameter
Setting description: Page URL pattern regular expression, where <cc> is a substitute for 2-letter country code, <ll> (<lll>) is a substitute for 2- (3-) letter language code. Regular expression is case insensitive. If both <ll> and <lll> are captured, the first code has a preference over the second.
Setting sample: /country/<cc>/<ll>/
6) By specified custom rule
Description: In contrast to methods #1 or #2, where Truwex uses its own intrinsic correlations, here that's the user who sets the rules: he links some specific text to some country and (or) language. The desired text is specified via text regular expression pattern and via some restrictions on elements containing this text: seek text in any element or in elements with particular name, in element's text content or in attribute. Truwex checks these rules one after another. For every rule, it selects nodes from the page according to specified element restrictions, and applies regular expression pattern. If a matched text is found, Truwex gets country and (or) language from this rule and stops checking the other rules.
Settings
Parameter name: Element name
Setting type: parameter
Setting description: Element name, or *, or empty string. Empty string and "*" mean the same: search in any element.
Setting sample: a
Parameter name: Attribute name
Setting type: parameter
Setting description: Attribute name, or *, or empty string. "*" means to search in any attribute, empty string means to search not in attribute, but in element's content.
Setting sample: href
Parameter name: Text pattern
Setting type: parameter
Setting description: Text regular expression pattern, case sensitive.
Setting sample: /country/us/en/privacy\.html
Parameter name: Language
Setting type: parameter
Setting description: 2-letter language code selected from a list
Setting sample: en
Parameter name: Country
Setting type: parameter
Setting description: 2-letter country code selected from a list
Setting sample: us
1.3 Issue category: Search Engine Optimization
1.3.1 A web page is not indexed in MSN
Issue description: MSN operator site:[web page url] does not return the web page information.
Issue ID: 901
Issue detailed description:
1.3.2 A web page is not indexed in Yahoo
Issue description: Yahoo Site Explorer API does not report that the site is indexed.
Issue ID: 924
Issue detailed description:
1.3.3 A web page is referenced by dynamic hyperlink only
Issue description: A web pages is linked only by JavaScript or Flash link. It may cause problems with a website indexing by search engines.
Issue ID: 902
Issue detailed description:
1.3.4 A web page is blocked by robots.txt file
Issue description: A robots.txt file has setting, which prevents a web page indexing by search engines.
Issue ID: 903
Issue detailed description:
1.3.5 A web page is blocked by robots meta tag
Issue description: Page's robots meta contains 'noindex', which prevents a web page indexing by search engines.
Issue ID: 922
Issue detailed description:
1.3.6 A web page is linked through rel=nofollow attribute
Issue description: Rel=nofollow attribute is used to link not trusted websites. Search engines do not count such hyperlinks.
Issue ID: 904
Issue detailed description:
1.3.7 A web page is linked from page with robots meta 'nofollow'
Issue description: Page with meta name='robots' value='nofollow' is referrencing the current page.
Issue ID: 921
Issue detailed description:
1.3.8 Multi-step redirect link to internal web page
Issue description: The original link on web site points to the target link through several redirects. It may prevent the target web page from indexing. The original hyperlink may not be bound to the target link by search engines. It reduces the number of incoming links to the target web page.
Issue ID: 905
Issue detailed description:
1.3.9 Client side redirect link to external website
Issue description: This redirect method may be considered as a spam technique by search engines.
Issue ID: 906
Issue detailed description:
1.3.10 Client side redirect to external website
Issue description: This redirect method may be considered as a spam technique by search engines.
Issue ID: 923
Issue detailed description:
1.3.11 A web page is loaded by client side redirect
Issue description: The original hyperlink may not be bound to the target link by search engines. It reduces the number of incoming links to the target web page.
Issue ID: 907
Issue detailed description:
1.3.12 Deep page
Issue description: Page's depth is more than the specified number. (Page depth is the number of clicks to the page from one of starting pages.)
Issue ID: 413
Issue detailed description: Page depth is the number of clicks to the page from one of starting pages. If this number is more than the specified threshold, an error is detected.
Issue settings
Parameter name: Page depth threshold
Setting type: threshold
Setting description: Page depth threshold. The depth below or equal this threshold considered as good.
Setting sample: 3
1.3.13 Long URL
Issue description: A web page URL should not exceed 250 symbols.
Issue ID: 916
Issue detailed description:
1.3.14 A web page with many parameters in its URL
Issue description: Search engines are reluctant to index a web page with many parameters.
Issue ID: 915
Issue detailed description:
1.3.15 Long HTML title
Issue description: HTML title should be 80 symbols or less.
Issue ID: 910
Issue detailed description:
1.3.16 Non relevant words in HTML title
Issue description: All words from HTML title should have entries in page's content (page's text and alts).
Issue ID: 917
Issue detailed description:
1.3.17 Duplicated HTML titles
Issue description: A web page has the same HTML title with another web page.
Issue ID: 402
Issue detailed description:
1.3.18 Non relevant words in HTML keywords
Issue description: All words from HTML keywords meta should have entries in page's content (page's text and alts)
Issue ID: 918
Issue detailed description:
1.3.19 Long HTML description
Issue description: HTML description should be 150 symbols or less.
Issue ID: 911
Issue detailed description:
1.3.20 Duplicated HTML descriptions
Issue description: A web page has the same HTML description with another web page.
Issue ID: 407
Issue detailed description: Web section contains two or more pages with the same Description meta tag.
1.3.21 Page has too many links
Issue description: Google webmasters guidelines do not recommend to place more than 100 hyperlinks on a single web page.
Issue ID: 919
Issue detailed description:
1.3.22 Dynamic links are found
Issue description: Manual check. Robots do not crawl on dynamic links such as script links or flash ones. The referred pages may remain unindexed.
Issue ID: 920
Issue detailed description:
1.3.23 Link to improper web content
Issue description: A hyperlink on a web page leads to spyware, porn, or spam content, or to a de-indexed web page.
Issue ID: 908
Issue detailed description:
1.3.24 Web pages with the same content
Issue description: Pages have similar content
Issue ID: 912
Issue detailed description:
1.3.25 Different URLs to the same web page
Issue description: Different URLs refer to the pages with identical content.
Issue ID: 913
Issue detailed description:
1.4 Issue category: Web site quality
1.4.1 HTML title: missing
Issue description: HTML 'Title' tag is empty or missing.
Issue ID: 401
Issue detailed description: Title tag (<title> tag containing in <head> element) is empty or missing.
1.4.2 HTML keywords: missing
Issue description: Keywords missing. Page with missing 'Keywords' meta tag
Issue ID: 404
Issue detailed description: Keywords meta tag is <meta name="keywords" content="">. Truwex detect an error if this meta is missing or its 'content' attribute is empty.
1.4.3 HTML keywords: default value
Issue description: 'Keywords' meta tag has one of the user-defined values.
Issue ID: 403
Issue detailed description: Keywords meta tag is <meta name="keywords" content="">. Truwex detect an error if 'content' attribute of this tag equals to parameter specified.
Issue settings
Parameter name: Default value for keywords meta tag
Setting type: pattern
Setting description: String with default value for 'content' attribute of keywords meta tag.
Setting sample: Keywords
1.4.4 HTML keywords: repetitive
Issue description: More than two pages with the same 'Keywords' meta tag
Issue ID: 405
Issue detailed description: Web section contains more than two pages with the same Keywords meta tag.
1.4.5 HTML description: missing
Issue description: Description missing. Page with missing 'Description' meta tag
Issue ID: 406
Issue detailed description: Description meta tag is <meta name="description" content="">. Truwex detect an error if this meta is missing or its 'content' attribute is empty.
1.4.6 HTML description: default value
Issue description: 'Description' meta tag has one of the user-defined default values
Issue ID: 408
Issue detailed description: Description meta tag is <meta name="description" content="">. Truwex detect an error if 'content' attribute of this tag equals to a parameter specified.
Issue settings
Parameter name: Default value for description meta tag
Setting type: pattern
Setting description: String with default value for 'content' attribute of description meta tag.
Setting sample: Description
1.4.7 HTML character set: missing
Issue description: Character set metatag is not found
Issue ID: 409
Issue detailed description: Page has no character set meta tag. Example of valid charset meta tag: <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
1.4.8 Broken links are found
Issue description: Broken links are found on a page
Issue ID: 410
Issue detailed description: Page contains links that are broken: they may have not-valid URL, or server returns 404 Page not found error, or no any response from server has been received.
1.4.9 Broken source URLs are found
Issue description: Images or some other elements with broken source URL are found on a page
Issue ID: 411
Issue detailed description: Page requires resources that are broken. E.g. CSS, JavaScript, or image file can not be downloaded. The issue is similar to the previous Broken links are found issue, but objects differ.
1.4.10 Broken anchors found
Issue description: Broken anchors are found on a page
Issue ID: 412
Issue detailed description: Page contains non-balanced intra-page links: for example it has <a href="#legend"> source anchor but has no corresponding <a name="legend"> destination anchor, or vice versa. Also this issue appears if a name in the destination anchor has # sign before it, i.e. source anchor is <a href="#odd">, where fragment identifier is "odd" and the destination anchor is <a name="#odd">, where anchor name is "#odd". IE understands such links but they are incorrect according to HTML standard and so may cause problems in other browsers: for example Netscape 7.1 and FireFox 2.0 do not treat them well.
1.4.11 Page not found
Issue description: A web page belongs to a web site, but broken
Issue ID: 418
Issue detailed description: Broken link, which is a part of scanned website.
1.4.12 Page not accessible
Issue description: Page not accessible: access is forbidden or authorization is required
Issue ID: 419
Issue detailed description: A page URL was found in a starting URLs of a web section or in a link on some web section's page and this URL belongs to the website. But the page can not be loaded because of "access is forbidden" or "authorization is required" error.
1.4.13 Old pages found
Issue description: Page is old: its modification date is older than specified number of days
Issue ID: 414
Issue detailed description: Page modification date is obtained as minimal date between Last Modified Date and File Modified Date returned by the server. Truwex compares this date with today date using the specified threshold.
Issue settings
Parameter name: Old pages threshold (number of days)
Setting type: threshold
Setting description: Pages older than specified number of days considered as not good.
Setting sample: 200
1.4.14 Script error popup is detected
Issue description: Script error popup dialog window is detected
Issue ID: 420
Issue detailed description: Pop-up window is detected while opening a web page in Internet Explorer. This is a script error dialog window.
1.5 Issue category: Interactive behavior
1.5.1 New browser window is detected
Issue description: Page opens a new Internet Explorer browser window
Issue ID: 416
Issue detailed description: The page opens a new Internet Explorer window without a user intervention. Read the related W3C WCAG section: [W3C 10.1 (2)].
1.5.2 Popup dialog window is detected
Issue description: Popup dialog window is detected
Issue ID: 417
Issue detailed description: Pop-up window is detected while opening a web page in Internet Explorer. E.g. java script error, java script dialog, active-x or certificate prompts. Look to the page properties and find details about this window in Issues tab. Read the related W3C WCAG section: [W3C 10.1 (2)].
1.6 Issue category: Google Analytics
1.6.1 Google Analytics JavaScript file is in Head section
Issue description: Error: Google Analytics JavaScript file is in <head></head> section. The early Google Analytics guidelines recommended this placement, however now they prescribe to place the code immediately before the </body> tag.
Issue ID: 531
Issue detailed description: A script with source equal to urchin.js or __utm.js is found in page's Head.
1.6.2 Google Analytics Account variable value is incorrect
Issue description: Error: Google Analytics Account variable _uacct is set to the default value 'UA-xxxxxx-x' or its value differs from the one user has specified.
Issue ID: 535
Issue detailed description: A variable _uacct has default value of 'UA-xxxxxx-x'.
1.6.3 Google Analytics Account variable value can not be detected because page script contains error
Issue description: Error: Google Analytics Account variable _uacct is not found because an error occured in page's script
Issue ID: 533
Issue detailed description: Page's script contains errors, therefore IE blocks access to all script block, and so this variable can not be detected.
1.6.4 Google Analytics Event Tracking detected, but does not work
Issue description: Error: Google Analytics event tracking detected, but it will not work because Google Analytics script is not downloaded. The event tracking are event handlers containing the following function names: urchinTracker, __utmSetTrans, __utmLinker, __utmLinkPost, __utmSetVar, __utmVisitorCode.
Issue ID: 540
Issue detailed description: Event handlers with GA function name is found (urchinTracker, __utmSetTrans, __utmLinker, __utmLinkPost, __utmSetVar, __utmVisitorCode), but GA script (urchin.js, or __utm.js) is not downloaded.
1.6.5 Google Analytics JavaScript file is not downloaded
Issue description: Error: Google Analytics JavaScript file 'urchin.js' or '__utm.js' is not downloaded for this page
Issue ID: 529
Issue detailed description: File with name urchin.js or __utm.js was not downloaded for the page.
1.6.6 Google Analytics Account variable is not found
Issue description: Error: Google Analytics Account variable _uacct is not found
Issue ID: 532
Issue detailed description: Variable _uacct is not found, while no any script error was detected.
1.6.7 Google Analytics WebBeacon is not detected
Issue description: Error: Google Analytics web beacon is not detected. The web beacon is __utm.gif file downloaded from one of the following URLs: http://www.google-analytics.com, https://ssl.google-analytics.com, http://service.urchin.com, https://service.urchin.com.
Issue ID: 537
Issue detailed description: File with source URL starting with http://www.google-analytics.com/__utm.gif?, https://ssl.google-analytics.com/__utm.gif, http://service.urchin.com/__utm.gif, or https://service.urchin.com/__utm.gif is loaded for the page.
1.6.8 Google Analytics Cookie is not detected
Issue description: Error: Google Analytics cookie __utmX is not detected
Issue ID: 539
Issue detailed description: Cookie with name matching '__utm[a-Z]' pattern is not detected.