Public Forums 71,145 posts

[chrisyork Friend chrisyorkJoin date: September 2010Posts: 3Downloads:3Uploads:0]

#154667

Hi,

I would like my site to validate to AA standards but I have come across some issues that are based around the JAT3 system…

PRIORITY 1:
These are the cpanel settings, which fail:
# These links won’t work if javascript is not supported. (2)#

* Line 210: <a href=”#” onclick=”cpanel_apply();return false;” class=”button” title=”Apply setting”>
* Line 211: <a href=”#” onclick=”cpanel_reset();return false;” title=”Reset to default setting”>

These are queried:

# Ensure this document can be read without style sheets (24)#

* Line 15: <link rel=”stylesheet” href=”/index.php?jat3action=gzip&type=css&file=t3-assets%2Fd346fc8c047e4c64181715260e21031b.78d628c554e53de56b8d8ef1f733233c.css” type=”text/css” />
* Line 47: <style type=”text/css”>
* Line 98: <div class=”childcontent-inner clearfix” style=”width: 200px;”>
* Line 98: <div class=”megacol column1 first” style=”width: 200px;”>

# This element may not be accessible to all users. Please ensure there is an accessible interface to this object (7)#

* Line 16: <script type=”text/javascript” src=”/index.php?jat3action=gzip&type=js&file=t3-assets%2Fc8a739b6f1ba45b3021d0f0dcf5c062e.6543500cf0beb2d8e2d4afe49b4b6c69.js”>

This is probably not a problem, but I thought it is worth highlighting

PRIORITY 2:

# This element uses absolute units of measure rather than relative units of measure (17)#

* Line 98: <div class=”childcontent-inner clearfix” style=”width: 200px;”>
* Line 98: <div class=”megacol column1 first” style=”width: 200px;”>

and
# Verify absolute units of measure are not used on stylesheets (2)#

* Line 15: <link rel=”stylesheet” href=”/index.php?jat3action=gzip&type=css&file=t3-assets%2Fd346fc8c047e4c64181715260e21031b.78d628c554e53de56b8d8ef1f733233c.css” type=”text/css” />

# Improper header nesting: Header levels must not increase by more than one level per heading. Do not use headings to create font effects; use style sheets to change font styles (1)#

* Line 173: <h3>

# For non-decorative effects provide redundant event handlers to ensure device-independent. (5)#

* Line 177: <a title=”Increase font size” onclick=”switchFontSize(‘walking-the-talk-t3_font’, ‘inc’);return false;”>
* Line 178: <a title=”Decrease font size” onclick=”switchFontSize(‘walking-the-talk-t3_font’, ‘dec’);return false;”>
* Line 179: <a title=”Default font size” onclick=”switchFontSize(‘walking-the-talk-t3_font’, ‘reset’);return false;”>
* Line 210: <a href=”#” onclick=”cpanel_apply();return false;” class=”button” title=”Apply setting”>
* Line 211: <a href=”#” onclick=”cpanel_reset();return false;” title=”Reset to default setting”>

and for the same lines

#For scripts, specify logical event handlers rather than device-dependent event handlers (5) #

I wonder if anyone can give me information about how to solve these issues… or maybe it is something that is ‘in development’…

[Khanh Le Moderator Khanh LeJoin date: November 2013Posts: 1884Downloads:41Uploads:31 Thanks: 44 Thanked: 203 times in 131 posts]

#357052

In this case, you can disable the cpanel (by disable all option in User tools section, Tab Profiles) and don’t use compress for js/css optimize. In my idea, following all standards is good, but in some case it could cut your power off.

[chrisyork Friend chrisyorkJoin date: September 2010Posts: 3Downloads:3Uploads:0]

#362097

<em>@khanh le 195995 wrote:</em><blockquote>In this case, you can disable the cpanel (by disable all option in User tools section, Tab Profiles) and don’t use compress for js/css optimize. In my idea, following all standards is good, but in some case it could cut your power off.</blockquote>

Thanks for your response to this – sorry for the delay in responding, I wasn’t being deliberately rude.

The problem with not following standards is that when you have a client who wants you to ensure that the work you do for them ‘complies with AA accessibility’, it is difficult to point to your own website as an example!

I understand the desire for power (or whistles and bells), but they need to be things that you turn on, rather than have to turn off… a bit like the opt-in for emails. That way people who use JoomlaArt’s (excellent) systems can rest assured that they are following good practice, but can CHOOSE to get more ‘power’ if they find something missing. Hope this makes sense – it is supposed to be one of the advantages of using CMS like Joomla – we let someone else worry about the ‘technical side’ and get on with working out the structure and populating content…

So as a thought for future development, if it were possible to define specific pages that are fully compliant (e.g. a home page or an ‘accessible version’) in the back end, this would be a helpful feature.

Good work with the JAT3, its a great system so this is constructive feedback rather than cricitism.

[Author]

Posts