Theme Accessibility [#342524]

Can you tell me if your theme validates according to:
* WCAG 1.0 Priority 1
* XHTML 1.0 Strict

Also, info on Section 508 compliance would also be useful.

I haven't found an easy way to scan through those themes which comply.

Comments

Comment #1

peterx CreditAttribution: peterx commented 24 February 2009 at 05:51

Visit http://d-theme.com/sharepoint_like. 6.x-1.1 is WCAG AA etc as far as a computer can check. The Cynthia Says links produce checklists of additional tests to be performed by humans.

Comment #2

mgifford

he/him

English

CreditAttribution: mgifford commented 25 February 2009 at 20:48

I still get 3 Validation Output errors:
Error Line 151, Column 59: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag.
…r links">

And from http://wave.webaim.org/
Uh oh, WAVE has detected 2 accessibility errors

From an empty H1 tag and an empty H2 tag.

Thoughts?

Mike

Comment #3

peterx CreditAttribution: peterx commented 26 February 2009 at 00:40

Links can contain ul elements. ul elements are not allowed inside text level elements including em. The following line in node.tpl.php is probably causing one of the validation errors.
<div class="clear links"><em><?php print $links ?></em></div>

In page.tpl.php there is a h1 around site name. Is your site name empty?

Comment #4

mgifford

he/him

English

CreditAttribution: mgifford commented 26 February 2009 at 05:08

Well, in page.tpl.php, these are the lines in question:

 17       <?php if ($site_name) { ?><h1 class='site-name'><a href="<?php print base_path() ?>" title="<?php print t('Home') ?>"><?php print $site_name ?></a><?php } ?>
 18       <span class="small"><br />&#8226; &#8226; &#8226; &#8226; &#8226;</span></h1>

This isn't ideal as if the $site_name isn't there then the theme is definitely broken.

However, this produces the following html:

      <h1 class='site-name'><a href="/" title="Home">Theme Testing</a>			<span class="small"><br />&#8226; &#8226; &#8226; &#8226; &#8226;</span></h1>

Which shouldn't be causing any issues that I can see.

Mike