bookmark
· · to read
The WordPress Twenty Sixteen theme: Good, Bad or Ugly? - A Bright Clear Web (A Bright Clear Web)
My review of Twenty Sixteen, the new theme from the WordPress team. Learn about its features, its pros and cons and who it's best suited for.

This is a really good post to use as a guide if you’re a blind person trying to work with the Twentysixteen WordPress default theme. It walks through the different steps you can take to customize the theme for your site, without using code. It also gives some detail about the various color schemes that come packaged with the theme.

reply
· · to read

Now that I’m familiarizing myself with this theme, (I tested it before it was bundled into core as part of the WordPress Accessibility Team but haven’t given it much of a look since), I’m seeing that we do have two menu locations. Getting back to my comments re: including the link always in the post, I looked at your reply to my tweet on your site and noticed that you included the tweet. For some reason I was thinking the original link would be pulled in even though it’s not displayed in the tweet, but I’m just going to blame that on not enough caffeine. 🙂 So I will go ahead and change that setting. I also need to add and/or rearrange some categories on this site while I’m at it.

note
· · to read

#ID24, (otherwise known as Inclusive Design 24), is happening again next week, and the sensible part of my brain is saying “No, really, you shouldn’t stay awake for twenty-four hours and it doesn’t matter how good the talks are going to be because you are not in your twenties anymore”, and the rest of my brain is saying “This schedule is awesome and it will be so much fun to participate on the social medias with everybody and bring some IndieWeb goodness and then shove it all to your Facebook page”. I think I know which part is going to end up winning. I need to take Noter Live for a spin because I haven’t done so yet on the new computer, because I haven’t done that yet and live tweeting the whole conference a couple of years ago was fun.

read
· · to read
5th Annual Hacktoberfest Kicks Off Today, Updated Rules Require 5 Pull Requests to Earn a T-shirt
DigitalOcean, along with GitHub and new partner Twilio, are sponsoring the 5th annual Hacktoberfest. The event was created to encourage participants to make meaningful contributions to open source …

I’m wondering if @DictationBridge has any issues that need pull requests. I’m also wondering if pull requests on docs count. I should check the rules because a limited edition Hacktoberfest t-shirt would be nice to add to the collection.

note
· · to read

I can remember a time when the #WordPress customizer was off limits if you used a screen reader. I’m playing with it now and even though I know there’s more work to do I’m so proud to see how far it’s come. And no, I’m not praising my own work, I’ve had nothing to do with it.

watch

· · to read

This Is For Everyone is a talk I will definitely be revisiting, along with all the other talks given so far as part of this year’s Inclusive Design 24, because it’s jam-packed with information, including some very useful statistics. It’s a really good overview of accessibility at a high level, and is a great way to kick off a conference whose talks go into quite a bit of detail about how to make the web more accessible, complete with examples. Hint Indieweb folks, given your love of POSH, (plain old semantic HTML for the rest), you’re already on the right track to an accessible web, because semantic HTML is the foundation of everything accessible.

note
· · to read

Dear #indieweb I am going to do my very best to not flood Indienews with #ID24 web-related talks but you have no idea how difficult this is going to be. We’re only four hours into a twenty-four hour conference and there’s been a ton of really, really good web-related stuff here.

note
· · to read

Blind people, I am not having your excuses for why you can’t make the things you create accessible to all disability groups today, especially if you constantly flag accessibility fails on the part of others. If @BlindBargains can manage it, so can you. If you create a podcast, then it needs transcription. If you run a website, it needs skiplinks. It needs images with alternative text. These things are part of accessibility in particular and inclusive design in general, and you cannot complain about the accessibility fails of others, (hashtag a11yFail), and then skip the parts you don’t want or that are too hard or too inconvenient.