Enabling Google Sheets for Jetpack Forms on Accessibility Team Make site

[alh0319]

The Accessibility team is refining the process for theme accessibility-ready reviews so that it is more scalable and easier for theme developers to request a review at any time.

If a new theme that has not yet been published adds the accessibility-ready tag, it is added to a ​list of themes that need an accessibility-ready review in Trac. This process works well for themes that are not yet approved; however, it does not work for already live themes, as we don't want them to add the accessibility-ready tag (and show in search as accessibility-ready) before they are approved to use it.

It is not possible to open tickets directly in the Themes Trac.

Because of these limitations, @joedolson has created a ​contact form so theme developers can request an accessibility-ready review. When this form submits, it emails to one person, and entries can be viewed in the admin for the Accessibility Make site by a limited number of people.

In an ideal world, this form would add the accessibility-ready keyword to the existing Trac ticket for the theme, or open a new ticket to request the review, so requests can be viewed and managed in Trac.

Since the form is a JetPack form, that does not seem possible. However, I see a way to connect Google Sheets to a form. I am wondering if we can get the connection enabled or "allowed" so I can set up a Google sheet for tracking theme accessibility ready review requests.

If this is not possible, are there any other ideas about how developers of approved themes can request the review?

Thanks.

[alh0319]

@otto or @dd32, are you the people to ask about this?

[dd32]

However, I see a way to connect Google Sheets to a form. I am wondering if we can get the connection enabled or "allowed" so I can set up a Google sheet for tracking theme accessibility ready review requests.

I think the person setting it up just needs to be an Admin on the site. Joe is, you're not.

---

Is this flow the correct workflow for this tag though?

This doesn't prevent themes ignoring y'all and just using the tag anyway.

It seems like the ideal process would be something like:

New theme:

• Submit, goes through regular Theme Review process, goes live, without accessibility-ready tag, triggers workflow

Updated theme adding tag:

• Submit update, goes live, without the accessibility-ready tag, triggers workflow

Workflow:

• Pings Slack / emails team, with a link to the theme.
• Discussion can take place with the author on the most recent Themes ticket.
• If the author needs to make an update, they can submit a new version with the fixes, new ping goes out, etc.
• Once someone approves it (Either themes wp-admin, special link in email or make/accessibility admin), tag is added, and future updates can use it.

[alh0319]

I think the person setting it up just needs to be an Admin on the site. Joe is, you're not.

@joedolson are you able to connect a Google Sheet to that form?

This doesn't prevent themes ignoring y'all and just using the tag anyway.

Yes, this is a significant downside of the current process. We have a ticket view that shows us all themes with the tag that have recently been updated and the theme would show there. If someone from the team manually watches it, they can catch those themes that way.

This actually brings me back to this ticket: 7715. In an ideal world, the accessibility-ready status and search filter would not be handled by a theme tag and would, instead, be handled by meta on themes that the themes and accessibility team can edit themselves or through the review process.

Would you be able to help with that, @dd32?

[muddassirnasim]

This came up during the Accessibility team meeting.

Design updates to WordPress core are currently in progress and will need accessibility review, especially given the scope of the CSS changes and the size of the admin interface. The basics are expected to be fine, but there may be many details to check.

Additional review and feedback would be appreciated as this work moves forward.