Call for Team Rep Nomination – December 2022

As usual at this time of the year, we’re opening a call for (at least) one new 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 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.. I’ve been Team Rep for almost two-and-a-half years, which is way longer than usual, and now it’s really time for me to step down. It’s been an incredible journey, I learned a lot, and I’m really grateful to everyone who I got to know during my term.

To learn more about the role, you can check the article about what it means to be a Team Rep. Here are the main takeaways.

  • Team Rep is an administrative role, not a Lead one.
  • 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.

Traditionally, the Accessibility Team has had two Team Reps, which allows them to share responsibilities, divide tasks and cover each other when needed. Since the election of @joesimpsonjr, we switched to having three Team Reps (at least temporarily) to reduce the burden even more.

If you want to be considered for the role or know someone who would be a great fit, you have the opportunity to nominate yourself or others by adding a comment to this post. Remember that if someone proposes your name, but you don’t feel like accepting, you should feel more than free to say no: we will consider your nomination only if you agree.

Nominations review will happen during the meeting on Friday, December 16, 2022, at 16:00 UTC. We’ll decide if and how to manage the voting round, depending on the number of submissions. During the transition period, we will support the new Team Reps to be ready and operational as soon as they feel like it.

If you have questions about the Team Rep role or the nomination process, please feel free to reach out to @alexstine, @joesimpsonjr, or me (@ryokuhi) in the comments or on 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/., either with a Direct Message or in the #accessibility channel.

Props go to @alexstine and @joesimpsonjr for reviewing this post before publication.

#team-reps

Accessibility Team Meeting Agenda: December 2, 2022

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, December 2, 2022, 16:00 UTC.

  • Updates from working groups:
    • Design
    • Documentation
    • General
    • 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/
    • Media
    • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
    • Themes
  • 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 also be held on Friday, December 2, 2022, 15: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).

X-post: Meetup.com Accessibility Overlay Update

X-comment from +make.wordpress.org/community: Comment on Meetup.com Accessibility Overlay Update

Accessibility Team Meeting Agenda: November 18, 2022

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, November 18, 2022, 16:00 UTC.

  • Updates from working groups:
    • Design
    • Documentation
    • General
    • 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/
    • Media
    • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
    • Themes
  • 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 also be held on Friday, November 18, 2022, 15: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

X-post: Choosing accessible/contrasting dark theme colors for online workshops and tutorial videos

X-comment from +make.wordpress.org/training: Comment on Choosing accessible/contrasting dark theme colors for online workshops and tutorial videos

X-post: Multisite registration and activation pages have new HTML and CSS

X-comment from +make.wordpress.org/core: Comment on Multisite registration and activation pages have new HTML and CSS

Accessibility Team Meeting Notes: October 19, 2022

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 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/. channel and the meeting’s agenda here.

Updates from the working groups

Only groups that provided updates are shown below.

General

@ryokuhi reported that there are no tickets in need of special input from the team. During bug scrubs, the team is focusing on tickets milestoned for the next incumbent releases (6.0.4, 6.1, and 6.1.1) and on tickets Awaiting Review, to keep the queue under control. There are already 11 tickets milestoned for 6.2, which the team will start reviewing in the next few weeks.

By the time WordPress 6.1 will be released, 30 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets with the accessibility focus will have been fixed. @annezazu summarized in a post on the Make Core blog all accessibility improvements in WordPress 6.1.

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/

@annezazu shared for awareness a Pull Request to introduce a Browse Mode in the site editor.

@alexstine asked for some testing and feedback on the Pull Request to modify the shortcut which focuses the list view and on the Pull Request to improve region navigation. These are related to the Pull request to imporve regions and shortcuts in the editor.

Media

@joedolson slated two tickets from the WP Campus Gutenberg report for WordPress 6.2: one is about insufficient form semantics and the other is about insufficient labelling and inappropriate nesting of form controls. These tickets, together with the one about text inadvertently rendered by assistive technologies, will be all tackled as a group.

MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.

@joedolson shared that HelpHub, the part of the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ website which includes end-user documentation, is undergoing a redesign. It’s going to follow the same patterns used for other redesign, but it should get some accessibility attention in the near future. For more details, there’s a post about HelpHub redesign in the Make Documentation blog.

Open floor

@joedolson reminded about WordPress Accessibility Day, happening on November 2-3, 2022. Registration is open (at the time of the meeting, more than 500 people had already done it), sharing on social media is appreciated (the website is wpaccessibility.day), and volunteers are still needed, especially for the post-event video-editing work (please reach out to Isla Waite in the WordPress Accessibility Day Slack instance).

If you’ve been a (more or less) regular contributor to the Accessibility Team in the past year, please send a Direct Message to @joedolson, who will add the appropriate Accessibility Team member or contributor badge to your WordPress profile.

@joesimpsonjr shared the page with the newly added venue accessibility checklist page in the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Organizer Handbook, to tackle a few accessibility issues that impacted on the experience of a few participants during WordCamp US 2022.

#meeting-notes

X-post: WordPress 6.1 Accessibility Improvements

X-comment from +make.wordpress.org/core: Comment on WordPress 6.1 Accessibility Improvements

Accessibility Team Meeting Agenda: October 21, 2022

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, October 21, 2022, 16:00 UTC.

  • Updates from working groups:
    • Design
    • Documentation
    • General
    • 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/
    • Media
    • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
    • Themes
  • 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 also be held on Friday, October 21, 2022, 15: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

Accessibility Team Meeting Notes: October 7, 2022

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 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/. channel and find the meeting’s agenda here.

Gutenberg

@joedolson reported that the main update on all things is that we’re moving rapidly towards release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. on WP 6.1. @sabernhardt is working on developer notes for 6.1 changes.

Media

Joe reported that Media has started working on milestoning issues for 6.2. There’s a large backlog of issues (over 600), so we’re focused on finding simple fixes that have simply dropped off everybody’s radar.

On a more general note @alexstine asked if there anyone who wants to join these working groups or get more information?

Meta

@joedolson has provided extensive feedback on the Learn catalog and on the new Audio downloads section of openverse. The Learn changes I requested have already been fixed; I don’t have an update on the Audio downloads.

@zackkrida mentioned the Openverse side created a bunch of discrete GitHub issues from your suggestions but have yet to start work.

Open Floor

Joe made a general request that when we request working group updates, that the point person for each working group is specifically @ references in the request. Also, the point people are all listed in the Accessibility Handbook.

@sabernhardt shared that if you want to follow the dev note progress, there was an issue for the general Accessibility improvements dev note and the overall TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket is #56723. @annezazu has requested help.

** Thanks to everyone who attended, including first-timers interested in contributing to the accessibility of WordPress. We’ll see you for the next weekly bug scrub.