We uploaded some styling and layout fixes to the staging and production servers earlier today, bringing both of them up to date with our private development server. For now, everything is mostly good. Here’s a quick rundown:
Sidebars were being bad. Very bad. They wouldn’t align right or left according to theme option settings, so we had that fixed. This wasn’t a problem on the production server but those of you using the staging server, test.publish, to test things out (over a hundred of you), this was extremely problematic. This has been resolved and is unlikely to happen again. Thank you for being patient.
Speaking of blog sidebars, the “POST sidebar” is now obsolete. From now on, the Blog Index Sidebar will appear on all posts. This includes the blog landing page (known as the blog index), individual blog posts, and categories. This was to provide consistency to post-related components and streamline the publishing process.
Also, some minor aesthetic styling changes were made to the sidebar. I don’t recall the nature of all the changes that were made, but they were all good.
When using the “skip to content” feature (hint: when your site loads, press tab then press enter), keyboard focus moves to the next link when hitting tab a second time. Prior to today, this was broken; pressing tab a second time used to take the user to the top instead of to the next link on the page, which was a violation of Illinois Information Technology Accessibility Act Implementation Guideline #9.4. As a public state entity, we are bound by law to make all of our web content accessible to all, and this fix brings our WordPress theme that much more compliant.
While an accessible theme doesn’t necessarily guarantee accessible content (that is a blog post for another day), it’s definitely a step in the right direction.
In the pipeline
A navigation and documentation revamp is on the way. Also, we’d like to update the production server to v3.9.1, as well as update all of its plugins.
Note: it seems the Blog index can only display the “default header image” as its header image. It appears to be a new bug. We prefer that header images be customizable, so we’re looking into it. As usual, we’ll keep you all posted.
Happy Monday, everyone.