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).

Accessibility Team Meeting Agenda: January 4th

This is the proposed agenda for the accessibility team meeting on January 4, 2019 at 16:00 UTC. Due to the holidays season having just passed and little new progress at this point in the new year, the meeting will be mostly an open forum plus just a couple items to discuss:

  1. Discuss tickets https://core.trac.wordpress.org/ticket/34681 and https://core.trac.wordpress.org/ticket/43773
  2. Preliminar discussion on new year’s goals and Gutenberg phase 2 accessibility
  3. Open forum

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

Today’s accessibility bug scrub is cancelled.

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

Accessibility Team Meeting Notes: 12/14/2018

Meeting notes on Slack

WordPress 5.0.2 update

Note: WordPress 5.0.1 was released between the publication of the agenda and the meeting, so all references to 5.0.1 are assumed to refer to 5.0.2.

There were no significant updates pertaining accessibility plans in WordPress 5.0.2. There are some outstanding pull requests milestoned in the Gutenberg GitHub repository, but no definite progress.

Block Editor Documentation update

While the user documentation was finished prior to the release of WordPress 5.0, there was insufficient time to prepare it for publication. This is largely because of the need to edit and merge different sets of documentation in order to avoid redundancy.

With the upcoming holidays and associated slowdown, the public availability of the the documentation is still unknown.

Follow up from WordCamp US hackathon

Deque supported a hackathon to implement automated testing using Axe. The hackathon was well-received and effective, with several potential projects coming out of it.

Two big highlights are the beginnings of a11y tests added to the Gutenberg e2e test suite (https://github.com/WordPress/gutenberg/pull/12743) and work developed to add automated tests to Twenty Nineteen. The Twenty Nineteen tests are intended to become a base pattern for testing accessibility in themes generally.

The team created a GitHub project to track ideas and progress on these projects. WordPress automated accessibility testing project

Block editor strategic planning

Gutenberg Phase 2 is in very early stages. The only notable publication is a set of early mock-ups. While these shouldn’t be taken as definitive, they are indicators of what is being considered and proposed. However, we should all keep our eyes open to watch for any red flag issues, to try and avoid having problems crop up later.

Open Forum

Discussed raising the topic of the fixing the settings API again. This was last raised about 2 years ago, but was largely dropped as focus turned to the development of the new editor. It’s definitely a worthwhile project, but should be coordinated with any discussions concerning the long term goals for Gutenberg.

Repost: Takeaways from the WordCamp US Accessibility Hackathon, by Deque

Accessibility Team Meeting Agenda: December 14th

This is the proposed agenda for the accessibility team meeting on December 14, 2018 at 16:00 UTC

  1. WordPress 5.0.1 update
  2. Block Editor documentation update
  3. Follow-up from WordCamp US automated testing hackathon
  4. Block editor strategic plan, phase 2
  5. Open forum

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

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

Meeting Plans for December 2018

Since December incorporates a large number of holidays, WordCamp US,  and other team member travel, we’re planning on a number of changes to the meeting calendar for the rest of 2018.

We’ll have a meeting on December 7th, during WordCamp US, with no agenda. If anybody has questions on WordPress accessibility, accessibility in WordPress 5.0, or other topics to discuss, please show up and ask! Many regular team members will be in Nashville, but those of us not attending WordCamp US will do our best to answer your questions.

Schedule for December

  • December 7th: Bug Scrub: cancelled, Meeting: Open forum.
  • December 14th: Bug Scrub: cancelled, Meeting: normal. Agenda will be published in advance.
  • December 21st: All meetings cancelled.
  • December 28th: All meetings cancelled.

We’ll return to normally scheduled meetings on January 4th. If there are changes to this schedule, we’ll announce them here!

Accessibility Team Meeting Notes: November 30, 2018

Meeting transcript on Slack

Accessibility review for the 5.0 About page

Related ticket: #45178.

The About page looks good. The only concern is wether the Classic Editor informations should be shown when the plugin is installed but not activated.

Update on WPCampus Gutenberg accessibility audit

WPCampus is doing a fundraising to support an accessibility audit on Gutenberg. @bamadesigner is coordinating the initiative.

The audit is also supposed to provide actionable data. Most vendors offered to submit issues to Github and talk through the issues. The focus of the audit lies mostly on WCAG 2.0 and 2.1.

The selection committee is finalizing the selection of the vendor. They are in the process of sending follow up questions to the vendors in hopes of deciding late next week, or right after WordCamp US.

Any help and support to show the community how important this is would be nice.

Current progress on Gutenberg accessibility documentation

The document is still available in Google Docs. @abrightclearweb is reviewing the last details.

@chrisvanpatten and @dryanpress from the Docs team are working to implement the document on Gutenberg user documentation, since this guide is valuable for all users. They will ask the Accessibility team to review the Assistive technologies section.

Information about the WordCamp US Contributor Day accessibility team table / the hackathon

@rianrietveld is coordinating the initiative.

Developers from Deque Systems will join the accessibility team and WP core developers at the contributor day. They will work together to set up automated accessibility testing for WordPress.
The plan is to create a framework for testing and example tests for themes first (like Twenty Nineteen) and also generate a list of tests to write.

If there is time the goal is also to set up a framework for Gutenberg and core. @johnbillion and @joemcgill will help out during the contributor day.

Accessibility team meeting agenda: November 30th

This is the proposed agenda for the accessibility team meeting on November 30, 2018 at 16:00 UTC.

  • Accessibility review for the 5.0 About page
  • Update on WPCampus Gutenberg accessibility audit
  • Current progress on Gutenberg accessibility documentation
  • Information about the WordCamp US Contributor Day accessibility team table / the hackathon
  • Open floor and/or Discussion on a few tickets/issues, time permitting

If you have anything to propose to add to the agenda or specific items related to the above, then please leave a comment below. Either way, everyone is welcome to join!

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