Tutorial Development Checklist

• Tutorial created and announced to the team for Q/A review
• Tutorial reviewed and ready to publish
• Tutorial submitted and published to WPTV
• Tutorial published on WPTV
• Tutorial captioned
• Tutorial created on Learn.WordPress.org
• Tutorial post reviewed for grammar, spelling, etc.
• Tutorial published on Learn.WordPress.org
• Tutorial announced to Marketing Team for promotion

Hi @westnz ,
The draft of this script is also ready for review in this doc . 🥳

Looking forward to your feedback!

I have sent a request to access the doc 😉

Sorry, forgot to tick the box—done :-)

Reviewed 😃
Great work @ironnysh

Hi @jonathanbossenger , now that the rewrite is done (thank you, @westnz ! 🙌), I wanted to make sure that this script would work for the developer audience, too. Could you take a look?

Hi @ironnysh just to make sure I understand, do you mean, "will this make sense to developers" or do you mean "should we use this in the developer learning pathway for #2188 "

Hi @jonathanbossenger , option 2 😀

As discussed here :

What if we stick to the "traditional" division of Developer vs. User used in the Learning Pathways? This way, both audiences share the same intro , but the practical part of the tutorial changes:

User

• What is accessibility, and why is it important? (this issue)
• Tools to test your content for accessibility. ( Tutorial: Testing your content for accessibility  #2201 )

Developer/designer

• What is accessibility, and why is it important? (this issue)
• Best practices when developing/designing an accessible theme. ( To-Do Best practices for developing an accessible theme  #2188 )
• Tools to test your theme for accessibility. ( Tutorial: Testing your content for accessibility  #2201 )

@ironnysh Gotcha, thanks for clarifying (my memory fails me form time to time).

Yes, I think this will be perfect for the theme developer module on accessibility.

Coolio! :-)
I'll get to work on best practices for developers/designers, and incorporate the “tools to test” in there as well.

Sounds great, I look forward to reading it.

Hi team, I would like to be involved in recording this video

Thanks @ervanyuff
I will be in contact once the script and voice recording is finished. 👍

The recording has been completed + shared.

Hey @ervanyuff
When do you think the recording for this lesson will be done? 😀

Hi @westnz This video might be finished earliest by the end of the next week. I'll update if I can finish sooner 🙏

Sounds good. Thank you for the update. 👍

Hi team, here is what is accessibility, and why is it important video. Please feel free to provide any feedback. Thank you 🙏

Fantastic video editing skills @ervanyuff 🌟

Review:

1. I would add a question mark to the slide at 00:09?
2. Can the text start sooner to match the narration in three places: 1) 1:22, 2) 1:33, 3) 3:04. The narration begins slightly before the text appears.
3. The blurry example is not being displayed, 5:29 -5:35
4. I suggest using a red or yellow color for the annotation/rectangles to help guide the reader's eye, 6:00

Well done on the video edit @ervanyuff , agree with @westnz on the feedback.

hi all, currently I am at the contributor day at WCEU Torino and this is the first tutorial I have reviews, hope my feedback is useful.

Tutorial/Lessons Review Checklist

Please tick all items you've confirmed:

• Learning outcomes/objectives are clear.
• Technical concepts introduced in the content are accurate.
• The speed of demonstrations are easy to follow.
• The narration audio matches what is shown visually.
• Spelling and grammar are correct.
• Sound quality is consistent throughout the video.
• Brand Usage Guidelines and Promotional Guidelines are being followed.
• Media assets are all in the public domain ( CC0 ).

Here are two comments:
video time 2.26 talking about accessibility is hard
the image right is not clear to me, should this represent baking? I suggest finding a more distinct image.

Video time 4.11 table with accessibilities issues
maybe adding a title to the table such us issues would be helpful.

Cinzia

Tutorial/Lessons Review Checklist

Please tick all items you've confirmed:

• Learning outcomes/objectives are clear.
• Technical concepts introduced in the content are accurate.
• The speed of demonstrations are easy to follow.
• The narration audio matches what is shown visually.
• Spelling and grammar are correct.
• Sound quality is consistent throughout the video.
• Brand Usage Guidelines and Promotional Guidelines are being followed.
• Media assets are all in the public domain ( CC0 ).

Leave an additional comment below with feedback.

1. Add Wordpress.org logo on title slide of video.
2. Great video - Ervan!

Hi team! Thank you for all the feedback @westnz @digitalchild @moltilearn @hazeldrio

@moltilearn 2.26 is this icon is good enough?

@hazeldrio Did you mean by this part?

I think the WordPress logo is already there. Do we need to add more? If so, maybe it can be put on the right side like this?

@ervanyuff Not a big deal but I think this is the new thumbnail graphic. So the call out was that the title slide was missing the full WP logo (see example below).

Hey @hazeldrio and @ervanyuff
There are a few thumbnail designs to choose from. Both of these are from the list of available ones: https://make.wordpress.org/training/2024/06/10/thumbnail-creation-project/ 😃

Hi team! here is the updated video. Please let me know if there is anything missing 🙏

//published