Tag: accessibility

Fixes galore

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:

Blog sidebars

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.

Accessibility

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.


Staging server stabilized

As many of you are aware, the staging server has not been operating in an agreeable manner lately. Sites on test.publish experienced text alignment issues caused by sidebars even if sidebars weren’t present, which proved to be a major issue for content presentation.

I say were because this issue has been officially resolved. We received a fix from our vendor early this afternoon and relayed that fix from our development server to test.publish about an hour and a half ago. Many, many apologies for the inconvenience.

Also resolved

A few Events Manager accessibility issues were fixed last week. The monthly calendar views were not screen reader friendly (they were practically hostile), so I altered the Events Manager template to make us more compliant with state law than we were previously.

In a nutshell: << now has title text that says “previous month,” while >> says “next month.” These were coded into the calendar for navigation purposes, but they mean nothing to our visually-impaired visitors who use screen readers. Now they’ll know what those <a> tags do.

In addition, event dates now have title text that state the full date and the event name. Identifying the header cells in that monthly table view is proving to be problematic, so that accessibility quirk will have to wait. But for now, at least people using screen readers will know the monthly calendars contain links to event listings. These accessibility fixes were non-invasive and live in files apart from the theme, so I uploaded them to the live production server.

It’s okay. Sometimes none of this makes sense to me either.

Known major issues

  1. The search function returns results in full blog post format, even for pages. We have a ticket open with the vendor and hope to get this resolved shortly.
  2. When the blog is configured to show up on the home page, both the image slider and the default header image appear. Yeah, it’s not supposed to do that. Vendor is also working on this.
  3. No shortcode documentation. Yes, it’s coming. I’m planning to update/streamline Publish.uic.edu documentation in general, so shortcodes will be a part of that. Very soon.