Accessibility Meeting Notes for 19 April 2019

Meeting transcript on Slack

Welcomed new contributors

Welcomed and got introductions from Enrique Sanchez & @nataliemac; gave them an introduction to the Accessibility Team purview and operations.

1) WordPress 5.2 Accessibility Team work statement

@joedolson didn’t know what the intent behind this agenda item was, so tabled for next week.

2) WordPress 5.3 Goals

Reviewed goals for 5.3. @nataliemac will review & update spreadsheet of priorities. Enrique Sanchez volunteered to help with planning on Uniform Search.

3) Update on Automated Testing

@gziolo has made a pull request to incorporate Axe testing into Gutenberg e2e suite. Pending review.

4) Update on User Handbook

Discussed whether we should publish @abrightclearweb‘s documentation into our Handbook, since it’s now mid April and we still have no updates on user documentation.

Laid out scope of what this would take, which is significant.

@karmatosed will follow-up to try and get something moving next week. It would be preferable to not have to reduplicate this work, but we feel strongly that it needs to be published.

5) Continuing Discussion: W3C alt decision tree

Tabled due to shortage of time.

6) Update on Accessibility Team/Contributors Badges

All badges have been updated per discussion last week.

Accessibility meeting agenda for 19 April 2019

This is the proposed agenda for the weekly accessibility team meeting on Friday 19 April 2019 at 15:00

  • WordPress 5.2 Accessibility Team work statement
  • WordPress 5.3 goals
  • Update on Automated testing
  • Update on User Handbook
  • Continuing discussion: strategies for use of the W3C alt decision tree in translations.
  • Update on Accessibility Team/Contributors badges assignment
  • Open Floor

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 19 April 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

This meeting is held in the #accessibility channel in the Making WordPress Slack (requires registration).

X-post: The Get Involved table at WCEU 2019

X-comment from +make.wordpress.org/community: Comment on The Get Involved table at WCEU 2019

Accessibility Meeting Notes for 12 April 2019

Continue discussion on WP.org profile badges

Reviewed criteria for Team/Contributor badges for the team:

1) Team badges:

  • Past team leads
  • Regular participation in meetings (at least once per month)
  • Leadership role
  • Writing documentation
  • Leading code contributions (project management for major tasks, significant code written, etc.)

2) Contributor Badge:

  • Occasional meeting participation
  • Code contributions on Github or Trac (bug reporting, testing, and patching)
  • Assisting in Accessibility Support forum
  • Performing A11y Theme Reviews

3) Update cycle

  • Badge assignments will be reviewed in mid April and mid October each year, and will be based on participation during the prior 6 months.

Additionally, we reviewed the badge assignments for the Accessibility team and contributors throughout the project. We believe that this is now up to date according to the above criteria.

If you’ve contributed to WordPress Accessibility and you do not have a badge assigned, please comment below and let us know! We assembled a lot of this from memory and searching through trackers, meta activity, and slack conversations. It was definitely not an infallible process.

If the reason you don’t have an Accessibility badge is because your contribution isn’t covered by the above criteria, please let us know that, as well! The criteria are open to changes.

Open Floor

@greatislander Wanted to address an small accessibility improvement that we could add to the Settings API immediately, since getting the complete API revamp is stalled at the moment. Team agreed that adding role="presentation" to make the settings tables presentational is probably a good choice, though we’ll want to test it.

Note

We got through only one item on our scheduled agenda for this week, since we spent most of the team getting our badges up to date. We’ve committed to a 6 month review cycle for badges, so that we never spend that much time on it again…

The rest of this week’s agenda will be addressed next week.

Accessibility meeting agenda for 12 April 2019

This is the proposed agenda for the weekly accessibility team meeting on Friday, April 12, 2019 at 15:00.

  • Continue discussion on WP.org profile badges
  • Update on Automated testing
  • Update on User Handbook
  • Continuing discussion: strategies for use of the W3C alt decision tree in translations.
  • Uniform Search
  • Open Floor

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday, April 12, 2019 at 14:00.

This meeting is held in the #accessibility channel in the Making WordPress Slack (requires registration).

Accessibility Team Meeting Notes for 4/5/2019

Meeting notes on Slack

Profile badges

  • We have not been keeping up to date on these for some time.
  • We don’t have a consistent plan for granting badges.
  • @audrasjb will create a spreadsheet to share among the team where we will document badges
  • @joedolson will figure out who needs to be notified about new badge assignments
  • The team will jointly figure out who needs to be awarded badges.
  • Tentative policy agreed on:

1) Team badges:
– Regular participation in meetings
– Leadership role
– Writing documentation
– Leading code contributions

2) Contributor Badge:
– Code contributions on Github or Trac
– Assisting in Accessibilty Support forum
– Performing A11y Theme Reviews

Update on Automated Testing

  • @greatislander has been in communication about getting added to WP Rig
  • Some feedback on documentation improvements
  • No response from Underscores yet

Block Editor User Handbook update

  • No new information.

Should we copy the alt text decision tree for translations?

  • @audrasjb feels strongly that we should make our own copy and provide all translations in handbook/HelpHub.
  • Reviewed licensing for W3C docs, which will permit this as long as we credit them appropriately.
  • @audrasjb volunteered to take on copying the tree over.
  • Will finalize decision in next meeting; want @afercia to be present for the final conversation.

Uniform Search

  • No progress made. Nobody has yet stepped up to share the process of figuring out what this will entail.

Open Floor

@luke_pettway reported that the Navigation block is going into development very soon. His interactions with the team working on that exposed a number of accessibility blind spots, so hopefully the development process for this will work well to iterate through those issues.

See this comment on the Navigation menu block for revised information on the proposal.

See the prototype for more information on proposed interactions.

Luke will write up notes and post to the channel for comments; he wants some second opinions in some areas.

Accessibility meeting agenda for 5 April 2019

This is the proposed agenda for the weekly accessibility team meeting on Friday, April 5, 2019 at 15:00.

Please note the change of time for the meeting; this may or may not impact you depending on how and when your timezone handles daylight saving time.

  • Discuss how we handle WP.org profile badges for the team.
  • Update on Automated testing
  • Update on User Handbook
  • Continuing discussion: strategies for use of the W3C alt decision tree in translations.
  • Uniform Search
  • Open Floor

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub on Friday, April 5, 2019 at 14:00 is cancelled for this week.

This meeting is held in the #accessibility channel in the Making WordPress Slack (requires registration).

X-post: Weekly Digest | Week 13

X-comment from +make.wordpress.org/updates: Comment on Weekly Digest | Week 13

Accessibility team meeting notes for 3/29/2019

Meeting notes on Slack

Update on Automated testing

  • Some Twitter buzz and stars on GitHub repo, but no testing comments yet.
  • Discussed best strategies for moving forward. Will work on integrating with common WordPress theme dev resources such as Underscores, WP CLI, WPRig, etc.

User Handbook

  • Dave Ryan responded and reported that he expected to be submitting a draft to HelpHub this week.

Use of tables in Health Check

  • Health check plugin makes extensive use of tables for showing site information. Discussed whether these are data tables (and need headings) or presentational (and need role=presentational)
  • Decided that due to the mixed content of both columns, this was best as a presentational table, but that there is no particularly good other semantic choice for display of this information.

Should we copy the alt text decision tree for translations?

  • Core media views & Gutenberg contain links to the W3C alt decision tree. That document is only available in English.
  • We need to determine a way to provide access to this data in translation.
  • Probably need to communicate with documentation and polyglots to figure out the path for this.

Meeting time change

  • Due to daylight saving time change in Europe, we voted to change the meeting time to 15:00 UTC.
  • Meeting time change effective 5 April, 2019.
  • Meeting time has been updated on make/accessibility and on the master list of team meetings.

Accessibility meeting agenda for 3/29/2019

This is the proposed agenda for the weekly accessibility team meeting on Friday, March 29, 2019 at 16:00.

  • Update on Automated testing
  • Update on User Handbook
  • Use of tables in Site Health screens
  • Should we copy the alt decision tree into the Handbook for translation?
  • Open Floor

If you have any additional topics to propose, please comment below.

Accessibility Bug scrub will happen on Friday, March 29, 2019 at 15:00.

This meeting is held in the #accessibility channel in the Making WordPress Slack (requires registration).