These are the weekly notes for the accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.
Help testing the WordPress Auto-updates Feature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.
@audrasjb and @pbiron asked the team for help testing the Auto-updates Feature plugin. This is a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party that aims to provide automatic updates for plugins and themes feature as an opt-in feature.
You can find more information about the plugin on the plugin’s page and report any issues you come across to the plugin’s GitHub repository.
Statement on the use of Crowdcast for WP community events
We discussed the Community team’s consideration to use the Crowdcast streaming platform for online events. Knowing how inaccessible Crowdcast is, the Accessibility team wants to help the Community team find better alternatives. @joedolson wrote this post with recommendations for alternative setups and suggestions to make online events more accessible.
Open Floor
Team meeting time change due to DST
@ryokuhi reminded the team that we haven’t made a decision about moving our meeting time to adjust to DST. This is a change we’ve done in the past, and that other teams have done as well.
The consensus from team members present was that it was OK to move the meeting time, but we’d like to give folks who could not attend the chance to have their say.
Please let us know in the comments of this post if you are in favor of or against moving the meeting time an hour earlier to adapt to DST.
We will be making a final decision during our meeting next week.
+make.wordpress.org/core/
#meeting-notes
