Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#5 | page.tpl_.php_.patch | 447 bytes | mgifford |
#5 | node.tpl_.php_.patch | 497 bytes | mgifford |
Comments
Comment #1
mgiffordJust the CSS validates in this theme.
Comment #2
peterx CreditAttribution: peterx commented6.x-1.6 validates as XHTML 1.0 strict, WAI A and AA, plus US 508 with just one change. The change is described at http://d-theme.com/burnt and the page implements the change plus has validation buttons.
You can still make a page fail validation by including bad content, something that is nothing to do with the theme. As an example, in the test page I created a link from the test page back to drupal.org. In the link I specified the link text of
and that is the same as the link text in one of the menu entries. Under WAI AA, duplicate link text is illegal unless you provide title atrtributes in both links to distinguish the links. The menu already includes the title attribute. All I had to do was include a title in the link I created on the page.Comment #3
peterx CreditAttribution: peterx commented6.x-1.6 node.tpl.php:
Change:
<em class="clear links"><?php print $links; ?></em>
to:
<div class="clear links"><?php print $links; ?></div>
because $links can contain HTML elements.
Change:
<em class="clear terms"><?php print $terms; ?></em>
to:
<div class="clear terms"><?php print $terms; ?></div>
because $terms can contain HTML elements.
Comment #4
peterx CreditAttribution: peterx commented6.x-1.6 style.css:
font-family: Lucida Grande, Tahoma, Arial, Helvetica, sans-serif;
should be:
font-family: "Lucida Grande", Tahoma, Arial, Helvetica, sans-serif;
Comment #5
mgiffordHere's a patch for this. Also seems to be a problem with the footer in the page.tpl.php file.
Comment #6
mgiffordadding accessibility tag