Category Archives: Notes

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

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 by 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 12:28 pm on September 9, 2025
Tags: , ,   

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

Rishi Mehta 6:43 am on September 26, 2024  

Accessibility Team Meeting Notes: September 18, 2024

These are the bi-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 Wednesday. This particular meeting was not held. See the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Gutenberg Working Group: @annezazu for this ‘hefty’ share from 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/ working group:

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.

joesimpsonjr 3:12 pm on August 20, 2024  

Accessibility Team Meeting Notes: August 16, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

General Working Group: @joedolson shared this update for discussion/comment:

  • Lots of progress on patches, but I’ve been really short on time to get them committed. Hopefully will make some progress next week.

Gutenberg Working Group: @annezazu for this ‘hefty’ share from 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/ working group:

@joedolson commented:

  • Would like to second @annezazu pointing out of the accordion block as something that should get attention. It’s been a heavily demanded block, and maybe if it goes in we can get ‘accordion’ removed as a search keyword for the details block.

@poena also commented:

  • Yes the “Deprecate comment pagination” issue could benefit from comments from the team. I need to reply back, it is on my to do list.

Media Working Group: @annezazu for this ‘hefty’ share from the Gutenberg working group:

  • @antpb is continuing to work on a PR for the future media library interface, but it’s not ready for reviewing yet; once that’s making more progress, media will need to be a major focus.

Meta Working Group: @annezazu for this ‘hefty’ share from the Gutenberg working group:

  • Joe Dolson will be doing a final 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) review of the Playground block next week, then it should become available for Learn users after that.

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.

joesimpsonjr 11:06 pm on August 4, 2024  

Accessibility Team Meeting Notes: August 2, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Meta Working Group: @elblakeo31 shared this update the impacts the 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. working group for discussion/comment:

  • He’s performing an automated accessibility scan on learn.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/. I just delivered a list of all the elements missing alt text in Learn. Anyone can request any automated testing from me. We’ve also been tuning Equalify, based on what we’ve learnt from our WordPress volunteering. Here’s an article he wrote about that: https://equalify.app/helping-wordpress-org-become-accessible/

Electing two new Make WordPress Accessible Team Reps

We received two nominations – @nhrrob and @rcreators – who expressed interest in assuming the roles and nominated themselves on our Call for Team Reps post. There were no other nominees and @joesimpsonjr moved to ratify them as our new Team Reps effective September 1st. @joedolson confirmed that this is acceptable as process. Joe Simpson will follow through on onboarding the remainder of the month. Welcome to Rishi and Nazmul Hasan Robin!

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.

joesimpsonjr 10:29 pm on July 21, 2024  

Accessibility Team Meeting Notes: July 19, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Team Updates

Design Working Group:

Documentation Working Group:

  • Joe also mentioned that @Amber Hinds and the contributors at WCEH spent some time on theme accessibility-ready documentation.

General Working Group:

  • WordPress 6.6 is released. Also, bug scrubs have been continuing; I’ve now got about 30 tickets milestoned for 6.7, so Joe will be getting started on those soon. @afercia has been getting a number of tasks done 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/, as well.

Gutenberg Working Group:

  • @joedolson ran the bug scrub this week on Gutenberg issues, and @jeryj made a PR for one of the open issues that we wanted to have available to test conceptually. Here: is the link to the Github PR. This automatically opens the 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. panel for 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. settings when a block is selected. Currently, the block sidebar stays in whatever mode you’ve selected, which requires you to switch modes if you want to configure blocks. This PR would change that so that the block sidebar auto-switches to be active when you select a block. We want to test this to see whether it makes an easier flow; it might be an improvement, but we’re not really sure. I’m going to try and set up a test environment that can be shared so that I can ask some people to try it out. When I (Joe) do, I’ll post on Make WordPress Accessible.

Themes Working Group:

Work is starting on Twenty Twenty Five, so that’s the biggest new thing. But the progress on the accessibility-ready tag is also moving forward; continuing work as I mentioned earlier, but also some tickets with movement to add information about the accessibility-ready tag in user facing environments in the theme directory.

These two items would really help in letting people know what exactly the accessibility-ready tag means.

Media Working Group:

  • @antpb is working on experimentation for the next generation media library; we discussed it on Wednesday. Nothing else to report there. It’s still in very early stages, but we talked about some long-term goals that we want to think about, so that the media library can be built in a way that would support those features. Things like an in-browser captioning environment, etc.

Meta Working 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. is giving feedback to @elblakeo31, who is getting his process refined, on the following update:

Also, FYI- Looks like there’s a comment on the Alt issue here: https://github.com/WordPress/wporg-main-2022/issues/462#issuecomment-2214176587.

The hardest part is the timing; the scans of the old design are mostly being ignored, because (rightly) they’re going to be redesigned soon.

Open Floor:

@joesimpsonjr will follow up with @nhrob and @rcreators regarding expressed interest in assuming the 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. roles and asked Joe for thoughts on procedure and preparing for a vote to make it official. He suggested posting a post for a Call for Team Reps, documenting what is seen as responsibilities to pass on as well. You can use this as a reference https://make.wordpress.org/updates/team-reps/.

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.

joesimpsonjr 10:45 am on June 8, 2024  

Accessibility Team Meeting Notes: June 7, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Team Updates

Documentation Working Group:

  • @Dani Guardiola has stepped up to do a review of the Accessibility Handbook and start updating it. @joedolson has already fixed a handful of issues in the Handbook thanks to Dani’s feedback.

Team Updates

General Working Group:

Here’s the latest for the General Working Group.

  • Lots of progress recently on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets, so things have been moving forward at reasonable pace in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Joe also shared that we’re currently in 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, so enhancements for 6.6 are closed.

Team Updates

Gutenberg Working Group:

@annezazu shared this update from 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/ Working Group:

Pulled from last week’s Core updates:

  • Grid layout: Stabilise grid layout visualiser and resizer saw a bonus aspect of the grid layout work land, offering a visual way to resize. Tied to this, a recent change makes the outlines of the visualizer easier to see based on the text color.
  • Unify publish flows: Curious to hear from folks around a change to the RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. panel making it behind a three dot menu (adding an extra step) rather than displaying it as a top level item in the post 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.. For scheduled posts, a PR is underway to ensure the publish date control selection is shown within the modal.
  • 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. shadows: Edit/create shadows in global styles landed and is in a solid spot for the release.
  • Block HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.: after more research and experiments, work to Add support for block name aliases for variations is being mostly pushed to 6.6 except for items from this list, which should all be significantly lower risk, and prepare the ground for the bigger changes (for are targeted for 6.7).
  • Inserter: a PR landed to show all blocks when searching for blocks while a block is selected. The current experience shows either a limited set or no blocks depending on allowed blocks.
  • Data Views: a recent PR bootstraps an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to allow third-party developers to register and unregister post type actions. This is going to be available in the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. only for now and is not planned for 6.7 but relates to the overall efforts.
  • Accessibility: review and join a discussion around a recently opened issue for Consistent Sidebar DOM and Open/Closing Interactions.

Joe stated that there was a project to merge the code base for the site editor and the post editor. That has created a few new accessibility problems that need to be ironed out; I don’t know whether that will happen in time, but we’ll see.

Themes Working Group:

@Amber Hinds is starting to work through the backlog of accessibility-ready theme reviews.

Media Working Group:

  • Media is continuing to work through issues; but most major work is being slowed due to the future planning for the media library redesign.

Meta Working 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. is continuing to work on the site redesign; work is currently mostly in Learn.

Open Floor:

@joesimpsonjr shared three items for consideration/discussion:

  • 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 kicks off next week. Anything to share on 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/ or the event to share at this time?
  • The Accessibility Team is in need of new Team Reps to take over for Alex and myself who have served two plus years. @nhrrob has shown interest and would like more info on what the role entails (Alex has shared some basic info). Alex also mentioned a short voting period as part of the process as well. If you are interested, please reach out;
  • WordCamp US happens in August in Portland, OR. Are there any folks from the team planning on attending the event AND contributor day? Joe is NOT planning on attending, unfortunately.
  • @amberhinds shared this thread for our Accessibility Team plans for WCEU. Joe and Amber are leading the Contributor Day table at WCEU; Amber is focusing on doing theme accessibility reviews and Joe is focusing on developer onboarding and tickets.
  • Team Reps: I’m open to stepping back on with @nhrrob
  • Amber and Joe will be at WCUS as well.

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.

joesimpsonjr 5:58 am on May 15, 2024
Tags: 6-6-release-leads, , ,   

Accessibility Team Meeting Notes: May 3, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Team Updates

Gutenberg Working Group:

@annezazu shared this update from 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/ Working Group:

Themes Working Group:

@poena shared this update from the Themes working group:

  • The focus style change in Twenty Twenty-Four was punted from the minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. 6.5.3. to 6.6 https://core.trac.wordpress.org/ticket/60808

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

joesimpsonjr 3:03 pm on April 5, 2024
Tags: , ,   

Accessibility Team Meeting Notes: April 5, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Team Updates

Gutenberg Working Group:

@annezazu shared this update from 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/ Working Group:

Joe commmented that the data views will need some attention, since they’re going to be important in the next gen admin.

Meta Working Group:

@joedolson reported that 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. is prepping the new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. directory design, and he provided some feedback last week. But if anybody else wants to take a look, it’s been posted in #website-redesign and could use some time. All the issues he’s reported have already been handled.

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

joesimpsonjr 4:05 am on April 1, 2024
Tags: , ,   

Accessibility Team Meeting Notes: March 15, 2024

These are the bi-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 or see the full meeting schedule.

Updates from the working groups

NOTE: Only groups that provided updates are shown below.

Team Updates

General Working Group:

  • @joedolson shared that he’ll continue to work his way through the backlog of issues on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.; mostly finished with tickets awaiting review, and aiming to get a lot done in 6.6.

Gutenberg Working Group:

@annezazu shared this update from 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/ Working Group:

  • Zoomed out view tracking issue has been edited to add more individual tasks and items. This is an area to pay attention to as work is beginning to revisit this option and how it interacts with things like patterns.
  • DataViews: Forms overview issue to discuss how to unify the various forms created like inspector panels or detail pages.
  • WIP: Advancing site editor index views issue that showcases follow up work to the data views for pages and templates.
  • WordPress 6.5 – Data Views accessibility audit issue to capture feedback coming from the 6.5 release of data views to help focus next steps for 6.6.

Joe commmented that the data views will need some attention, since they’re going to be important in the next gen admin.

Meta Working Group:

@Blake (Equalify) is working on a project to bulk assess the accessibility of .org properties.

Open Floor for Discussion:

  • Joe asked for everybody take time to look at WordPress 6.5. While major changes are out of scope at this point, if you find minor accessibility issues, those can still be fixed. Work on 6.6 is already started, so don’t hesitate to participate on issues milestoned for that, as well. 6.6 is intended as a polish and maintenance release, which is a great opportunity to focus on fixing issues instead of chasing features, so this is a very important release for our team.

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