This fork of Joomla to improve accessibility interested me
Accessible (a8e) Joomla! is a Joomla! fork that conforms to accessibility guidelines and web standards. A8e Joomla! will follow regular Joomla! releases. The project should implode when regular Joomla! finally conforms to the standards.
Accessibility of Internet sites is very huge within the federal government and addressed by Section 508 of the Rehabilitation Act, 1998.
In 1998, Congress amended the Rehabilitation Act to require Federal agencies to make their electronic and information technology accessible to people with disabilities. Inaccessible technology interferes with an individual's ability to obtain and use information quickly and easily. Section 508 was enacted to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals. The law applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology.
About every Webmaster that I've talked to about accessibility, inside and outside of the federal government, agrees with the goals of accessibility. They're just not sure how best to design and manage their pages due to the rapidly changing online technology.
I have never really worried whether I was certified or not. This Computerworld article gets right to the point:
Depending on whom you talk to, certification programs are either borderline rip-offs that provide little useful knowledge, or valuable hiring tools that make it easier for IT execs to pick the most promising new employees.
Available from vendors focusing on their own products, or outside organizations offering multi-vendor training, these certificate programs are expanding to fill the many specialized technology subsets that have multiplied along with the growth of data storage and other IT areas.
Now this isn't to say that I don't have a few IT certifications under the belt and didn't receive some benefit from them. One of the most intensive IT certifications of recent years was in IT security and another to "please" the crowd was a certification for migration to Microsoft's Server 2003. By the time I was done with those certifications though, I didn't know enough to get the job done.
For the most part, I usually say "no" to making New Year resolutions and IT predictions. I never really get things 100% completed to say I've resolved those things that I previously promised. I have yet to ever fully predict what is just around the corner for IT (actually it almost usually turns out better than even my most optimistic predictions). However, no matter the time of year, I always have goals that I strive to meet.
The following are some of my open source IT goals for 2007:
- Return of the Geek. Outside my "day job", the past year has been filled with freelance projects designing and hosting sites for various clients. As I wrote a few months ago, the whole experience of working outside of work for cash has led a bad taste to my mouth. When you really don't need the money, why do it? For 2007, I rather spend my time contributing to open source projects such as Drupal. I've been a wall flower for too long and I think the core developers would like to see wall flowers not be wall flowers.
- For sites that I own, I need to do a better job of installing the betas and release candidates. For example, when I started CMS Report it was with Drupal 4.7 Beta 1. I'm sad to report that this site is still using Drupal 4.7. It's very hard to contribute to open source if you're not willing to go on the edge with some of your production sites.
The discrepancy has revived complaints about the accuracy of reporting agencies' results, which often differ from companies' own audience measurements (see BusinessWeek.com, 10/23/06, "Web Numbers: What's Real"). It also underscores the rivalry between comScore and Nielsen//NetRatings for recognition as the most trusted source for Web-traffic data. The winner, if one emerges, may set the standard for how site popularity is measured, influencing how marketers dole out billions in online ad dollars each year. Recognizing the high stakes in that tussle, comScore and Nielsen//NetRatings both are refining their tactics.
Initially, you might say, "who cares, the sites I design won't compete with these big dogs". But consider this, there is not a client or site owner that doesn't want to see more traffic with their sites. The client already knows how many users they were getting with the old site. What happens if the client now observes that the site you redesigned gets less traffic? At least, less traffic according to the the statistic package they are using. Either way, the client isn't happy and wants to know what you're going to do to correct the problem?
On a recent visit to Drupal's forum I found another post with both Joomla and Drupal in the subject line. Making comparisons between Joomla and Drupal are very common these days as they are currently considered the top two open source content management systems (CMS) out there. The forum post written by Steve Burge contains a link that takes you to a comparison table he did between Joomla and Drupal. While the table may not give the full picture of each CMS, I'm convinced that Burge tried to be as non-bias as he possibly could in his comparison.
There is something interesting about the table posted at Burge's site. Specifically, take a look at which elements according to Burge each CMS excels in and which elements each CMS fails. Did you notice a particular pattern in where each CMS is considered to have failed? If not, perhaps you didn't see the excerpt I posted earlier from Gadgetopia's Deane Barker, titled Architecture and Functionality in Content Management.