Elxis CMS Forum
Support => General => Topic started by: theprincy on December 12, 2006, 21:57:59
-
it is accessible in accordance with the 508 and WCAG ?
if it is not him/it you would be able here also inziare the job that I have completed for mambo 4.5.4:) only that deals with to make some changes to the core
-
What is the 508 / WCAG???
-
508 : http://www.access-board.gov/508.htm
Section 508 requires Federal departments and agencies that develop, procure, maintain, or use electronic and information technology to ensure that Federal employees and members of the public with disabilities have access to and use of information and data, comparable to that of the employees and members of the public without disabilities–unless it is an undue burden to do so
WCAG : http://www.w3.org/TR/WCAG10/
Abstract
These guidelines explain how to make Web content accessible to people with disabilities. The guidelines are intended for all Web content developers (page authors and site designers) and for developers of authoring tools. The primary goal of these guidelines is to promote accessibility. However, following them will also make Web content more available to all users, whatever user agent they are using (e.g., desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.). Following these guidelines will also help people find information on the Web more quickly. These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.
a site of elxis ( http://test.powerpcweb.it/elxis ), almost valid for the 508 I must add only some labels to the layout, in morning it should be valid ::) ;) if everything is all right
-
Can you post here some examples of what changes you did for 508/WCAG compliance? If I understood well one of the things you did was to add everywhere title and alt attributes. Is this correct? In Elxis we already make mass use of "title" instead of the "alt" attribute in url's and images. "title" is compatible with all browsers but "alt" is not compatible with firefox. Any other example?
-
EX:
components/com_content/content.php
from
echo '<tr>';
echo '<td valign="top">';
for ( $z = 0; $z < $leading; $z++ ) {
if ( $i >= $total ) {
// stops loop if total number of items is less than the number set to display as leading
break;
}
echo '<div>';
show( $rows[$i], $params, $gid, $access, $pop, $option, $ItemidCount );
echo '</div>';
$i++;
}
echo '</td>';
echo '</tr>';
to
// echo '<tr>';
// echo '<td valign="top">';
for ( $z = 0; $z < $leading; $z++ ) {
if ( $i >= $total ) {
// stops loop if total number of items is less than the number set to display as leading
break;
}
echo '<div>';
show( $rows[$i], $params, $gid, $access, $pop, $option, $ItemidCount );
echo '</div>';
$i++;
}
//echo '</td>';
//echo '</tr>';
or
elxis/includes
from
echo ( "<span class=\"pathway\">". $home ." ". $path ."</span>\n" );
to
echo ( "<ul class=\"pathway\">". $home ." ". $path ."</ul>\n" );
or
elxis/includes/frontend.html.php
<table cellpadding="0" cellspacing="0" class="moduletable<?php echo $moduleclass_sfx; ?>">
<?php
if ( $module->showtitle != 0 ) {
?>
<tr>
<th valign="top">
<?php echo $module->title; ?>
</th>
</tr>
to
<div cellpadding="0" cellspacing="0" class="moduletable<?php echo $moduleclass_sfx; ?>">
<?php
if ( $module->showtitle != 0 ) {
?>
<h3>
<?php echo $module->title; ?>
</h3>
this they are only some modified files, if you want I prepare you the package that I am modifcando and I send you him
-
Ok, you replaced tables and other "static" tags and attributes with divs and tags that have a kind of meaning, like the h1 tag, maybe the <ul>, <li> or <p> tags etc. If I guess well this is due to the voice browsers to understand and emphasize the reading text better. Replacing the tables with divs is something I also like, for other reasons, but requires many changes in Elxis and in current templates and css. It is not so simple as it requires a mass re-writting of the html output in frontend. A disadvantage is that the table usage create a more "solid" content that is easier to display fine. Divs require many css hacks to display correctly with all browsers.
-
actually to I have modified only hourly 10 files, it is validato 508, WCAG An and WCAG AAA while for WCAG AA the alone problem the template to be structured better, believes that I can say that they are almost there to the attainment of the destination, if it interests yourself I pass you the files actually modified to hourly
-
Hi since would not I want every time to refer the job dall beginning that you say to already implement these changes in the next release?
-
You can send me the files you modified in a zip to check them when it is time to start develioping the next version. I am uncertain about how this solution will go well with existing templates and third party components, modules etc. It must be checked thoroughly.
-
you have a p.m ;)