Lade Daten...

Bitte warten

Forum

Moderiert von: stefan, spinne
Forum:	Module
Sie schreiben eine Antwort zum Thema:	Kontaktformular einbinden
Gehe zu:	OpenPHPNuke - das Open Source CMS Forum Index

Benutzername:
eMail
Nachricht:	[quote author=stefan date=2008-07-30 14:08:42] <span class="quoteheader">Petra schrieb am 30.07.2008 um 12:49:33 Uhr folgendes:</span>[quote] > > Zu den vielen Fehlern.....gibt es dafür ein Program, das dieses korrigieren kann? > [/quote] Oh liebe Petra, die Frage ist richtig gut. Wenn du eins findest das automatisch Fehler korrigiert dann wären wohl viele Webmaster und HTML Autoren arbeitslos. Nein leider wird das wenn überhaupt nur bedingt möglich sein. Eilweise passiert das sogar schon in opn. So wird (gibt ausnahmen) -> und paar andere typische werden ebenfalls vor der Ausgabe korrigiert aber komplett zu korrigeren automatisch ist unmöglich. Man kann nicht wissen wie es denn gemeint ist, da ist der Mensch (zum glück) eindeutig im vorteil. Was es allerdings zuhauf gibt sind Prüfprogramme die eben Fehler Zeigen. Hier muss man aber auch klar sagen das man sich überlegen sollte bis zu welchem grad man korrigiert. Es gibt mehere Arten von Fehlern. a) HTML Fehler (Hier kann man noch Unterteilungen vornehmen b) Styles (css Fehler) c) Accessiblity Fehler (Unterteilung in P1 / P2 / P3 / All möglich) d) Links e) Structure und noch weiter die nicht so wichtig sind. alles bezogen auf deine Startseite d) da gibts ne link auf den du verweist [url=http://www.webkatalog-nie-mehr-suchen.de]http://www.webkatalog-nie-mehr-suchen.de[/url] den gibts nicht der ist tot -> schlecht ... e) Da hast du keine Fehler ausser im br aber das sagte ich ja schon. du benutzt 125 mal br aber nur 44 sind davon sauber auch wieder geschlossen b) <span style="font-size: 11px;"> nicht gut weil: It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names. c) Beispie p3 Fehler Adjacent links should include non-link, printable characters (surrounded by spaces) between them [P3, 10.5]. Do not place two links next to each other without non-linked, printable characters between them because the two links may be rendered as a single link in some user agents. [url=http://www.tiere-liga.de/klick.php?ID=6]Mitglied bei[/url][url=http://www.tiere-liga.de] Tiere-Liga[/url] Bitte jetzt mal das off topic zu entschuldigen hier mal deien fehler (nur die startseite) Validator message export for "http://www.abenteuer-miniriff.com/": 1. Warning in line 10 at character 32: (Grouped->Search Engine) Found 1 missing keyword/phrase. Make sure that there is a keyword or phrase between commas and at the beginning and end of the list. The keywords list should not begin or end with a comma, nor should it have two commas in a row with no keyword or phrase in between them. 2. Warning in line 10 at character 32: (Grouped->Search Engine) The keywords end in a comma. This is a common error. The last comma should be removed or a keyword should be added after the comma. 3. Warning in line 33 at character 18: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment. 4. Warning in line 34 at character 1: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment. 5. Warning in line 34 at character 152: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment. 6. Warning in line 35 at character 1: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment. 7. Warning in line 194 at character 33: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, AI Internet Solutions recommends putting the script (especially longer scripts) in an external file and using the "src" attribute to specify the external file. The next best option for XHTML documents would be to not put the script content in a comment and to disregard pre HTML 3.2 browsers. 8. Warning in line 200 at character 3: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers. 9. Warning in line 209 at character 33: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, AI Internet Solutions recommends putting the script (especially longer scripts) in an external file and using the "src" attribute to specify the external file. The next best option for XHTML documents would be to not put the script content in a comment and to disregard pre HTML 3.2 browsers. 10. Warning in line 236 at character 33: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, AI Internet Solutions recommends putting the script (especially longer scripts) in an external file and using the "src" attribute to specify the external file. The next best option for XHTML documents would be to not put the script content in a comment and to disregard pre HTML 3.2 browsers. 11. Warning in line 252 at character 48: It appears that two (or more) consecutive forward slash characters ("//") were used in this URL where only one should have been used. This may cause problems in some browsers. Please check the link. 12. Warning in line 253 at character 102: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) 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 [P2, 10.1]. Avoid using target="_blank" because spawning a new window can be confusing and disorienting to the user. If a new window must be spawned, then it is recommended that it be indicated in the link description, such as by using the text "new window" somewhere in the "title" attribute value (recommended) or by adding "(new window)" to the link description. This message is displayed up to 3 times. 13. Warning in line 268 at character 194: (Accessibility->General Accessibility) This alt text may be too short to be meaningful. Consider a longer and better description of the object. This alt text is only 6 characters long and should probably be lengthened. 14. Warning in line 276 at character 195: (Accessibility->General Accessibility) This alt text may be too short to be meaningful. Consider a longer and better description of the object. This alt text is only 7 characters long and should probably be lengthened. 15. Warning in line 278 at character 195: (Accessibility->General Accessibility) This alt text may be too short to be meaningful. Consider a longer and better description of the object. This alt text is only 7 characters long and should probably be lengthened. 16. Warning in line 289 at character 2: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) Style sheets should be used to control layout and presentation [P2, 3.3]. The element you've used ("small") is a presentational element. Presentational elements include "font", "b", "i", "big", "small", and others. For presentation, consider using style sheets (CSS) instead. Use HTML elements only for content and structure and not for layout and presentation. Use the "em" and "strong" elements for structural emphasis. This message is displayed only once. 17. Warning in line 290 at character 136: The "small" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text. 18. Warning in line 290 at character 1090: The "small" element contains no text and may be useless. Consider removing this element or placing text in it so that it contains text. 19. Warning in line 324 at character 139: (Accessibility->General Accessibility) Alt text should be succinct (clear and precise in a few words). AI Internet Solutions recommends that alt text be 75 characters or less, including spaces and punctuation. This alt text is 77 characters and should probably be shortened. If a long description is needed, then consider using the "longdesc" attribute to specify a link to a long description of the object. 20. Error in line 332 at character 71: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 21. Error in line 333 at character 2: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 22. Warning in line 333 at character 90: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) 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 [P2, 10.1]. Avoid using target="_blank" because spawning a new window can be confusing and disorienting to the user. If a new window must be spawned, then it is recommended that it be indicated in the link description, such as by using the text "new window" somewhere in the "title" attribute value (recommended) or by adding "(new window)" to the link description. This message is displayed up to 3 times. 23. Error in line 333 at character 99: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 24. Warning in line 334 at character 83: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) 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 [P2, 10.1]. Avoid using target="_blank" because spawning a new window can be confusing and disorienting to the user. If a new window must be spawned, then it is recommended that it be indicated in the link description, such as by using the text "new window" somewhere in the "title" attribute value (recommended) or by adding "(new window)" to the link description. This message is displayed up to 3 times. 25. Warning in line 336 at character 86: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 3)) Adjacent links should include non-link, printable characters (surrounded by spaces) between them [P3, 10.5]. Do not place two links next to each other without non-linked, printable characters between them because the two links may be rendered as a single link in some user agents. 26. Error in line 337 at character 2: The "p" tag must have an end tag (</p>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 27. Warning in line 338 at character 10: [64] An invalid character reference was found in the "href" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 28. Error in line 338 at character 92: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 29. Error in line 339 at character 2: The "p" tag must have an end tag (</p>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 30. Warning in line 339 at character 13: [64] An invalid character reference was found in the "href" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 31. Error in line 339 at character 87: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 32. Error in line 339 at character 203: A quoted string (like an attribute value) cannot be immediately followed by text. It must be followed by a space or by the end of the tag. Is there a missing space character? 33. Error in line 340 at character 2: The "p" tag must have an end tag (</p>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 34. Warning in line 341 at character 10: [64] An invalid character reference was found in the "href" attribute value. The most likely cause is an unencoded ampersand. This is a common error that should be fixed (even though it still works most of the time). Ampersands should be encoded as "&" even when specifying script variables. Web browsers will convert the "&" entities back to just '&'. Example: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value". Note that the ampersand in the URL was encoded as "&". Other causes of invalid references are misspelled entity names and missing semicolons. 35. Error in line 341 at character 91: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 36. Warning in line 341 at character 157: (Accessibility->General Accessibility) This alt text may be too short to be meaningful. Consider a longer and better description of the object. This alt text is only 7 characters long and should probably be lengthened. 37. Error in line 341 at character 182: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 38. Error in line 342 at character 2: The "p" tag must have an end tag (</p>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 39. Error in line 343 at character 84: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 40. Error in line 344 at character 2: The "p" tag must have an end tag (</p>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 41. Error in line 345 at character 71: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 42. Error in line 345 at character 71: (Accessibility->Section 508 Accessibility Standards) The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [Section 1194.22 (a)] 43. Error in line 345 at character 71: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 1)) The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [P1, 1.1] 44. Warning in line 345 at character 71: [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images). 45. Error in line 345 at character 130: In XHTML, enumerated attribute values are case sensitive and must be lowercase. Instead of "BOTTOM", use "bottom". This is in contrast to HTML, where values are normally case-insensitive. 46. Error in line 346 at character 2: The "p" tag must have an end tag (</p>) but the end tag was not found. In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 47. Error in line 347 at character 149: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 48. Error in line 348 at character 2: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 49. Error in line 349 at character 2: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 50. Error in line 350 at character 192: The end tag for "p" (opened in line 346) should appear before the end tag for "div" (nesting error). 51. Warning in line 362 at character 40: At least one character (codepoint) between 128 and 159 (inclusive) was found on line 362. These codepoints are commonly found in Windows character sets like Windows-1252 but may not work for everyone, especially those not using Windows. Consider using "“" instead of this character. 52. Warning in line 368 at character 44: At least one character (codepoint) between 128 and 159 (inclusive) was found on line 368. These codepoints are commonly found in Windows character sets like Windows-1252 but may not work for everyone, especially those not using Windows. Consider using "“" instead of this character. 53. Error in line 396 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 54. Warning in line 401 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 55. Error in line 405 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 56. Warning in line 409 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 57. Error in line 420 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 58. Warning in line 424 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 59. Error in line 428 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 60. Warning in line 432 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 61. Error in line 436 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 62. Warning in line 442 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 63. Warning in line 457 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 64. Error in line 461 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 65. Warning in line 465 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 66. Error in line 469 at character 106: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 67. Warning in line 473 at character 105: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "mehr..." has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4]http://www.abenteuer-miniriff.com/system/article/index.php?opnparams=AHcDbgZkATYANlE4[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 68. Error in line 518 at character 2: [47] The "ul" element must directly contain at least one "li" element. 69. Error in line 525 at character 73: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 1)) The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [P1, 1.1] 70. Error in line 525 at character 73: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 71. Error in line 525 at character 73: (Accessibility->Section 508 Accessibility Standards) The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the "longdesc" attribute to specify the URI to an extended description of the image. [Section 1194.22 (a)] 72. Warning in line 525 at character 73: [13] HTML 4.01 and XHTML require that the "alt" attribute be used with the "img" element. The "alt" attribute is critical for accessibility. It lets authors specify equivalent text to serve as content when the image cannot be seen or displayed. Use alt="" when alternate text is not appropriate, such as when images are intended to format a page (such as spacer images). 73. Error in line 526 at character 92: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 74. Warning in line 547 at character 179: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Hausi" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=UzhTJ11mWSZWJQc4ACNXbABsAGtQa1V3UiZTZQZkCm4CYwA5Ux0MZ1UgVH0EPA]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=UzhTJ11mWSZWJQc4ACNXbABsAGtQa1V3UiZTZQZkCm4CYwA5Ux0MZ1UgVH0EPA[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 75. Warning in line 560 at character 552: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "1" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 76. Warning in line 560 at character 717: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "2" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=AHBWPVwqCGsAYwBnAGBQNFVhASoDMVU%2BAXJWe1M9Cz8BMQUnXTReMlE3V34EMFZwWGdWalcz]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=AHBWPVwqCGsAYwBnAGBQNFVhASoDMVU%2BAXJWe1M9Cz8BMQUnXTReMlE3V34EMFZwWGdWalcz[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 77. Warning in line 560 at character 882: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "3" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=BnZROlIkWTpdPgViAGBSNlBkASpXZQdsCXpVeFQ6ATUCMgooBm9cMF07BSxTZ1F3BDtTbFYy]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=BnZROlIkWTpdPgViAGBSNlBkASpXZQdsCXpVeFQ6ATUCMgooBm9cMF07BSxTZ1F3BDtTbFYy[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 78. Warning in line 568 at character 588: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "1" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 79. Warning in line 576 at character 593: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "1" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 80. Warning in line 576 at character 760: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "2" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=AHBWPVwqCGsAYwBnAGBQNFVhASoDMVU%2BAXJWe1M9Cz8BMQUnXTReMlE3V34EMFZwWGdWalcz]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=AHBWPVwqCGsAYwBnAGBQNFVhASoDMVU%2BAXJWe1M9Cz8BMQUnXTReMlE3V34EMFZwWGdWalcz[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 81. Warning in line 576 at character 925: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "3" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=BnZROlIkWTpdPgViAGBSNlBkASpXZQdsCXpVeFQ6ATUCMgooBm9cMF07BSxTZ1F3BDtTbFYy]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=BnZROlIkWTpdPgViAGBSNlBkASpXZQdsCXpVeFQ6ATUCMgooBm9cMF07BSxTZ1F3BDtTbFYy[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 82. Warning in line 576 at character 1090: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "4" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=VCQBalYgXD8FZgJlAWEHYQc9ASoFNwZtBHcHKlU7ATUGOgspVz5dMQFnUntWYlh%2BBToEOlYy]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=VCQBalYgXD8FZgJlAWEHYQc9ASoFNwZtBHcHKlU7ATUGOgspVz5dMQFnUntWYlh%2BBToEOlYy[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 83. Warning in line 584 at character 580: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "1" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=B3dROlwqWTpTMFs8UzNVMQI2V3xXZVc8UiEDLlY4DDhSYgEjUDleMlcxASgDN1VzVGtRbA[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 84. Warning in line 584 at character 752: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "3" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=BnZROlIkWTpdPgViAGBSNlBkASpXZQdsCXpVeFQ6ATUCMgooBm9cMF07BSxTZ1F3BDtTbFYy]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=BnZROlIkWTpdPgViAGBSNlBkASpXZQdsCXpVeFQ6ATUCMgooBm9cMF07BSxTZ1F3BDtTbFYy[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 85. Warning in line 584 at character 915: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "4" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=VCQBalYgXD8FZgJlAWEHYQc9ASoFNwZtBHcHKlU7ATUGOgspVz5dMQFnUntWYlh%2BBToEOlYy]http://www.abenteuer-miniriff.com/system/forum/viewtopic.php?opnparams=VCQBalYgXD8FZgJlAWEHYQc9ASoFNwZtBHcHKlU7ATUGOgspVz5dMQFnUntWYlh%2BBToEOlYy[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 86. Warning in line 587 at character 181: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Harald" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5UIFBrCXYBclplAiECOQJuB2wAOwEjBXFUYgBiDGgAYVZvUR9dNlwuADsAPVZg]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5UIFBrCXYBclplAiECOQJuB2wAOwEjBXFUYgBiDGgAYVZvUR9dNlwuADsAPVZg[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 87. Warning in line 595 at character 181: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Harald" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5UIFBrCXYBclplAiECOQJuB2wAOwEjBXFUYgBiDGgAYVZvUR9dNlwuADsAPVZg]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5UIFBrCXYBclplAiECOQJuB2wAOwEjBXFUYgBiDGgAYVZvUR9dNlwuADsAPVZg[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 88. Error in line 605 at character 2: [47] The "ul" element must directly contain at least one "li" element. 89. Error in line 612 at character 2: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 90. Error in line 613 at character 54: The "img" tag must be closed by either adding a slash to the end of the tag if proper (<img ... />) (empty element shorthand) or using a separate end tag (</img>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 91. Warning in line 645 at character 187: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Petra" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 92. Warning in line 646 at character 182: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "amcc" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 93. Warning in line 647 at character 182: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "amcc" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 94. Warning in line 648 at character 186: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "amcc" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 95. Warning in line 649 at character 185: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Petra" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 96. Warning in line 650 at character 182: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "amcc" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=CWIFcV1mC3RSIVFuVHcEP1Y6VzwCOQ8tB3NTZQFjDmpVNAA5BmFdOgJhATg[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 97. Warning in line 651 at character 185: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Petra" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 98. Warning in line 652 at character 185: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Petra" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw]http://www.abenteuer-miniriff.com/system/user/index.php?opnparams=VT5XI1VuCHdUJ1NsDi0AOwRoAGsGPQAiCHxUYgBiWz8AYVduB1ELZFYiUHhTYw[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 99. Error in line 664 at character 2: (Accessibility->Section 508 Accessibility Standards) The "input" tag has an "id" attribute but it must be used to explicitly associate this control with a "label" element using the "label" element's "for" attribute (for="text-id-1893270606"). When electronic forms are designed to be completed online, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues [Section 1194.22 (n)]. Information attached to controls via the "label" element can be very useful to users of talking browsers. Note that "id" and "for" values are case sensitive. Visit [url=http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels]http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels[/url] for more information. 100. Warning in line 664 at character 2: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The "input" tag has an "id" attribute but it should be used to explicitly associate this control with a "label" element using the "label" element's "for" attribute (for="text-id-1893270606"). Labels should be explicitly associated with their controls [P2, 12.4]. Information attached to controls via the "label" element can be very useful to users of talking browsers. Note that "id" and "for" values are case sensitive. Visit [url=http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels]http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels[/url] for more information. 101. Error in line 668 at character 195: (Accessibility->Section 508 Accessibility Standards) The "input" tag has an "id" attribute but it must be used to explicitly associate this control with a "label" element using the "label" element's "for" attribute (for="text-id-228877856"). When electronic forms are designed to be completed online, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues [Section 1194.22 (n)]. Information attached to controls via the "label" element can be very useful to users of talking browsers. Note that "id" and "for" values are case sensitive. Visit [url=http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels]http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels[/url] for more information. 102. Warning in line 668 at character 195: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The "input" tag has an "id" attribute but it should be used to explicitly associate this control with a "label" element using the "label" element's "for" attribute (for="text-id-228877856"). Labels should be explicitly associated with their controls [P2, 12.4]. Information attached to controls via the "label" element can be very useful to users of talking browsers. Note that "id" and "for" values are case sensitive. Visit [url=http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels]http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels[/url] for more information. 103. Warning in line 671 at character 46: The value of the "name" attribute ("reset") may conflict with properties of the JavaScript Form object when using JavaScript. It is recommended that the value of the "name" attribute be changed to avoid potential conflict when accessing the form object's properties, methods, and event handlers. Values that should not be used include "action", "elements", "encoding", "length", "method", "name", "target", "reset", "submit", and some others. 104. Warning in line 679 at character 33: [28] The "div" tag is contained in a "span" tag (which was opened in line 679). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Firefox, Mozilla, and Opera. Possible solutions: 1. Close the "span" tag before using the "div" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "div" tag; 2. Eliminate the "div" tag; or 3. Reorder the "div" and "span" tags. 105. Error in line 679 at character 104: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 106. Error in line 679 at character 280: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 107. Warning in line 699 at character 98: (Styles->General) It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names. 108. Error in line 699 at character 205: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 109. Error in line 699 at character 209: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 110. Warning in line 741 at character 134: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Hauptseite" has already been used to link to a different resource ([url=http://www.abenteuer-miniriff.com/modules/mylinks/index.php]http://www.abenteuer-miniriff.com/modules/mylinks/index.php[/url]). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1] 111. Error in line 747 at character 62: "scrollAmount" contains uppercase characters. All start tags, end tags, and tag attributes must be in lowercase because this is an XHTML document. 112. Error in line 747 at character 79: "scrollDelay" contains uppercase characters. All start tags, end tags, and tag attributes must be in lowercase because this is an XHTML document. 113. Error in line 749 at character 2: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 114. Error in line 749 at character 6: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 115. Error in line 749 at character 71: The attribute value "0" for the "border" attribute was not enclosed in single or double quotation marks when it must be. In HTML 4.01, attribute values containing characters other than A-Z, a-z, 0-9, hyphens, periods, underscores, and colons must be quoted. In XHTML/XML, all attribute values must be quoted. Quotes are recommended even if they are not required. 116. Warning in line 749 at character 202: For better backward compatibility with HTML, use a space character before the '/' character. 117. Error in line 750 at character 2: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 118. Error in line 750 at character 6: The "br" tag must be closed by either adding a slash to the end of the tag if proper (<br ... />) (empty element shorthand) or using a separate end tag (</br>). In XHTML, all elements not declared as empty (like "b", "p", "span", etc.) must have an end tag. Elements declared as empty (like "br", "img", "input", etc.) can have an end tag or can use the empty element shorthand. 119. Error in line 750 at character 117: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 1)) The "img" element requires the "alt" attribute to specify a text equivalent. The text equivalent should be a short phrase that succinctly identifies the image and makes its function clear (like "next page" instead of "green arrow"). However, use alt="" when appropriate, such as when images are intended to format a page (such as spacer images). If appropriate, consider also using the [/quote]

Sicherheits-Code
Sicherheitscode hier eingeben

Thema im Überblick

Autor
stefan Wohnort: Münster	Kontaktformular einbinden Geschrieben: 31.07.2008 11:19 naja ich kann.

spinne Registriert: 21.08.2003 Wohnort: Luzern	Kontaktformular einbinden Geschrieben: 31.07.2008 10:53 stefan.... jetzt hast du es kaputt gemacht hier im thread... durch dein posting... ich kann hier zumindest nicht mal mehr was editieren keine admin mehr auswählen... die html tags haben deinen beitrag zerschossen. (zumindest geht hier bei mir auf der arbeit IE6 nichts zu ändern usw.) 6. Warning in line 35 at character 1: Found the character '<' in a ' Gehe zu: Wähle ein Forum Thema abonnieren [eingefügt von stefan] alos hier gehts [eingefügt/] [ Diese Nachricht wurde bearbeitet von: stefan am 31.07.2008 11:21 (Originaldatum 31.07.2008 10:53) ]

stefan Wohnort: Münster	Kontaktformular einbinden Geschrieben: 30.07.2008 14:14 hmm erstanlich der text war zu lang für einen Beitrag da hat er dann was durcheinander gewürfelt. Waren eigentlich 285 Punkte. Muss ich prüfen, denke aber auch das das hier off topic wird. Denke aber du hast schon mal hinweise um gezielter zu suchen oder nachzufragen

stefan Wohnort: Münster	Kontaktformular einbinden Geschrieben: 30.07.2008 14:08 Petra schrieb am 30.07.2008 um 12:49:33 Uhr folgendes: Zu den vielen Fehlern.....gibt es dafür ein Program, das dieses korrigieren kann? Oh liebe Petra, die Frage ist richtig gut. Wenn du eins findest das automatisch Fehler korrigiert dann wären wohl viele Webmaster und HTML Autoren arbeitslos. Nein leider wird das wenn überhaupt nur bedingt möglich sein. Eilweise passiert das sogar schon in opn. So wird (gibt ausnahmen) -> und paar andere typische werden ebenfalls vor der Ausgabe korrigiert aber komplett zu korrigeren automatisch ist unmöglich. Man kann nicht wissen wie es denn gemeint ist, da ist der Mensch (zum glück) eindeutig im vorteil. Was es allerdings zuhauf gibt sind Prüfprogramme die eben Fehler Zeigen. Hier muss man aber auch klar sagen das man sich überlegen sollte bis zu welchem grad man korrigiert. Es gibt mehere Arten von Fehlern. a) HTML Fehler (Hier kann man noch Unterteilungen vornehmen b) Styles (css Fehler) c) Accessiblity Fehler (Unterteilung in P1 / P2 / P3 / All möglich) d) Links e) Structure und noch weiter die nicht so wichtig sind. alles bezogen auf deine Startseite d) da gibts ne link auf den du verweist http://www.webkatalog-nie-mehr-suchen.de den gibts nicht der ist tot -> schlecht ... e) Da hast du keine Fehler ausser im br aber das sagte ich ja schon. du benutzt 125 mal br aber nur 44 sind davon sauber auch wieder geschlossen b) nicht gut weil: It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names. c) Beispie p3 Fehler Adjacent links should include non-link, printable characters (surrounded by spaces) between them [P3, 10.5]. Do not place two links next to each other without non-linked, printable characters between them because the two links may be rendered as a single link in some user agents. Mitglied bei Tiere-Liga Bitte jetzt mal das off topic zu entschuldigen hier mal deien fehler (nur die startseite) Validator message export for "http://www.abenteuer-miniriff.com/": 1. Warning in line 10 at character 32: (Grouped->Search Engine) Found 1 missing keyword/phrase. Make sure that there is a keyword or phrase between commas and at the beginning and end of the list. The keywords list should not begin or end with a comma, nor should it have two commas in a row with no keyword or phrase in between them. 2. Warning in line 10 at character 32: (Grouped->Search Engine) The keywords end in a comma. This is a common error. The last comma should be removed or a keyword should be added after the comma. 3. Warning in line 33 at character 18: Found the character '>' in a '', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment. 4. Warning in line 34 at character 1: Found the character '<' in a '', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment. 6. Warning in line 35 at character 1: Found the character '<' in a '