Accessibility Team Meeting Agenda: February 22nd

This is the proposed agenda for the weekly accessibility team meeting on Friday 22 February 2019 at 16:00.

  • Uniform Search Planning
  • Update on User Handbook
  • Prioritize Gutenberg A11y issues for WP 5.2
  • Search: Replace Placeholder with Label (https://github.com/WordPress/gutenberg/issues/13900)
  • Surface keyboard shortcuts visibly (https://github.com/WordPress/gutenberg/issues/13688)
  • Improve keyboard navigation between the block inspector and the block content (https://github.com/WordPress/gutenberg/issues/13663)
  • Open Forum

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

Accessibility Bug scrub will happen on Friday 22 February 2019 at 15:00

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

Accessibility Team Meeting Notes: February 15th

Meeting notes on Slack

Lack of Agendas & publishing of notes

  • We’ve struggled to get agendas and notes published recently, due to personal issues.
  • Will get all notes caught up with today (@joedolson)
  • Want to devise a better system for preparing agendas, that takes into account who will be present at any given meeting.
  • Last week’s meeting agenda contained numerous items where nobody present had relevant new information.
  • People anticipating attending a meeting should contact team reps if they have a topic they’d like to raise

Updates on Gutenberg user docs

  • Still no updates on Github or elsewhere
  • Mentioned in update chat with @chanthaboune; hope to get some information soon.
  • Should we publish the docs for assistive technology ourselves, or would that just create long-term confusion?

WordPress 5.2 Release schedule

  • Release schedule has been set for late April.
  • Time frame will not allow for Uniform Search
  • We believe it does give space for us to accomplish the 32 accessibility tickets currently slated for next release.
  • @joedolson will take ownership of the Uniform Search ticket so that we can begin planning, aiming to accomplish this in 5.3

Open Floor

  • From @afercia: note new proposal to systematically integrate animated micro-interactions in Gutenberg’s UI.
  • While we don’t have any fundamental problems with this in general, we should comment to ensure that the accessibility concerns with animations are raised.
  • From @afercia: Block specific responsive controls – very complicated and questionable semantics, particularly due to multiple controls that share the same label – labels should be unique. Topic will be discussed in design meeting, as well.

Accessibility Team Meeting Notes: February 8th

Meeting notes on Slack

Updates on WP 5.2 schedule and goal setting

  • No known schedule, nobody present has an update.
  • Discussed Uniform Search – what it is, what it would require, and what we need in order to have time for it.

Updates on Gutenberg user docs

  • Pinged @dryanpress for updates, no response.
  • Apparently no action on Github issue since January 15th.

Updates on Gutenberg phase II

  • Major discussions since last week’s meeting on the topic of navigating between blocks and sidebar (inspector)
  • Lots of promising ideas and engagement; working to reach a decision and implementation.
  • Work is developing on the Navigation menu block. Navigation menus are one of the more complicated and essential features, so accessibility should monitor this in an ongoing manner.

Open Floor

Discussed goals with @vossisboss to identify a good path for participation.

Post meeting follow-up:

@greatislander showed up shortly after the meeting with an update on automated testing:

  • Initial idea of packaging as a plug-in proved infeasible due to the size of the package.
  • Waiting on updates for the publication of axe-jest-puppetteer packages to NPM (anticipated around 5.1 release.)

Accessibility Team Meeting Notes: February 1st

Meeting notes on Slack

Gutenberg Phase 2 Widgets Screen

  • Goal is to start using blocks on the widgets screen; building out blocks to match existing widgets
  • Discussion of the general design, layout and accessibility of new page
  • Current design repurposes Gutenberg layout
  • Reproduces same issues with sidebar as in Gutenberg editor
  • Should we focus on improving the Sidebar UI or different design in Widgets?
  • Design should be consistent; so fixing the Sidebar UI is important
  • Many possible issues to address; top priority is topbar/inspector (Sidebar) navigation

Validate 5.2 Accessibility focused tickets scope / Triage update

Currently 30 accessibility tickets milestoned for 5.2. All of them have owners. Depending on 5.2 schedule, we may not be able to handle more.

5.2 schedule is currently an unknown factor.

Current goal: handle these 30 tickets for 5.2, revise based on schedule.
Ambition goal: work on #31818 (Uniform Search) if 5.2 schedule allows.

Accessibility Team Meeting Notes: January 25th

Apologies for the late report. We’re working on getting caught up!

Meeting notes on Slack

Individual availabilility in coming months

The majority of attendees have 1-4 hours per week available. We’d like to take some time to come up with better usage of time for those who have only very small amounts of availability, as anybody with only 1-2 hours a week is essentially only attending meetings.

Update on Automated Testing projects

  • Axe tests are running against Twenty Nineteen
  • Setup is clunky because the NPM packages aren’t published yet
  • Next steps:
    • Make it easier to install/run tests against any theme
    • Possible to install dependencies without requiring a clone of Gutenberg
    • Goal: installable as a plugin for easy installation
  • Joe Dolson will update the accessibility theme unit test data for use in theme testing. Needs to incorporate Gutenberg block output.

Update from research team/Gutenberg user testing

  • No one was present with information to report.

Verify team About page is up to date

  • Agreed that the info is essentially accurate, although we may want to make some changes anyway. Joe Dolson will review and report back.
  • Question whether the team has any materials on WP specific accessibility testing workflows; shared the accessibility-ready theme testing guidelines, which are already included on the About page.

Tickets for discussion:

  • https://meta.trac.wordpress.org/ticket/4091
  • https://core.trac.wordpress.org/ticket/38338

Discussion on 4091 (Slack)

Discussion on 38338 (Slack)

Accessibility Team Meeting Agenda: February 1st

This is the proposed agenda for the weekly accessibility team meeting on Friday 1 February 2019 at 16:00.

  1. Gutenberg phase 2 Widgets screen – GitHub Issue 13204
  2. Validate 5.2 Accessibility focused tickets scope / Triage update
  3. Open floor

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

Accessibility Bug scrub will happen on Friday 1 February 2019 at 15:00

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

Accessibility Team Meeting Agenda: January 25th

This is the proposed agenda for the weekly accessibility team meeting on Friday 25 January 2019 at 16:00

  1. Individual availability for the incoming months
  2. Update on automated testing projects
  3. Update from Research team/Gutenberg user testing process and communication
  4. Verify the team About page is up to date: https://wordpress.org/about/accessibility/
  5. Discuss tickets https://meta.trac.wordpress.org/ticket/4091 and https://core.trac.wordpress.org/ticket/38338
  6. Open floor

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

Accessibility Bug scrub will happen on Friday 25 January 2019 at 15:00

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

Accessibility Team Meeting Agenda: January 18th

This is the proposed agenda for the accessibility team meeting on Friday 18 January 2019 at 16:00

  1. Update on WP Campus Gutenberg audit
  2. Update on automated testing projects
  3. Future release(s) goals and discuss triage/milestoning to help a maximum of accessibility focused tickets to land in 5.1.x or 5.2
  4. Block Editor updates and planning
  5. Individual availability for the incoming months
  6. Open floor

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

Accessibility Bug scrub will happen on Friday 18 January 2019 at 15:00

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

Accessibility Team Meeting Notes: 1/11/2019

Meeting notes on Slack

Update on Block Editor Documentation

Dave Ryan gave an update on progress towards publishing the Block Editor user docs. The materials are almost finished being unified and outlined, and they hope to get the docs into HelpHub by the end of January.

Track progress on the User Docs

Dicussion on Gutenberg Phase 2 Planning

Continued discussing coordination planning for Gutenberg phase 2, trying to improve what didn’t work in phase 1. Andrea Fercia proposes a new team that takes responsibility for feature scoping that combines facets from accessibility, design, and internal architecture.

Not everybody agrees that a new team would help solve the problem.

Will continue discussion next week. This is expected to be a long-term assessment.

Individual & team goals for 2019

Joe Dolson asked for individual members to communicate their goals for 2019 in WordPress Accessibility in an attempt to keep track of projects and what people are doing.

Progress on automated testing

There’s an updated version of the scripts package; project is moving forward. Will communicate with @greatislander to eventually share information with the Theme Review team once the automated testing suite is sufficiently mature.

Plans for the Nimbus testing server

The team has had a dedicated server for some years used for running user tests. It has not been used significantly recently, so the team voted to decommission the server. Future tests can be prepped on an ad hoc basis.

Open Forum

Andrea Fercia requested feedback on a quirky JAWS/IE11 issue with fieldsets.

Accessibility Team Meeting Agenda: January 11th

This is the proposed agenda for the accessibility team meeting on January 11, 2019 at 16:00 UTC

  1. Update on Block editor documentation
  2. Continue preliminary discussion on new year’s goals and Gutenberg phase 2 planning
  3. Discuss Accessibility team organization: individual & team goals for 2019.
  4. Progress on automated testing projects
  5. Plans for the Nimbus testing server
  6. Open Forum

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

Accessibility Bug scrub will happen on January 11, 2019 at 15:00 UTC

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