Recap of February 14, 2017 Meeting

Slack log (requires Slack login to view. Set one up if you don’t have a Slack account).

Lesson Plan Updates

Copyediting Updates

  • @donkiely finished copyediting the template tour plan and is currently working on copyediting the WooCommerce plan
  • @skarjune finished copyediting the widget areas plan and it is ready for testing.

Testing Updates

From @melindahelt: We had 5 in attendance. No real theme developers, so I presented the same information but highlighted the user side of the application (selecting H1, H2 in editor vs coding into a theme).

Overall, the content was great, but it did feel a little basic for a “theme” lesson plan.

We did have a blind software developer attendee who came specifically to learn more about WordPress. We took advantage of having a subject matter expert and launched into a larger discussion/Q&A after the presentation, which was enjoyed by all.

One specific suggestion from the software developer was to include at least a mention of form accessibility. Even though this is just a taste of accessibility, that’s an area where things can go wrong very quickly and a form can be completely un-accessable to screen readers.

A second attendee sent me the following after our meeting:
1) A skip navigation link.
Once someone has screen read the navigation/menu a number of times they no longer need to hear it. Insert near the top of the html a link <a class=”screen-reader-tex­t skip-link” href=”#MainContent” title=”Skip to content”>Skip to content</a>, and then just before the content <a name=”maincontent” id=”maincontent”><­/a>
See http://webaim.org/techniques/skipnav/­ for a more detailed explanation.

2) Include an audio file of a screen reader reading an html page.
Perhaps done by having the page with an audio button, so the user can see what the screen reader is reading.
I was already thinking a little bit about suggestion #2. We talked about screen readers and the blind developer offered to do a demo for us some day. But, perhaps a video/audio clip showing a screen reader as it navigates through a page would be a helpful resource. I know there’s way to turn that on with some operating systems, but having something ready to go for instructors would be helpful.

  • Given this feedback, we talked about expanding the plan to have a separate plan for users and one for theme developers. We also talked about pushing this out into a full workshop and will talk about this on the blog and in next week’s meeting.

Other Things

  • @donkiely noticed that the Storefront theme used in the WooCommerce plan is not included in the style guide. We decided to change the style guide to say that Storefront is “approved” for WooCommerce lesson plans, but to make sure that people know that other themes can be used with WooCommerce. We also double checked that Storefront is GPL compliant.