Source View: http://community.elgg.org/

No meta description tag found. Use a description tag that accurately describes the contents of a web page.

Line 1 Yahoo Google Bing

A well-written description tag attracts more clicks in search results than an irrelevant or missing description.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<head>

<title>The Elgg Community</title>

<!--[if gt IE 7]>

<![endif]-->

<!--[if IE 7]>

<![endif]-->

<!--[if IE 6]>

<![endif]-->

/**

* Don't want to cache these -- they could change for every request

elgg.config.lastcache = 1379048194;

elgg.config.viewtype = 'default';

elgg.config.simplecache_enabled = 1;

elgg.security.token.__elgg_ts = 1379696958;

elgg.security.token.__elgg_token = '3dec68db2873a5c84677937fbd7d3aa5';

//Before the DOM is ready, but elgg's js framework is fully initalized

elgg.trigger_hook('boot', 'system');</script>

var _gaq = _gaq || [];

_gaq.push(['_setAccount', 'UA-20121988-4']);

_gaq.push(['_trackPageview']);

(function() {

var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;

ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';

var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);

})();

</script>

</head>

<body>

Headings should not be empty.

Line 69 WCAG2 AA G130

Add text to the heading, or ALT text if the heading contains an image. Screen readers read out page headings, allowing users to quickly skip to a section, but some older screen readers do not ignore empty headings.

This page has more than one H1 tag, which violates Bing webmaster guidelines.

Line 69 Bing

Leave the title of the main content as H1 and change other H1 tags to a lower heading level.

<h1>

Each A tag must contain text or an IMG with an ALT tag.

Line 70 WCAG2 A F89

Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT tag is blank, screen readers have nothing to read, so read out the URL instead.

IMG tags must have an ALT attribute.

Line 71 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Use text links rather than image links. In general, text links are more easily recognized as clickable.

Line 71 Usability.gov 10:6

Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

<img src="http://community.elgg.org/mod/community_theme/graphics/logo.png" width="144" height="76"

Required attribute "alt" not specified.

Line 71 HTML Validation

</a>

</h1>

All FIELDSET tags should be labeled with LEGEND tags.

Line 75 WCAG2 A H71

The first element inside the FIELDSET must be a LEGEND element, which provides a label or description for the group.

JavaScript changes: changed to value='56371ed0375e704a366d0dc0955ab954'

JavaScript changes: changed to value='1379696959'

<div>

LABEL elements should be associated with other controls using FOR attributes.

Line 77 WCAG2 A 4.1.2

Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.

<label>Username or email</label>

This form control has no associated LABEL element.

Line 78 WCAG2 A F68 Section 508 1194.22 (n)

Add a LABEL tag with the FOR attribute set to the ID of this control. This allows screen readers to tell the user what each control does. Do not wrap LABEL tags around input controls (implicit labels) since this is very unreliable in older screen readers.

<div>

LABEL elements should be associated with other controls using FOR attributes.

Line 80 WCAG2 A 4.1.2

Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.

<label>Password</label>

This form control has no associated LABEL element.

Line 82 WCAG2 A F68 Section 508 1194.22 (n)

This form has fields without LABEL elements or TITLE attributes.

Line 82 Section 508 1194.22 (n)

Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users. Without these, forms are very hard to use with a screen reader. Forms designed to be completed online 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.

Search engines cannot index areas of sites that require a log in.

Line 82 Google Blogs

Use LABEL tags for each data entry field to show what data is expected.

Line 82 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

</div>

Use text links rather than image links. In general, text links are more easily recognized as clickable.

Line 87 Usability.gov 10:6

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 87 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

</a>

</div>

This form control has no associated LABEL element.

Line 92 WCAG2 A F68 Section 508 1194.22 (n)

Remember me </label>

<li><a class="registration_link" href="http://community.elgg.org/register">Register</a></li> <li><a class="forgot_link" href="http://community.elgg.org/forgotpassword">

Lost password </a></li>

</ul>

</div>

</fieldset></form></div></div></div>

<ul class="elgg-menu elgg-menu-site elgg-menu-site-default clearfix"><li class="elgg-menu-item-activity"><a href="http://community.elgg.org/activity">Activity</a></li><li class="elgg-menu-item-discussion"><a href="http://community.elgg.org/discussion/all">Discussion</a></li><li class="elgg-menu-item-groups"><a href="http://community.elgg.org/groups/all">Groups</a></li><li class="elgg-menu-item-plugins"><a href="http://community.elgg.org/plugins">Plugins</a></li><li class="elgg-menu-item-showcase"><a href="http://community.elgg.org/showcase">Showcase</a></li><li class="elgg-menu-item-themes"><a href="http://community.elgg.org/plugins/category/themes">Themes</a></li></ul>

All FIELDSET tags should be labeled with LEGEND tags.

Line 106 WCAG2 A H71

The first element inside the FIELDSET must be a LEGEND element, which provides a label or description for the group.

This form control has no associated LABEL element.

Line 107 WCAG2 A F68 Section 508 1194.22 (n)

The REQUIRED attribute is not supported in Internet Explorer 9 and earlier.

Line 107 Internet Explorer

JavaScript changes: added required='-1'

<input type="text" class="search-input" size="21" placeholder

There is no attribute "placeholder".

Line 107 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="Google search" required

"required" is not a member of a group specified for any attribute.

Line 107 HTML Validation

</fieldset>

</form>

<scrip

Required attribute "type" not specified.

Line 113 HTML Validation

$('.elgg-search').live('submit', function() {

var userQuery = $(this).find('.search-input').first().val();

var q = $(this).find('[name="q"]');

q.val("site:http://community.elgg.org/ " + userQuery);

});

</script>

</div>

This page has more than one H1 tag, which violates Bing webmaster guidelines.

Line 129 Bing

Leave the title of the main content as H1 and change other H1 tags to a lower heading level.

<h1><span>elgg</span>Community</h1>

<h2>Community support from<br />community members</h2>

Each A tag must contain text or an IMG with an ALT tag.

Line 131 WCAG2 A F89

Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT tag is blank, screen readers have nothing to read, so read out the URL instead.

</div>

<div class="elgg-module elgg-module-aside" ><div class="elgg-head"><h3>Login</h3></div><div class="elgg-body"><form method="post" action="http://community.elgg.org/action/login" class="elgg-form elgg-form-login">

All FIELDSET tags should be labeled with LEGEND tags.

Line 134 WCAG2 A H71

The first element inside the FIELDSET must be a LEGEND element, which provides a label or description for the group.

JavaScript changes: changed to value='56371ed0375e704a366d0dc0955ab954'

JavaScript changes: changed to value='1379696959'

<div>

LABEL elements should be associated with other controls using FOR attributes.

Line 136 WCAG2 A 4.1.2

Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.

<label>Username or email</label>

This form control has no associated LABEL element.

Line 137 WCAG2 A F68 Section 508 1194.22 (n)

This form has fields without LABEL elements or TITLE attributes.

Line 137 Section 508 1194.22 (n)

Use LABEL tags for each data entry field to show what data is expected.

Line 137 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<div>

LABEL elements should be associated with other controls using FOR attributes.

Line 139 WCAG2 A 4.1.2

Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.

<label>Password</label>

This form control has no associated LABEL element.

Line 141 WCAG2 A F68 Section 508 1194.22 (n)

This form has fields without LABEL elements or TITLE attributes.

Line 141 Section 508 1194.22 (n)

Search engines cannot index areas of sites that require a log in.

Line 141 Google Blogs

Use LABEL tags for each data entry field to show what data is expected.

Line 141 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

</div>

Use text links rather than image links. In general, text links are more easily recognized as clickable.

Line 146 Usability.gov 10:6

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 146 Usability.gov 14:3

</a>

</div>

This form control has no associated LABEL element.

Line 151 WCAG2 A F68 Section 508 1194.22 (n)

Remember me </label>

<li><a class="registration_link" href="http://community.elgg.org/register">Register</a></li> <li><a class="forgot_link" href="http://community.elgg.org/forgotpassword">

Lost password </a></li>

</ul>

</div>

</fieldset></form></div></div> </div>

</div>

<div class="elgg-module elgg-module-community-plugins elgg-module-community" ><div class="elgg-head"><h3>Plugins</h3></div><div class="elgg-body"><p>Contribute, find, review</p>

Don't use generic text like "Click Here" or "Read More" in link text, because it says nothing about the link target when read out by a screen reader. Link text: "more..."

Line 167 WCAG2 AAA F84

Either change the link text, or add a TITLE attribute to the link with a fuller description of the link destination.

If several links on a page use the same link text, all those links should point to the same destination. This text is used in some of the duplicated links: "more...".

Line 167 WCAG2 AAA 2.4.9

If several links refer to different targets but share the same link text, add additional link text hidden offscreen by CSS.

Users should be able to quickly look at each link and tell where it goes. Link text: "more..."

Line 167 Usability.gov 10:1

Don't use generic link labels like "click here" or "read more" because they're hard to tell apart when users scan a page.

<div class="elgg-module elgg-module-community-discussion elgg-module-community" ><div class="elgg-head"><h3>Discussion</h3></div><div class="elgg-body"><p>Community discussion is a great way to find support and help others.</p>

Don't use generic text like "Click Here" or "Read More" in link text, because it says nothing about the link target when read out by a screen reader. Link text: "more..."

Line 170 WCAG2 AAA F84

Either change the link text, or add a TITLE attribute to the link with a fuller description of the link destination.

Users should be able to quickly look at each link and tell where it goes. Link text: "more..."

Line 170 Usability.gov 10:1

Don't use generic link labels like "click here" or "read more" because they're hard to tell apart when users scan a page.

<div class="elgg-module elgg-module-community-more elgg-module-community" ><div class="elgg-head"><h3>More</h3></div><div class="elgg-body"><p>Contribute to Elgg. Open source works best as a community.</p>

<ul>

<li class="bug_tracker"><b>Bug tracker</b><br /><a href="https://github.com/Elgg/Elgg/issues">Github</a></li>

<li class="mailing_list"><b>Mailing list and IRC</b><br /><a href="http://groups.google.com/group/elgg-development/">For developers</a> also <a href="http://webchat.freenode.net/?channels=#elgg">#Elgg on Freenode.net.</a></li>

<li class="api_reference"><b>API reference</b><br />The best way to find out what functions exist. <a href="http://reference.elgg.org">Check it out</a>.</li>

</ul>

</div></div> </div>

</div>

<h2>Navigation</h2><ul class="elgg-menu elgg-menu-footer-navigation elgg-menu-footer-navigation-default"><li class="elgg-menu-item-home"><a href="http://elgg.org">Home</a></li><li class="elgg-menu-item-community"><a href="http://community.elgg.org">Community</a></li><li class="elgg-menu-item-blog"><a href="http://blog.elgg.org">Blog</a></li><li class="elgg-menu-item-hosting"><a href="http://elgg.org/hosting.php">Hosting</a></li><li class="elgg-menu-item-services"><a href="http://elgg.org/services.php">Services</a></li><li class="elgg-menu-item-docs"><a href="http://docs.elgg.org">Docs</a></li></ul> </div>

<h2>Contact</h2>

</div>

Document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag.

Line 195 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 195 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

2>Legal</h2>

Elgg is a registered trademark of Thematic Networks.<br />

<a href="http://elgg.org/domain.php">Domain policy</a>.<br />

</span>

<ul class="elgg-menu elgg-menu-footer elgg-menu-hz float-alt ptl elgg-menu-footer-default"><li class="elgg-menu-item-about"><a href="http://community.elgg.org/about">About</a></li><li class="elgg-menu-item-privacy"><a href="http://community.elgg.org/privacy">Privacy</a></li><li class="elgg-menu-item-terms"><a href="http://community.elgg.org/terms">Terms</a></li></ul></div> </div>

</div>

(function() {

var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true;

po.src = 'https://apis.google.com/js/plusone.js';

var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s);

})();

</script></body>

</html>

URL:	http://community.elgg.org/
HTTP Status:	200 OK
MIME Type:	text/html
Last Modified:	Mon, 01 Jan 1601 00:00:00 GMT
Download Time:	Less than a second
Cookies:	Elgg=hkbn4u8edn963gs3k7ivosc7
Size:	12 KB
Page Weight:	21 KB (total size of HTML, CSS, JavaScript and images)
Depth:	0 clicks from home page
Charset:	UTF-8
Forms:	3 forms containing 16 controls
HTTP Headers:	8 headers Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection: keep-alive Date: Fri, 20 Sep 2013 17:09:18 GMT Pragma: no-cache Server: nginx/0.7.65 Set-Cookie: Elgg=hkbn4u8edn963gs3k7ivosc7u5; path=/ Transfer-Encoding: chunked X-Powered-By: PHP/5.3.2-1ubuntu4.7ppa5~lucid1
Links In:	1 pages http://community.elgg.org/
Links Out:	24 links http://community.elgg.org/ http://community.elgg.org/login http://community.elgg.org/twitter_api/forward http://community.elgg.org/register http://community.elgg.org/forgotpassword http://community.elgg.org/activity http://community.elgg.org/discussion/all http://community.elgg.org/groups/all http://community.elgg.org/plugins http://community.elgg.org/showcase http://community.elgg.org/plugins/category/themes https://github.com/Elgg/Elgg/issues http://groups.google.com/group/elgg-development/ http://webchat.freenode.net/?channels= http://reference.elgg.org/ http://elgg.org/ http://blog.elgg.org/ http://elgg.org/hosting.php http://elgg.org/services.php http://docs.elgg.org/ http://elgg.org/domain.php http://community.elgg.org/about http://community.elgg.org/privacy http://community.elgg.org/terms
Images:	2 images http://community.elgg.org/mod/community_theme/graphics/logo.png 9 KB http://community.elgg.org/mod/twitter_api/graphics/sign-in-with-twitter-d.png 0 KB
CSS:	0 files
JavaScript:	0 files

Issues:	21 issues found on 45 lines

HTML Document