Category: wordpress

Podcast #96: WordPress, Events

Dennis and Ross are back! It’s been a while since the last podcast, and the guys catch up on events, news, and lots of great things happening with accessibility on WordPress.

Download Web Axe Episode 96 (WordPress, Events)

[transcript of podcast 96]

New Song!

So besides a new website, there’s a new Web Axe theme song! The vocal track isn’t added yet, so this episode will have an instrumental version.

The original WebAxe Theme Music is composed and produced by Jeff Ensign a.k.a. Evolution Noise Slave. Check out his work at glafizya.com.

Goings On

News

WordPress

Links

Events

Announcing the New Web Axe Website!

Welcome to the new Web Axe website, WebAxe.org! The RSS feed has also changed. It is now: http://www.webaxe.org/feed/

After over 7 years on Blogger, the website has moved to WordPress. It uses a fairly customized version of the Blaskan theme. Two important plug-ins used are WP Accessibility and WP-Accessible Twitter feed.

Reasons for the change include a fresh responsive design; a shorter and more accurate domain name; and, of course, to get off Blogger (which itself has many reasons, too many to list!)

What do you think of the new site?

About CMS Accessibility

This article was written for Web Axe by our friend, John Siebert, a Tampa Web Designer who has an interest in creating accessible web sites.

Content management systems (CMS) are a good way to go for both personal and business use. An open source CMS can get a website up efficiently, but is it accessible? With about 25% of internet users needing accessibility, it is very encouraging to keep your site web accessible. This is for every “human user” disabled and non-disabled no matter what browsing technology they are using. CMS platforms can definitely help you with that. But which one is the most accessible friendly? We will look into WordPress, Drupal, Joomla, and Posterous and compare the level of web accessibility.

All users have equal access to information and functionality. It is the developer’s responsibility to correctly design and develop a site that everyone can view and understand. What effects accessibility includes layout, markup, images and media, and JavaScript. A good CMS platform can make sure that these issues are compliant.

WordPress

WordPress states that it is web accessibility compliant. Unfortunately if developers tweak or create templates, it is up to the developer how well or little they configure accessibly into the site. There are plenty of accessibility plugins that a developer can implement into their WordPress site.

Here is a very helpful link full of WordPress accessibility plugins. WordPress also provides plenty of information and guidelines for creators that cover all basic HTML topics. Also check out the comments in the Web Axe blog on accessible WordPress themes.

Drupal

Drupal has plenty of helpful links for tips and topics to input accessibility into their platform. A helpful Drupal tutorial goes over:

  • What are the common accessibility barriers that my website needs to overcome, and how?
  • What tools help me manage the accessibility of contributed content that is beyond my control?
  • What Drupal modules and 3rd party accessibility tools will help?

You may want to check out the Web Axe podcast on the Drupal 7 and accessibility from last October. And here are a few more links for Drupal accessibility:

Posterous

Posterous does not cover as much accessibility information as other CMS platforms. Which leads me to believe that Posertous would not have much support for developers using their platform. We think it’s time Posterous stepped up to the plate on this issue and have sent them an e-mail with our concerns.

Joomla

Joomla has their own accessibility statement that shares their promises of fulfilling a true web accessible environment. However, they state that it is up to the designers and template designers to follow rules and regulations. They also state that they understand that the Joomla site itself does not comply with many WCAG/508 requirements.

Conclusion

When choosing a CMS platform, find one that has the most web accessibility support. The best would be WordPress and Drupal out of the four compared. By using a CMS platform you will have more support to maintain a web accessible site. Most of the accessibility changes can be fixed once and to the entire site through these platforms, saving time and money.

The best way to understand accessibility is to get to know a user that benefits from the accessibility you put into code. Once you understand the reason why accessibility is important for your site, you can then comprehend the reason for a CMS platform like WordPress or Drupal as the base of your site.

If you have any feedback about CMS and accessibility, especially Posterous and Joomla, please leave a comment.

Podcast #78: Web Accessibility News

Hosts Dennis and Ross discuss a variety of topics.

Download Web Axe Episode 78 (Web Accessibility News)

[transcript of podcast 78] (Much thanks to Joseph Montanez for helping with transcription.)

Announcements

News

Articles

Podcast #76: Web Accessibility Disasters

Dennis and Ross review web sites which should be great in web accessibility, but fail badly. The hosts provide a lot of constructive criticism, including many fixes that can be done in a minimal amount of time. Issues are also good to discuss as a reminder for our own work.

Download Web Axe Episode 76 (Web Accessibility Disasters)

[transcript of podcast 76]

Transcription provided by Katherine Lynch, a Drupal, WordPress, and accessibility professional.

Chatter

Articles

Web Site Disasters

Digitalaccessibiliy

Company targeting Accessibility for Ontarians with Disabilities Act (AODA)

The Good
  • Almost all of the text is marked up in HTML rather than image, flash or other media.
  • Simple, clean design.
The Bad
  • No ALT text on main banner.
  • Font size tool (triple whammy).
  • Underlines not links; links not underlined.
  • Headings not marked up appropriately.
  • Menu missing
    • List not a list (see Compliance page).
    • Inline / intrusive JavaScript.
    Job Accommodation Network (JAN)

    A service provided by the U.S. Department of Labor’s Office of Disability Employment Policy (ODEP). JAN’s mission is to facilitate the employment and retention of workers with disabilities by providing employers, employment providers, people with disabilities, and family members with information on job accommodations, entrepreneurship, and related subjects.

    The Good
    • Textual navigation; no Javascript based navigation.
    • Has proper ALT text on pictures and JAN and ODEP logos.
    The Bad
    • No heading tags; some marked up with bold tag.
    • There is a summary on layout table (double whammy).
    • No skip nav or skip to link provided.
    • Inline javascript. Example:
    • Non-breaking spacing used for layout.
    The Rose Project

    Mission is to provide maternal and child healthcare to the economically poor people of Malawi, with particular reference to HIV treatment and care.

    One of nine listed for Most Accessible Website in the Irish Web Awards?

    The Good
    • XHTML; semantic, clean mark-up
    • Using headings
    • Language is defined (xml:lang=”en”)
    • SWFobject.js for unobtrusive flash embedding
    The Bad
    • When JavaScript is unavailable, Flash replacement image has broken links and placeholder text.
    • Skip links – Skip link doesn’t work?
    • ‘Find out about ways to give’ button.
    • logo missing alt text for tag line.
    • H1 headings should be H2 (such as Featured Project).
    • Some links that should be underlined, are not.
    • Use of tags not recommended.
    • Links lack the default focus effect and outline removed!
      DO NOT do this:
    :focus {
    outline-color:-moz-use-text-color;
    outline-style:none;
    outline-width:0;
    }