Meeting notes from July 23rd, 2019

A meeting was held with the proposed agenda.

The following is the recap of the meeting, you can read the meeting transcript in the slack archives (a Slack account is required).

Updates

We got positive and supportive feedback about the skip links (accessibilityAccessibility 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)). Even though it is simple to implement, the authors were confused. But we have a post explaining what they are and how to implement them.

Authors are starting to change the admin notices, according to the guidelines.

Promoting other themes from within popular themes isn’t allowed. Few authors were caught doing this and they changed it upon request. Ignoring the request to remove the promotions will result in theme suspension.

After meeting with the documentation team, @acalfieri was selected as a representative from the Theme review team to update the theme developer handbook.

A new version of Theme Sniffer and WPThemeReview coding standards was released.

In the past seven days:

  • 449 tickets were opened
  • 463 tickets were closed
  • 416 tickets were set live
  • 25 new Themes were set live
  • 391 Theme updates were set live
  • 10 more were approved but are waiting to be set live
  • 39 tickets were not-approved
  • 8 tickets were closed-newer-version-uploaded

An automatic way of notifying theme authors

It was proposed that all the theme authors get automatically subscribed to the TRT blog so that they can be made aware of the announcements when they are made.

Another proposal was to send mass emails to all theme authors to make sure their themes are compliant with the newest requirements. Those whose email bounced would get suspended or changed to reviewing status.

An agreement was not reached. It was agreed that the TRT will reach out to other teams so that we can see how they are dealing with this issue, and if this can be solved on a more global basis.

Looking for good examples of keyboard navigation

A team needs a good example for keyboard navigation, especially for menus, so that we can provide an example for theme authors, as this is going to be the next a11yAccessibility 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) measure that will be implemented.

Currently, we don’t have an agreement to what is the best way to move forward with this so any contribution is welcomed.

Open floor discussion

The feature packages project needs active contributors, so if you are interested in contributing to the TRT open-source projects check out the official TRT Github repository.

#meeting, #meeting-notes, #trt