Category Archives: Working Group

Enrique Sánchez 9:46 pm on July 6, 2020
Tags:   

Accessibility Team Meeting Notes: July 3, 2020

These are the weekly notes for the 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) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Changes to the “Transform to” button and blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. “movers” in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/

The team discussed the newly updated controls in the block toolbar for the ‘Transform to’ and ‘movers’ actions. The new design proposes quite a few substantial changes and this has raised accessibility concerns within the team.

@afercia noted a few problems, such as a missing ‘grab area’ and the ‘hand’ mouse pointer now being used for interactive controls. Other team members also raised questions about the obviousness of this new user interface.

A summary of the team’s feedback has been posted on the issue for follow up.

Add a ‘description’ property to block patterns

We also discussed this Gutenberg issue that proposes to add a ‘description’ property to the newly added feature of Block Patterns.

The team raised arguments around the requirement of such a property, and the pros and cons behind such a rule. We decided that the property should be labeled as required while not being enforced with any checks.

With this feedback, @poena proceeded to finish and merge the corresponding PR. 🎉

#meeting-notes

Enrique Sánchez 5:44 pm on July 2, 2020
Tags:   

Accessibility Team Meeting Agenda: July 3, 2020

This is the proposed agenda for the weekly 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) Team meeting on Friday July 3, 2020 at 15:00 UTC.

  • Discuss changes to the “Transform to” and blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. “movers” in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Discuss this Gutenberg issue that proposes to add a ‘description’ property to block patterns
  • Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, July 3, 2020, at 14:00 UTC. Also please be aware that we are hosting additional bug scrubs focused on the 5.5 release.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Enrique Sánchez 3:35 pm on June 25, 2020
Tags:   

Accessibility Team Meeting Agenda: June 26, 2020

This is the proposed agenda for the weekly 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) Team meeting on Friday, June 26, 2020, at 15:00 UTC.

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, June 26, 2020, at 14:00 UTC. Also please be aware that we are hosting additional bug scrubs focused on the 5.5 release.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Enrique Sánchez 9:39 pm on June 19, 2020
Tags:   

Accessibility Team Meeting Notes: June 19, 2020

These are the weekly notes for the 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) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

New Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. 🎉

After accepting nominations, I’m happy to inform that @ryokuhi has been selected as our new Team Rep. Together, we’ll be sharing Team Rep responsibilities and helping the Accessibility team make WordPress better for everyone.

Discussion of Remove ‘Error:’ prefixes from error notices as they’re redundant

We discussed Remove ‘Error:’ prefixes from error notices as they’re redundant, a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket that is proposing remove type prefixes to error messages in wp-admin.

There are various opinions around whether type prefixes, such as ‘Error’, ‘Warning’, ‘Success’, etc. are needed, or are simply redundant on wp-admin messages and notifications.

The discussion was very constructive and informative, I encourage those interested to read it in full.

We agreed that uniformity was important and that this topic is closely related to the work happening on the WP Notify feature. For now, we decided to revert the removal of the ‘Error’ prefix and gather more feedback.

#meeting-notes

Enrique Sánchez 8:34 pm on June 18, 2020
Tags:   

Accessibility Team Meeting Agenda: June 19, 2020

This is the proposed agenda for the weekly 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) Team meeting on Friday, June 19, 2020, at 15:00 UTC.

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, June 19, 2020, at 14:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Enrique Sánchez 9:27 pm on June 16, 2020
Tags:   

Accessibility Team Meeting Notes: June 12, 2020

These are the weekly notes for the 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) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

New Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. nominations

The team has published a call for Team Rep nominations. We will be accepting submissions this week and will proceed with a vote during our next team meeting.

Next steps on documenting GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/’s accessibility features

The team will follow up on this task by creating a list of all the accessibility features in Gutenberg that need documenting. Once we have this list, we’ll start thinking about how we’d like to document these and where and how these will be communicated to users.

Call for testing: Removal of Infinite Scrolling from the media grid

As reported by @afercia, #50105: Remove infinite scrolling behavior from the Media grid is ready for accessibility testing. In particular, feedback is needed on focus management when new attachments are added to the media grid after users click “Load more”.

Help testing and providing feedback is appreciated on the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket linked above.

Alternate views for WP List Tables

The team also discussed #49715: Alternate views for WP List Tables as some decisions need to be made.

The conversation centered around having three different views for tables, something like compact, default, and expanded, and the possibility for a global setting to allow the user to choose which view they prefer by default.

Report on the progress made during WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

Team members that facilitated during WCEU Contributor Day reported on the progress made during the event.

Along with attendees, the group worked on a ticket for the Plugins & Themes Auto-update feature and also worked on reporting an issue and submitting a pull request in the Gutenberg GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository.

#meeting-notes

Enrique Sánchez 4:11 pm on June 12, 2020  

Team Rep nominations

The 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) team is officially accepting new Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. nominations. As announced in previous team meetings, @audrasjb will be stepping down as he now will be focusing more of his time on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team.

We’ll continue with the tradition of having two Team Reps on the team, so I (@nrqsnchz) will continue on the role, and this new person will be sharing responsibilities with me.

If you’d like to learn more about what it means to be a Team Rep, this article goes into detail about the responsibilities. But in summary:

Team Rep is a leadership role that is mostly administrative in nature; it is not a Lead role. Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities. Someone who is a leader in a team can lead whether they are doing the team rep job or not.

If you would like to be considered for the role or would like to nominate someone, please add a comment below. We’ll be reviewing nominations during our team meeting next week. Depending on the number of submissions, we’ll define if we’ll need to hold a round of voting.

And lastly, on behalf of the team, I’d like to thank @audrasjb for all the help and contributions provided so far. We are looking forward to continue working with you.

Enrique Sánchez 9:23 pm on June 11, 2020
Tags:   

Accessibility Team Meeting Agenda: June 12, 2020

This is the proposed agenda for the weekly 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) Team meeting on Friday, June 12, at 15:00 UTC.

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, June 12, at 14:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Enrique Sánchez 6:27 pm on June 8, 2020
Tags:   

Accessibility Team Meeting Notes: June 5, 2020

These are the weekly notes for the 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) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Documentation of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/’s accessibility features

We continued the discussion about documenting the features present in Gutenberg that help make the editor more accessible and the best way to bring awareness to them.

We agreed that this documentation should be easy to find and not buried or hidden under a menu. Some of the features we think would make part of this documentation are:

  • Edit and select modes
  • BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. and block breadcrumbs
  • Top toolbar
  • Spotlight mode

We agreed to continue this discussion next meeting.

Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. nominations

As @audrasjb steps down from being a team rep to focus more of this time on the Core team, the team is planning to launch new team rep nominations during the next team meeting. @nrqsnchz will continue to be team rep and the new person to fill JB’s place will share tasks and responsibilities with him.

Open floor

@afercia reminded everyone of the list of tickets that need help from the Editor and Media teams. @audrasjb will be reaching out to those teams.

Andrea also asked if there has been any progress or updates on the PR for addressing accessibility concerns of WritingFlow. There’s been consensus around creating a setting to turn this feature on and off and those involved are currently discussing how to call this setting in the PR.

#meeting-notes

Enrique Sánchez 11:33 pm on June 4, 2020
Tags:   

Accessibility Team Meeting Agenda: June 5, 2020

This is the proposed agenda for the weekly 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) Team meeting on Friday, June 5, 2020, at 15:00 UTC.

  • Continue the discussion from last week on the documentation of the accessibility features in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Start nominations for a new team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.
  • Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, June 5, 2020, at 14:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda