Category Archives: Working Group

Amber Hinds 2:01 pm on August 28, 2023
Tags:   

WCUS 2023 Contributor Day Summary

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 had 24 contributors working on various projects during 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. US 2023 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/.. The session started with an orientation for new contributors on getting involved with the accessibility team as a developer or tester.

Amber Hinds (@alh0319) gave a demonstration of how to use keyboard navigation and VoiceOver for people who were not familiar with screen readers or accessibility testing. WordPress targets Web Content Accessibility Guidelines (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/.) 2.1 AA conformance for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds 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/, and Twenty X themes.

@joedolson and @alexstine led a table of developers and assisted them in getting setup with local environments so they can submit patches to core and Gutenberg. Three new contributors got set up with local environments for patching and testing.

Projects Worked On

After the onboarding, contributors worked on the following projects:

Testing Twenty Twenty-Four

Multiple people tested the new Twenty Twenty-Four theme. Issues were opened in the 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 for Twenty Twenty-Four related to accessibility issues in the theme itself or 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. patterns included in the theme.

Testers included:

There is a Google sheet for tracking what has already been tested in Twenty Twenty-Four. The theme is not fully tested, and contributors are encouraged to continue testing and logging issues beyond contributor day. Please track what you have tested in the spreadsheet or reference it if you’re not sure what still needs to be tested.

When testing Twenty Twenty-Four @robpetrin noted that there are both block patterns created by the theme and core. If you want to disable the block patterns created by core to only test block patterns in the theme, Rob provided this code, which can be added to the functions.php file to disable core blocks.

add_action('init', function() {
	remove_theme_support('core-block-patterns');
});

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/ Accessibility Statement

Blake Bertuccelli-Booth (@elblakeo31) led a discussion about adding an accessibility statement to the footer of WordPress.org. There is not currently an accessibility statement for the WordPress.org website and contributors would like to see one added.

These are the steps identified to move forward with creating an accessibility statement:

  1. Domain discovery to determine what pages exist.
  2. Discussing WCAG Guidelines and what standards the WordPress website should strive for.
  3. Reviewing existing accessibility statements for similar projects or template sites (such as Drupal, UK examples, W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/.’s template, etc.)
  4. Testing web pages to identify existing issues or current accessibility status.
  5. Creating a draft statement in a Google Doc for the community to review.

Domantas Gudeliauskas. (@domantasgudeliauskas) created a spreadsheet of subdomains on WordPress.org and determined that there at 285,631 pages on WordPress.org, including subdomain sites, that might ned to be tested for accessibility problems.

There are several discussion threads in #accessibility for people who are interested in continuing this discussion and work.

Bug Scrub

Developers who worked on resolving existing accessibility tickets in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. and GitHub include:

We got one new WordPress account set up, three developers set up with new local environments, and reviewed, researched, and patched several accessibility tickets.

Thank You

Thank you again to everyone who contributed during Contributor Day. We look forward to seeing everyone at a future Accessibility team meeting.

Thanks to @joedolson for reviewing this post.

Joe Dolson 3:00 pm on August 7, 2023  

Matrix Test Results

In 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) chat for Friday, August 4th, the team ran the entire meeting within Matrix, using a variety of different clients, to assess the current state of the environment for users with disabilities. If you’re not already familiar with Matrix, it’s an open-source federated chat platform that is being evaluated as a possible replacement for 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/..

Right now, it is possible to use Matrix or Slack clients to interact in a Slack meeting, so while we held our meeting using Matrix, it was recorded in the Slack accessibility channel. Review the conversation in Slack.

As long as we can use both clients to interact, there are no significant concerns. However, we need to set accessibility criteria that the Matrix experience needs to meet before it’s feasible for the project to migrate solely to that platform. (Other teams may have other criteria, of course.)

Summary

Overall, Matrix was marginally usable for screen reader users and keyboard navigation. Most buttons were labeled and possible to interact with, and it was possible for screen reader users to post messages, read messages, and change channels. (Or rooms, in Matrix terminology.)

However, there were significant barriers to usability that would make the experience slow and frustrating for both these groups of users. As a productivity tool, it would significantly decrease the productivity and participation rate of users with disabilities.

Issues Noted

Please note that this was not a formal testing scenario, and should not be considered complete. This was a live interactive session in which we explored the environment trying to discover as much as we could in a short time.

  1. @alexstine (NVDA, Windows, Chrome, expert screen reader user) So far, I’m finding the web version of Element not verbose at all, causing me to really explore the page to get anything useful.

    Issue: Using a screen reader, the application didn’t provide much in the way of orienting tools that Alex could use to efficiently locate key functions and information.

  2. @Travel_Girl (Maja Benke) (Element web app, Firefox, Dark Mode, prefers reduced motion) I find it hard with keyboard to use it, but I’m not a native keyboard user.

    Issue: Two fundamental issues here. First, the keyboard shortcuts are difficult to locate. Second, the keyboard shortcuts are inadequate, and don’t provide tools for moving between application regions or navigating messages.

  3. @alexstine Landmarks are lacking and I can’t figure out how to predictably access the message list.

    Issue: As above, this is a lack of orienting tools and navigation mechanisms for reading messages.

  4. @alexstine Can you find a keyboard shortcuts guide? I’m coming up empty on basic docs.

    Issue: Keyboard shortcuts list was difficult to find in the app, and online docs were extremely minimal.

  5. @alexstine Got to be honest, this experienced is pretty terrible in comparison (to Slack). There is just no way to navigate the app globally. Slack uses F6 or Ctrl+F6 in the browser, and none of these work in Element web.

    Issue: Inability to navigate around the app is a major problem for screen reader users.

  6. @alexstine …There is no global navigation shortcut. This is going to be an absolute nightmare to use outside of fairly advanced users. It’s like Discord, passes useability standards but not by much.

    Issue: This is a common problem in applications that have done a good job with micro accessibility issues, but haven’t given significant consideration to macro issues. E.g., buttons are labeled and it’s possible to move from control to control, but the larger scope of navigation and orientation isn’t sufficient.

  7. @joedolson (Android Element app, Talkback) Worked OK in Android/Talkback. I didn’t explore extensively, and found one unlabeled button, but message navigation and authoring was fairly easy.

    Issue: The unlabeled button was the ‘Threads’ button, if I remember correctly.

  8. @Travel_girl I don’t know how to access the rooms via keyboard (if the room is not already open) as the tabindex is not consistent.

    Issue: While Ctrl+K can be used to open a command center to search rooms, navigating via various standard keyboard commands doesn’t move you around the page in a very predictable manner. This would be less of an issue if there was better exposure of keyboard commands.

  9. @alh0319 (Amber Hinds) When you open the more information button in the web app it doesn’t shift focus into that panel and so it’s essentially as if it’s not there. I haven’t even figured out how to tab into it.

    Issue: Loss of focus prevents users from using important interfaces.

  10. @joesimpsonjr Had difficult uploading an image (random I know) but no ability to add ALT text.

    Issue: Users cannot add alternative text to images. This makes images inherently inaccessible to screen reader users.

  11. @alh0319 I’m Mac, Chrome. I can get to the button and it reads[sic] as a button, but the space bar and Return key don’t trigger it. I think it’s acting as though my focus is still in the message list.

    Issue: Seems like a problem with custom key events not firing correctly. I’m not 100% clear what the context of this was; in the conversation thread, it may have been referring to the upload image button.

  12. @alh0319 Also if you search for a person to send them a DM, there is no way to get to the results for the person. The “button” to select the person is a div.

    Issue: This refers to the People > Start Chat button in the navigation sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. There is no way to navigate using the keyboard to choose a person to chat with.

  13. Numerous people commented on the lack of formatting controls. While formatting can be done in markdown (or at least markdown-like syntax), not all users are familiar with these options. There was no documentation of how to do this in the app that we could locate.

  14. @joedolson I also don’t like that there’s no border that indicates where the message text area is located. I keep clicking above it.

    Issue: Especially for low vision users, having a well-defined indication where you need to click to initiate an action is very helpful.

Reviewed by @alexstine for technical accuracy and clarity.

Joe Dolson 2:09 pm on August 4, 2023  

Testing Matrix

The goal 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 for August 4th, 2023 is to run our meeting in Matrix to give it a test for accessibility in various contexts. For the purposes of testing, we’ll want to have a diverse collection of devices and modes: high contrast, screen readers, etc., to get different perspectives on what works best.

Online App

Open the Element web app.

Change the home server from ‘matrix.org’ to ‘community.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/’

Log-in using the WordPress.org single sign-on.

Use in browser.

Embedded Chat

Go to https://make.wordpress.org/meta/chat/

Behavior is unpredictable depending on your current interaction state with this page. You may see an error and need to back up a couple of steps until you get a sign in option. 

Follows the same sign-in process through SSO; only gives access to the one embedded room.

This method will probably not be very useful for us in testing, but worth looking at.

Apps

There are a lot of different apps for Matrix. Browse all apps.

Choose one and install it. You’ll need to set your server to https://community.wordpress.org and log-in. 

  • Element
  • FluffyChat
  • Syphon
  • Quadrix
joesimpsonjr 8:11 pm on July 17, 2023
Tags: ,   

Accessibility Team Meeting Notes: July 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.

Team Updates

  • Gutenberg: @annezazu who provided this update for the Gutenberg working group: Passing on this post hot off the press: https://make.wordpress.org/core/2023/07/03/real-time-collaboration/ Otherwise, everything is all about 6.3! Trying to triage as much as possible to get issues into the 6.3 board (like this: * https://github.com/WordPress/gutenberg/issues/52254 or this:https://github.com/WordPress/gutenberg/issues/52253). Following the instructions for the Help Test WordPress 6.3 post will go a long way.
  • General: @joedolson shared the following updates for a couple of working groups: Joe committed or punted all tickets scheduled for 6.3 last week. Most remaining open issues are at risk, but punting to 6.4 isn’t the end of the world. On themes, I’ve got @Maja Benke connected to @kafleg to start her working on accessibility ready reviews

Open Floor

  • No updates to share at this time.

  • 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-ready, #design

joesimpsonjr 10:20 pm on June 16, 2023
Tags: ,   

Accessibility Team Meeting Notes: June 16, 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.

All Team Updates

  • Media: @joedolson committed the redesign of the admin image editor earlier this week.

  • General: He has punted a number of tickets to 6.4, but have a significant handful that are ready or nearly-ready to commit.

  • Themes: At WCEU, Joe talked to Maja Benke about taking on the task of reviewing themes for accessibility-ready tags, so she’s going to start getting trained in on that task and will interface with the theme review team to help on that. This is important since the theme review team is low on accessibility knowledge right now.

  • 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 site editor needs testing; we’re moving in very close to the end of the cycle, and there are a lot of new features that need some attention. Please install Gutenberg and play with all the new features. Particularly look for any focus losses, controls that aren’t working from the keyboard, or focus moves that should happen and don’t (e.g., opening a modal then not being placed inside it).

  • @sabernhardt shared the following 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. team update: Please review the pull request on 4730.

  • @alexstine shared this update for comment: https://github.com/WordPress/wporg-mu-plugins/issues/405 and for async review: https://github.com/WordPress/gutenberg/issues/51126#issuecomment-1594825674

Open Floor

  • WCEU A11yAccessibility 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 Onboarding — At 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/. at WCEU, the team onboarded a few additional people to review 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. output & Maja Benke wrote up a draft of a document for us to post to help people know the process they should follow when testing block output. Will document soon.

  • Is it possible to change our meeting time? — Also, Maja Benke requested that we once again consider changing our meeting time – she would like to attend, but our current time is not good for her. And, honestly, our current time isn’t really good for anybody in Europe – Friday evening is just not a great time for people to attend a meeting. We should give this serious thought. Other team members, like @poena, are also routinely unable to attend. Because we have members in the US Pacific time zone, we can’t move a lot earlier reasonably, but we could change to a different day, so that European attendees aren’t having to start off their weekend with a voluntary meeting…

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-ready, #design

joesimpsonjr 6:32 pm on June 15, 2023
Tags: ,   

Accessibility Team Meeting Notes: June 2, 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.

Documentation and General Teams

@joedolson has been focused on scrubbing older 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/ issues in bug scrubs; trying to get some of the early concerns re-addressed and establish status updates and has several patches nearing readiness to commit; awaiting some feedback.

Media Team

@joedolson mentioned needing needing opinions on [#50523] (https://core.trac.wordpress.org/ticket/50523). He’s requested feedback from #design and hoping to get it soon.

Themes Team

@joedolson reviewed three #accessibility-ready theme candidates last week, to help the themes team out. Anyone interested in training on how to review, contact Joe.

Open floor

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 is next week and we talked about 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/.. Also talked about WordPress Community Summit and being invited.

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.

Joe Dolson 5:14 am on June 7, 2023  

Contribute to Accessibility at WordCamp Europe Contributor Day

What does 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 do in WordPress?

We support the needs of people with disabilities across the entire project. This can range from training and teaching, consulting on specific development projects, testing features, and contributing code to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. With such a broad scope of needs, the accessibility team is always in need of more people to participate.

There’s no need to know code or accessibility to contribute to the accessibility team! An important part of what we do is help developers better understand how they can create more accessible code; so if you’re an experienced developer who wants to know more about accessibility, come chat with us!

If you don’t know code, but want to contribute, we’ve got ways for you to help as well – documentation and testing are always ongoing needs for our team.

What should I do to prepare to contribute?

The WordPress core team has already posted a lot of information on preparing for contributor day, and a lot of that is equally relevant for you. If you’re not a developer and don’t intend to test new code, you may not need to go through the whole process of setting up a local development environment. However, testing upcoming changes in WordPress does require a development environment where you can apply patches and pull requests for WordPress and for 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/.

However, testing isn’t just about new features. 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/ site itself needs ongoing review and testing, and the code that already exists in WordPress can always be improved.

Find us 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. Europe!

Both Joe Dolson (@joedolson) and Stefan Minoia (@ryokuhi) will be present to coordinate accessibility contributors at WordCamp EU’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/., and we’re looking forward to chatting with you about anything to do with WordPress and Accessibility! We can set you up with a task, answer questions, or start to teach you accessibility testing processes.

See you soon!

joesimpsonjr 6:00 am on May 22, 2023  

Accessibility Team Meeting Notes: May 19, 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.

Media Team

Here’s a status update from @joedolson and the Media team:

  • Patches for #50523 & #26381 are ready and could use testing/opinions. Please try these patches and make comments. These need to go in early to make it into 6.3.

General Team

@joedolson provided the following updates on General Team for discussion:

  • Feedback on #15631 and #32170 would be appreciated.It is sortable columns and is fairly extensive. All of the tickets are in the "could be ready to commit stage".

Gutenberg Team

@annezazu reported: A few notes — some accessibility testing for the navigation block with the interactivity API: https://wordpress.slack.com/archives/C02RP4X03/p1684403764422519 Also the 6.3 roadmap is now out in the open: https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/ I’m working on a next call for testing and hoping to post today to go through some of the in progress features :heart: Folks are always welcome to participate.

Open floor

@joedolson noted that WCEU is in three weeks and is looking forward to accessibility conversations that will be had there. He’ll be in Athens from June 6-13 and can chat about a11yAccessibility 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) at any time. He has an interest in bringing people in long term with more teaching about how to contribute to WordPress.

@joesimpsonjr shouted out Design Team’s @chaion07 for his appearance on the WP Tavern podcast about Contributing to WordPress as a non-developer.. He also asked about plans for 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/. 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. US in National Harbor in August.

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.

joesimpsonjr 5:54 pm on April 28, 2023
Tags: ,   

Accessibility Team Meeting Agenda: May 5, 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, May 5, 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, May 5, 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

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

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