worklog

Listening to a webcast of an interview with Alexander Limi about accessibility concerns in Plone and how it was built into Plone from the beginning. It turns out that by building Plone to standards they inadvertently made Plone mostly accessible. After they saw how some disabled users were able to use Plone without having previously thought about it, the development team made a conscious decision to persue and improve accessibility as a core development value in Plone. As a nice aside, he slams the AJAX craze.

There is a summary at webstandards.org http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/. For the full webcast, checkout The National Center on Access and Education’s full webcast: Accessibility and the Open Source Content Management Movement.

Sometimes good things are broken…

Had to fix the contents of template-functions-post.php, when iterating through pages it was outputting an extra <li tag. wrapped around an <ul> some stuff </ul> without a parent <ul element. This was in the function wp_list_pages call.

That was the only fault of wordpress. The template however… wow, it was kind of broken. I didn’t notice until I noticed that I had two of the cat backgrounds showing up and couldn’t figure out why - turned out to be multiple div closings when there weren’t divs and then the misuse of the id attribute - naming multiple things for the same id. Moral of the story? 1) Validate your pages, 2) Understand looping - it seems that sometimes people don’t know when or where to stop