Actually Turning on Heroku Dyno Access

Heroku got rid of the their free access a while back. I have one Node JS app on there that knits together a Slack form and WordPress site. I went to the trouble of upgrading to the bottom tier paid account with Heroku. It’s $5 a month. At that point, I thought I was done. […]

Read More… from Actually Turning on Heroku Dyno Access

H4 Widget Headers – Incorrect Nesting Fix

Nothing fancy here but I’m documenting it for the benefit of beginners or people who don’t do this at all. It seems most of the widgets in WordPress automatically give you h4 headers when you add them to the sidebar. That seems to go against the idea of nested and orderly headers that WCAG accessibility […]

Read More… from H4 Widget Headers – Incorrect Nesting Fix

Remove H1 Option from WordPress TinyMCE Editor

In terms of basic accessibility guidelines each page should have only one H1 element. In WordPress that’s usually built into the template and is usually the title of the post or page. I was thinking about that last night and wondered if we should just remove it as an option from the TinyMCE editor in […]

Read More… from Remove H1 Option from WordPress TinyMCE Editor

Javascript for Added Accessibility

Imagine you’ve got a legacy WordPress site built using one of those drag/drop themes. Now complicate it by having a chunk of content created by a non-standard javascript-based slider plugin. Continue to imagine you have a very, very short window of time to bring it up to WCAG2.0 accessibility standards.1 Child themes aren’t a viable […]

Read More… from Javascript for Added Accessibility