Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Accessibility OptionsAccessibility Options
Previous
 
Next
New Post
7/31/2009 10:52 AM
 

 

Hi everyone,

As you all know accessibility is a very hot topic these days…I was wondering if there are any discussions over adding accessibility controls to the core framework.

I would also like to give an example as to what that would mean. When you insert a Text/HTML module on your site you can modify all settings from text to images etc etc.

What I would like to see, if you upload and insert an image but you have forgotten to add an alternate text to instantly get a warning message. (I hope that example makes sense).

I would be happy if you all give your input on this matter.

Many thanks

 
New Post
7/31/2009 3:27 PM
 

Why not use a section 508 scanner to accomplish the same thing?  The tools already exist, why reinvent the wheel and complicate the interface?

Jeff

 
New Post
7/31/2009 4:23 PM
 

Hi Jeff,

Jeff Cochran wrote

Why not use a section 508 scanner to accomplish the same thing?  

I agree. As a developer you can and you should use a number of accessibility tools against your websites to make sure they conform. 

Jeff Cochran wrote

... complicate the interface?

When setting a site up for clients you ideally want them to manage it (administration and content updates) for themselves. You can write a manual, train them, educate them and instruct them accordingly. But people do tend to rotate. And an administrator cannot always be available. If the system allows warning messages (i.e. an option under the host settings to enable accessibility checks), even the less tech savvy content editor can produce a compliant content and avoid mistakes. 

 
New Post
8/1/2009 9:51 AM
 

 I agree with Jeff - I also think it would make things more difficult for inexperienced admins & authors if they get lots or warning or error messages.

A warning is only valid if you understand its context and meaning.

Not sure about writing manuals though - hours of photoshop and writing.
These days I use Camtasia and make short video clips to cover the various topics and tasks.
I find managers are happy to pay for these as it keeps training budgets independent of staff changes.
Staff seem to like them too and most are able to be productive from them.

The warning I would like is to be able to flag a particular admin and get an email whenever they have done something!

Ian


Mutate and Survive
 
New Post
8/1/2009 11:43 AM
 

I guess I'm more of the opinion that accessibility has to start with content, and if the content author or editor doesn't understand accessibility then nothing will help.  The simple things, a missing ALT attribute on an IMG tag, could be solved simply with defaults, not warnings.  But in the scheme of accessibility, those are extremely mionor errors.  Using a graphic to supply textual content can't be solved simply by a warning or by a default, the ALT attribute has to accurately replicate the text in the graphic.  Or better, by properly using CSS instead of making it a graphic.  How do you warn about that or force it to happen, other than by user training and skill?

The only thing DNN should do is enaure that all the core code renders HTML and CSS that complies with accessibility standards.  Which will never happen with the default navigation objects of course.  But the skins and content have to be the responsibility of the end designer and author.

Jeff

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Accessibility OptionsAccessibility Options


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out