Tag Archives: meeting notes

Nasim Miah 5:44 pm on November 18, 2025
Tags: , meeting notes   

Accessibility Team Meeting Notes: Nov 13, 2025

On Thursday, November 13, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by Nasim Miah. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Updates from working groups

Documentation:

@joedolson shared a documentation update on behalf of @rianrietveld:

  • wpaccessibility.org now has a proper search function.
  • Several documentation updates about webforms are under review and expected to be published soon.
  • The new “Debunking 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) myths” page is available here: https://wpaccessibility.org/docs/start/myths/overlays/
  • Rian is also working on implementing the new design, after which the WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. EM-audit can begin.

A key reminder: contributors should contact @rianrietveld before starting work on any documentation section, and should not submit PRs for issues that already have an assigned owner.
@joedolson also noted ongoing problems with PRs containing AI-written documentation, which currently does not meet quality standards.

On the topic of the accessibility profile badge, @joedolson suggested that contributors working on accessibility documentation should be eligible.

  • Nasim Miah agreed, noting it encourages consistent, quality contributions.
  • Both agreed badge criteria may need clearer standards, aligned with other teams.
  • Increased Profile Associations requests were noted; Nasim Miah also observed this trend.
  • @joedolson said smaller contributions are still considered, but must meet reasonable quality.

General

@joedolson reported that with the release of 6.9 RC1, work is now shifting toward preparing for 7.0. This week’s bug scrub focused on new tickets on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. that were awaiting review, and most of those have been milestoned for the 7.0 release.

Next week, the focus will shift to older tickets, prioritizing ones that need attention.

In this release, 33 accessibility issues were resolved on Trac and 43 issues were resolved on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/.

Gutenberg

@joedolson shared that all new 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/ features should continue to be tested during the 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. phase, and accessibility bugs should be resolved before release.
Features that didn’t make it into 6.9 — such as Tabs 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., Icons Block, and Template Management are likely candidates for 7.0.

He also noted that major items requiring attention are listed in the Release Progress document:
https://make.wordpress.org/accessibility/current-release-progress/

🗓️ Next Meeting Schedule

@joedolson noted that the next meeting is currently set for November 27th, which falls during the US Thanksgiving holiday, meaning many contributors will be unable to attend. He proposed skipping the meeting or shifting it by a week.

Nasim Miah agreed, saying it makes sense to skip the November 27th meeting and resume on December 4th instead.

@joedolson confirmed he will update the calendar and ensure the change is clearly noted in the meeting minutes.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @joedolson for the pre-publish review.

#accessibility, #meeting-notes

Krupa Nanda 7:54 am on November 4, 2025
Tags: , meeting notes   

Accessibility Team Meeting Notes: October 30, 2025

On Thursday, October 30, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by @krupajnanda. You can read the full transcript or see the meeting agenda.

Updates from working groups

Documentation Updates

  • Publishing of new documentation on wpaccessibility.org has started.
  • Three new topics are now available:
    1. Frontend code: Accessible name
    2. Web forms: Input field and form label
    3. Web forms: Input field and description
  • Site maintenance: 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) of wpaccessibility.org will be fixed by Joe and audited soon.
  • Outreach: @rianrietveld presented the project at WordPress Meetups in Amsterdam and Utrecht. Next presentation scheduled for November 27 at 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. Netherlands.

How others can help:

  • Read and share feedback on the new content at wpaccessibility.org.
  • Pages about web forms need examples of how plugins handle accessibility.
    • Contributors from WordPress form plugins are invited to share input via the contact page.
  • Extended update available at WP A11y Docs update October 2025.
  • Volunteers are needed to review new documentation and take ownership of unresolved issues.

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/ Updates

  • WordPress 6.9:
    • Most changes have been merged into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
    • Some remaining bug fixes will be backported.
    • Notable updates are still in progress for the Notes feature.
    • Joe will begin preparing the Accessibility Improvements List in the next couple of weeks for clearer tracking.

Themes Updates

  • @joedolson connected with @alh0319 to coordinate on finalizing the updated accessibility-ready guidelines.
  • Work is planned for late November, with the goal of having updates ready for broader review in December or January.
  • A special meeting with the Themes team will be scheduled once the guidelines are ready.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

#accessibility, #meeting-notes

Nasim Miah 3:30 pm on October 21, 2025
Tags: , meeting notes   

Accessibility Team Meeting Notes: October 16, 2025

On Thursday, October 16, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by @muddassirnasim. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Bug Scrub Schedule for WordPress 6.9

Updates from working groups

Design

No Update

Documentation: @rianrietveld reported that Work on the WP Knowledge Base

  • Rian started with (re)writing content about accessible web forms. @GaryJones and @Annelies Verhelst help with reviews. Nothing published yet, all in review at the moment.
  • Vyshnavi Kurapati works on improving the search functionality of the website
  • Jeffrey Lauwers will look at the design of the website, to give it a more professional and usable look and feel.

MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. handbook: @aialvi works on the migration of the current handbook to a new GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/ repo 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-handbook on github.com/wordpress.

General

@joedolson We’re under a week from betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1. There are now 14 tickets in the milestone, three of which need to be completed before beta 1. 28 tickets have been completed. The three tickets remaining in the milestone are plausible, assuming I can find the time to get through them all.

Gutenberg

@joedolson reported that, the icons 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. has been removed from 6.9, but the Accordion block has been stabilized and Block Comments (now Notes) is in the process of being stabilized. Both of these have been reviewed extensively, but don’t hesitate to keep re-checking. The Tabs Block is still undetermined, but will need additional accessibility review.

Media

@joedolson reported that There’s been good progress on #63895, but could really use more stock photo examples to test. Contact @saj1ad to provide images. (An update from Sajjad would be helpful here regarding whether he’s received any samples yet.)

Themes

@joedolson noted that looking towards having updates on accessibility-ready after WP Accessibility Day. @joedolson will follow up with @alh0319 to move this forward.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @joedolson for the pre-publish review.

#accessibility, #meeting-notes

Nasim Miah 1:56 pm on October 4, 2025
Tags: , meeting notes   

Accessibility Team Meeting Notes: October 02, 2025

On Thursday, October 2, 2025 at 11:00 PM GMT+8, a team meeting started in #accessibility facilitated by @muddassirnasim. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Bug Scrub Schedule for WordPress 6.9

The bug scrub schedule for WordPress 6.9 has been prepared for its upcoming release.

Updates from working groups

Design

@joedolson reported that the admin redesign is officially no longer part of the 6.9 roadmap, so it will not be an immediate concern. This outcome was largely expected.

There will also not be a new default theme in this release cycle, which means design needs are relatively light.

Documentation

@rianrietveld reported that the WP Knowledge Base is now ready for contributions 🎉. All 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) content from the current handbook has been copied into wpaccessibility.org, and placeholder pages have been created for new content. The How to contribute pages are finished, including information for contributors who don’t work with GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/. A tracking issue is available with details on what still needs to be written.

Rian will write the web form documentation herself, as she has permission to use materials written for the Dutch government. Level Level, a Dutch WordPress agency specializing in accessibility, will conduct an official WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.-EM audit on wpaccessibility.org at the beginning of November, with the goal of having all accessibility issues fixed by then. Contributors are encouraged to pick tasks from the projectboard Wp A11y Docs, but should only contribute on topics they know well, as AI is not yet reliable in accessibility.

For October, @rianrietveld will start writing content on web forms. @aialvi will work on migrating the current handbook to a new GitHub repository on github.com/wordpress. @joedolson and @1fixdotio will focus on the remaining issues in the website itself.

General

@joedolson reported that we are just under three weeks away from betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 of WordPress 6.9. There are 19 tickets still in the milestone, including five enhancements/features that need to be committed before beta. So far, 25 tickets have been completed for this milestone.

All enhancement and feature tickets were scrubbed on Tuesday and are in good shape, with most looking plausible to complete. However, a few are at risk. Ticket #48655 has had only minimal progress with some initial research, and ticket #49876 has seen no recent involvement from its contributor, meaning significant work is still needed.

Overall, the milestone is in good shape despite these concerns.

Gutenberg

@joedolson reported that several major features are in progress that are important for accessibility, including the Icons 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., Tab block, Accordion block, and Block Commenting. He has reviewed the Icons block, Accordion block, and Block Commenting, but has not yet had time to review the Tabs block.

Feedback on the Accordion block and Block Commenting is in good shape. However, the Icons block has been shifting directions frequently, and accessibility feedback has not yet been addressed. Joe plans to review the Tabs block this week and will revisit the Icons block to confirm whether his earlier feedback is still relevant after the changes.

There may be additional issues, but these are the main updates at this stage.

Media

@joedolson reported that testing on ticket #63895 is in progress, but more image sources are needed to ensure thorough results. In particular, images from major stock photo sites such as Shutterstock, Adobe Stock, Getty Images, iStock, and Alamy would be helpful. Contributors who have access to new images from these sources are encouraged to share them with @saj1ad, who is collecting them.

This ticket is not currently set for the 6.9 milestone but could be included if these issues are addressed in time.

Themes

@joedolson noted that @amberhinds is working on the theme accessibility ready guide. However, with WP Accessibility Day happening in less than two weeks, it is unlikely that there will be updates on this work until November.

@joedolson also mentioned that it may be difficult for him to attend the next meeting, since Accessibility Day will be ending just as the meeting begins.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @krupajnanda for the pre-publish review.

#accessibility, #meeting-notes

Krupa Nanda 9:16 am on September 23, 2025
Tags: , meeting notes   

Accessibility Team Meeting Notes: September 18, 2025

On Thursday, September 18, 2025, at 15:00 UTC, a team meeting started in #accessibility facilitated by @krupajnanda. You can read the full transcript or see the meeting agenda.

Biweekly Team Meeting Time Update

The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.

Bug Scrub Schedule for WordPress 6.9

The bug scrub schedule for WordPress 6.9 has been prepared for its upcoming release.

Announcing the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Program Team

 The recent launch of the Core Program team, which is an expansion of the previous Core AI Team program model. 

Updates from working groups

Documentation

@rianrietveld reported that the team has been working to make wpaccessibility.org ready for contributions. They have copied all 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) content from the current handbook into the new site and created placeholder pages for new content. @1fixdotio has implemented a preview option for Pull Requests so contributors can review proposed content without a local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer..

@rianrietveld also suggested including more people to work on the content of the documentation, and provides a list of Todo issues for people to contribute to, but cautions that contributors should only work on topics they know well, as AI is not yet very good at accessibility.

Aminul will work on the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of the current handbook to a new GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ repo, accessibility-team-handbook

Only the Accessibility Team-related info will stay in that handbook.

General

@joedolson reported that @alh0319 raised several new tickets that were reviewed in the bug scrub last week.

Gutenberg

@joedolson has raised comments on the Icon 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. and Block Commenting 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/, and needs to review the Tab block and Accordion block.

Media

@joedolson reopened the discussion on whether to import alt text from image metadata, noting the pros and cons both.

Meta

Updated the Current Release tracking document.

Themes

@alh0319 will be working on converting existing documents into markdown and adding them to a repository in the WP Accessibility organisation so that we can coordinate with other docs processes.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @muddassirnasim, for the pre-publish review.

#accessibility, #meeting-notes

Krupa Nanda 12:28 pm on September 9, 2025
Tags: , meeting notes,   

Accessibility Team Meeting Notes: September 03, 2025

On Wednesday, September 03, 2025 at 15:00 UTC, team meeting started in #accessibility facilitated by @krupajnanda. You can read the full transcript or see the meeting agenda.

New Team Reps

@krupajnanda and @thisisyeasin are selected as 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 Reps, and @muddassirnasim joined the team to contribute and gain experience in the role.

Accessibility Team Meeting Schedule

The team discussed finding the best meeting time that works across different groups, with @joedolson and the other team reps working to propose options for a vote. The new meeting time is to be announced soon!

Updates from working groups

Design

  • @joedolson shared that the design working group’s main focus is the admin redesign, which is a large and complex project that’s difficult to track. He emphasised the importance of reviewing new interfaces for accessibility since current work is mostly limited to design proposals. He also pointed out that specific areas, such as 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. Commenting, need more design attention and shared a related GitHub issue for reference.

Documentation

  • @rianrietveld and @joedolson are working on new Accessibility documentation, which can be followed on the make/accessibility blog with the hashtag #wp-a11y-docs. They are getting more contributors to help with this effort.

General

  • @joedolson reported on progress with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets, noting that 28 tickets were assigned to the 6.9 milestone, 7 were punted due to inactivity, and 18 have been committed. He also introduced a large patch on #40428 ticket related to hiding CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site.-generated content from assistive technologies and requested testing support.
  • Joe shared that he audited the WordPress admin for CSS-generated content issues, made changes to ensure dashicons selectors use generated empty alternatives, and emphasised the need to verify there are no visual differences in updated code. @krupajnanda suggested a potential “call for testing” post and requested instructions on how to test, to which Joe confirmed he would prepare guidance.

Gutenberg Team

  • @joedolson shared that the 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/ items and the implementation of the Lightbox in Galleries are the most relevant things that need testing.

Media

  • @joedolson mentioned he had a discussion point but preferred to defer it to the next meeting due to time constraints. He requested adding “Discuss integration of media metadata sourced alt text” to the next meeting’s agenda.

Meta

  • No updates were reported.

Themes

  • @joedolson reported that work is still ongoing to complete the accessibility-ready themes documentation, with Amber Hinds set to follow up on that.

Open Floor

  • Nothing major was discussed during the open floor.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.

Thank you, @muddassirnasim, for the pre-publish review.

#accessibility, #meeting-notes

joesimpsonjr 5:52 pm on April 28, 2023
Tags: , , meeting notes   

Accessibility Team Meeting Notes: April 21, 2023

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

Updates from the working groups

Only groups that provided updates are shown below.

## Gutenberg Team Here’s a status update from @annezazu and the 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/ team:

  • Mainly want to raise attention to the latest call for testing: https://make.wordpress.org/test/2023/04/17/fse-program-testing-call-21-front-page-fun/ combined with the latest update to the overall phase 2 issues: https://github.com/WordPress/gutenberg/issues/33094

### Media and Meta @joedolson provided the following updates on Media and 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. for discussion:

  • For media: the regression in media custom fields is fixed in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and just awaiting merging to 6.2.1; not much else has changed this week.
  • For meta: several changes made to alt text input, labeling, and public visibility for the photo library which should really improve that. For general: I’ve slated quite a few tickets from the distant past for 6.3 in the last couple weeks; if anybody wants to work on patches for those, or otherwise dive in, that would obviously be appreciated!

### Themes @poena generously provided the following update from the THEMES team: Themes: There is a proposal for reorginizing the theme developers handbook. There is a general request for feedback on the propsed outline. The feedback period for the outline ends on April 28, 2023. https://make.wordpress.org/themes/2023/04/04/theme-handbook-overhaul-proposal/ Kafleg, one of the team reps has also asked for help with some accessibility-ready theme reviews. Anyone interested can message him on slack or use the #themereview 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.

### Open floor

@joesimpsonjr asked if we’re all set as a team for 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. Europe’s 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/. @joedolson answered: We’re certainly set; we haven’t decided who is going to take responsibility for leading the table; I wanted to find out if any more people were likely to be there, first. It’s nice to be able to partner to run the table. I think that as long as Stefano and I are there, we’ll definitely have the table handled; that’s not a worry.

@joedolson made the following updates for consideration for the following teams/topics: As a general addition to the agenda, we should talk about WCEU and contributor day; I’ve written responses to the Make Team interview questions, which I’d appreciate feedback on. https://docs.google.com/document/d/19aC3kJF2PF0oSwUYub4K4taxvKVX3fhOHyST5EfF5A0/edit#heading=h.du9x0ee9zyb

@joedolson announced WP Accessibility Day save the date is out; it’ll be September 27th-28th.

@desrosj shared a crosspost on Cultivating More Effective Contributing on Contributor Days. Take a look when you have a moment…

@chaion07 shared this about WordPress 6.2 at https://make.wordpress.org/design/2023/03/30/why-jazz/

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility, #agenda, #meeting-notes

joesimpsonjr 5:51 pm on April 28, 2023
Tags: , , meeting notes   

Accessibility Team Meeting Notes: April 7, 2023

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

## Updates from the working groups

Only groups that provided updates are shown below.

[### General Team[(https://wordpress.slack.com/archives/C02RP4X03/p1680883795044319)

  • Reviewed 11 tickets 11 tickets in today’s bugscrub, slated several for 6.3 and closed two.

### Gutenberg Team

  • @annezazu reported on the following for the Gutenberg Team: I want to note this new layout type called “grid”: https://github.com/WordPress/gutenberg/pull/49018 It would be rad to get some reviews here! Finally, various modals are becoming more common and I’d love to get some early a11y thought around unifying the various modals here: https://github.com/WordPress/gutenberg/issues/39308 #49018 Try adding a grid layout type WordPress/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/ | Mar 12th | Added by GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ #39308 Align pattern / template part modal dimensions, and add view options WordPress/gutenberg | Mar 9th, 2022 | Added by GitHub

### Media Team @joedolson provided the following updates on Media and 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. for discussion:

  • There’s a regression in media modal custom fields caused by some accessibility changes, so that’s a priority right now, targeted for 6.2.1. The change that prevented a loss of focus also caused custom fields not to display on newly uploaded items. So we’re hoping not to have to revert that, and find an alternative solution. Otherwise, just scoping out what will fit into the 6.3 plans. See: https://core.trac.wordpress.org/ticket/58051

### Meta Team Joe also provided this for the Meta Team: There’s a lot going on in Meta right now, but probably the biggest thing we should be watching for is the possible switch from Slack to Matrix for a core chat service. It’s still very much in exploration stages, but it could mean significant changes in work flow. Mozilla switched to Matrix in 2020; here’s some info from Marco Zehe on using it with a screen reader: https://www.marcozehe.de/how-to-use-element-and-matrix-with-a-screen-reader/ Otherwise, there’s the ongoing redesign efforts and various new systems being spun up. It’s a lot to track…

Open floor

@joesimpsonjr mentioned making submissions for the WordPress Community Summit and announced @alexstine is helping organize 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. US 2023.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility, #agenda, #meeting-notes

joesimpsonjr 10:35 pm on April 5, 2023
Tags: , , meeting notes   

Accessibility Team Meeting Agenda: April 7, 2023

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, April 7, 2023, 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, April 7, 2023, 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).

#accessibility, #agenda, #meeting-notes

joesimpsonjr 6:42 pm on January 28, 2023
Tags: , meeting notes   

Accessibility Team Meeting Notes: January 20, 2023

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.

Documentation

@ryokuhi updated the group on a discussion in the channel about links opening in a new tab and it was pointed out that there isn’t anything about it in the Accessibility Handbook. @joedolson clarified provided a link to this topic in the Docs guide although without the accessibility reasons and mention by @sabernhardt it’s also in the Accessibility Handbook. Brings up the need for cross-referencing. Anyone interested, please make a Pull Request to the Doc Style Guide to add the cross-reference.

General

@ryokuhi shared that the General Team is:

  • currently focusing on the Awaiting Review queue and on tickets milestoned for 6.2;
  • at the moment, all the 12 tickets Awaiting Review have been reviewed at least once;
  • there are 15 tickets milestoned for 6.2, with 14 of them already reviewed in the last two bug scrubs;
  • following discussion on #56228 last week, we need a few eyes on the related Gutenberg Issue 42373, so that we set the time frame to milestone the related coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issue; and
  • 6 more tickets were already committed for the next release.

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/

Before the meeting, @annezazu reported this for the Gutenberg Team and welcomes comment:

  • Latest update for phase 2 items: https://github.com/WordPress/gutenberg/issues/33094#issuecomment-1384570000
  • Accessibility review for the offcanvas editor issue: https://github.com/WordPress/gutenberg/issues/46939
  • A run down of items for the training/docs/polyglot crew that might be helpful: https://make.wordpress.org/training/2023/01/13/information-sources-for-wordpress-6-2/#comment-3629

Media

@joedolson shared a post on media management that we may want to discuss during our next Media Team meeting.

Open floor

Notes during Open Floor:

  • Our Call for Team Rep nomination is still open at https://make.wordpress.org/accessibility/2022/12/02/call-for-team-rep-nomination-december-2022/. We’d love for someone to step forward to support this team’s efforts; and
  • @joedolson reiterated the need for testing on the FSE experience; anybody can do it: just spend time with the environment and see what accessibility issues you spot.

#accessibility, #meeting-notes