Accessibility Team Meeting Notes: June 18, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

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

Last week @ryokuhi wrote a post announcing his team rep term was coming to an end. Since there were no comments on it, we opened up a discussion in the meeting. Find the announcement post here. It was decided that @ryokuhi would remain team rep to help @alexstine with the day to day tasks required by the role. However, if you would still like to step up as team rep, just let @ryokuhi and @alexstine know and we can coordinate the transition.

Updates from the working groups

Only the groups that provided updates are listed below.

Documentation

Update from @azhiyadevev:

I’ve started updating the Pattern Library section on Make. A lot of work has already been carried out by @Jill Mugge and @joedolson. Unfortunately, it requires a bit more brain power from me to review everything that has been done so far. I’ve been lacking that this week with my schedule but next week should be better.

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 new and improved WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. experiences — all attention is now being focused on fixing bugs ahead of 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. on June 29th so it’s a great time to test!
  • Testing welcome on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ PR: Remove role group from blocks to see if I can fix JAWS. #32799.

Design

No big updates from Design today. The team reviewed the “About 5.8” Page ticket during the bug-scrub, but it seems in good shape as far as design is involved. View the Ticket.

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.

The team found that there’s no way to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. Meta tickets for focuses (including the accessibility one), but found a temporary workaround.

Meta ticket #5757 was updated to include the mockup of a possible solution.

Media

There is one ticket that currently needs the latest patch tested. Add a copy-link button at the media upload page.

General

  • 10 tickets milestoned for 5.8 were closed until now.
  • The Awaiting Review is clear from new tickets, but the team plans to really try to clear it completely including the really old tickets.

Open floor

  • Next week, @ryokuhi will not be able to attend the bug scrub or the meeting. If anyone would like to volunteer, please let @ryokuhi or @alexstine know. The date of the next bug scrub is Friday, June 25, 2021, 15:00 UTC. The meeting is one hour after.
  • @alexstine will be unavailable for the bug scrub and meeting on Friday, July 2. Right now, no extra coverage is thought to be required.

#meeting-notes

Accessibility Team Meeting Notes: June 11, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Call for 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.

It has been nearly a year since @ryokuhi was nominated team rep. Because of this, he feels like the time has come to step down and give others the opportunity to run as candidates for the position. Following the meeting, a Call for Team Rep post will be published where you can add your name in to the running. Call for Team Rep nominations

Gather some answers for a survey regarding ATAG Part B in WordPress

Mike Gifford, a Drupal accessibility professional, wants to collect some feedback. ATAG comes in 2 parts. Part A is to make it accessible to authors with disabilities. Part B is to support authors in producing accessible content. There is a huge opportunity to make the web more accessible by providing better tools to authors. Funka gathered together CMS that were popular by governments in the European Union. There was an effort to bring together as many of the maintainers of these CMS as we could to discuss what could be done collectively to implement ATAG 2.0 Part B. You can see the main results here. Find the questions below.

Is ALT text required?

At this time, ALT text is encouraged in WordPress but not required. This may change in the future, but no immediate plans.

Ability to change languages in the editor?

Not supported at this time. @joedolson found the issue has been raised and will follow-up on it.

Can authors understand accessibility documentation? Does it make sense to content editors/publishers?

Documentation is below expectations at this point especially when it comes to publishing information about how to use 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/ with assistive technologies. It’s a work in progress for the team as a whole.

Are tables accessible by default or does the editor guide you to make an accessible table?

No, you must know what you are doing to create a structurally accessible table.

Does WordPress include an accessible forms creator?

Since there is no forms creator in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., the answer is no. There are plugins that can add this functionality.

Can you upload videos with captions or transcripts? Are you able to add titles to IFrames?

Yes and yes. All of these are supported in WordPress core.

Is there any guidance to authors about creating accessible content in the editor?

There are a couple basic tools such as color contrast checking and heading order. This could be expanded in the future.

Any accessibility checking for uploaded documents such as PDFs?

No, nothing exists in core for that at the moment.

Does WordPress come with tools to help test the front-end of pages or the entire site?

No, nothing in core. There are some external services/plugins that can do this.

Would there be any interest in adding any of the above to core?

There may be some interest in the future, but at this point, it is not likely to happen.

Is there increased interest from authors for creating accessible content?

Absolutely.

What is happening to support authors who want to create accessible content?

Find the WordPress ATag statement here.

Is there increased interest to make the editor accessible to people with disabilities?

Probably not as much as the Accessibility team would wish.

What is WordPress doing to make the editors more accessible to people with disabilities?

That is one of our teams biggest goals. Progress takes time.

Has WordPress ever been in collaboration with other authoring tools?

Not with the Accessibility team, but the Security team works with others to ensure WordPress stays as safe as possible. It is also possible that other teams do as well.

Find the beginning of the conversation in the accessibility channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Open floor

Last week, a post about moving to 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 was published but now it has been covered up by other posts on the blog. The proposal is to pin the post at the top for a couple months.

@annezazu reports:

I just wanted to mention List View as something that would be great to get accessibility feedback around as it’s coming to 5.8 in the Post Editor + Template Editor and will be an important tool leading into whatever the Site Editor experience is like. You can read about the feature here and see what improvements are planned here.

#meeting-notes

Accessibility Team Meeting Notes: June 4, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Open issues before WordPress 5.8 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

The team had a general look at how work is progressing towards WordPress Beta 1, happening on Tuesday, June 8.

TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Tickets

All open tickets in the 5.8 milestone were looked at during the bug-scrub before the meeting.

Most of them are minor issues that need testing and code review, but that will be committable by Beta 1.

The biggest issue still to address relates to the removal of infinite scrolling from the media library (described in ticket #50105). It’s a hard-to-solve problem of backward compatibility, but @joedolson will dedicate some time to it to clearly identify the problem and possible solutions. Other possibilities would be to write a dev-note describing the breaking change and what authors will need to do to reinstate infinite scroll if needed.

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 and Pull Requests

Version 10.7.2 of 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 was released on the day of the meeting, probably including all and only features that will be included in the next version of WordPress.

In the next few weeks, the team will shift to test Gutenberg and Full Site Editing more in depth.

The latest Full Site Editing Call for Testing is open until June 16th, and might be a helpful place to guide testing.

Another area where test is needed is the WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editors (both in the Appearance menu and in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.), given that htey have gone through many changes recently and are still being improved upon. To have an idea about what is being worked on, you can check the project board for the block-based widgets editor in the Gutenberg repository on GitHub.

Documentation

Documentation will be worked on more extensively in the next few weeks.

The agreed changes to the accessibility handbook page about Working Groups have been made.

The updated WordPress Accessibility Coding Standards were published, just like a post about changes from WCAG 2.0 to WCAG 2.1.

Next step is to continue work on the Pattern Library: the draft document about accessible patterns and anti-patterns is public and everyone is invited to give feedback.

Open floor

The team agreed to unsubscribe from the notifications published in the 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 by the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ bot whenever a deployment happens in the Gutenberg repository. GitHub Pages were added to the repository, but since then the channel has been polluted by too many notifications per day. @ryokuhi agreed to take care of that.

As announced, on Monday, May 31st, @ryokuhi and @alexstine had a chat about with Mike Gifford, who asked if it was possible to

get a WordPress answer to a bunch of questions about ATAG Part B for the We4Authors Cluster project he’s involved in.

@ryokuhi suggested to reserve some time during the next weekly meeting to understand what the team can do and decide together how to move.

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 runs from Monday, June 7th to Wednesday, June 9th, with a lounge area dedicated specifically to accessibility. Team contributors are invited to join, but no one should feel forced to keep the Lounge Area covered.

@ryokuhi‘s term as Accessibility Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. has almost come to an end. Team Rep nominations will open up next week: if you’re interested in applying and have any questions, feel free to write a message to @ryokuhi or @alexstine.

#meeting-notes

Accessibility Team Meeting Notes: May 28, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Updates from working groups

Only working groups that provided updates are listed below.

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/

Feedback for the Seventh Call for FSE Testing is always welcome .

General

Having a look at the milestone on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., there are 11 open tickets in the 5.8 milestone. 5 other tickets have been closed. The current period is dedicated to fixing bugs and ends on June 8.

Media

The media team managed to get some key accessibility-related enhancements into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. before the deadline, so that was satisfying. They are now turning attention to get some bug fixes in and to test and polish the enhancements.

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.

A new ticket about coding string status on translate.wordpress.org only through color was opened in the Meta Trac and needs design feedback. @critterverse offered to take a look and provide any thoughts/feedback.

Open floor

@ryokuhi and @alexstine are going to meet with Mike Gifford in response to the following message.

Are there folks in the WP community working on improving the authoring interface in terms of accessibility? Specifically ATAG 2.0 Part B? Anyways, would love a discussion at some time with folks who might be interested in the findings from the We4Authors Cluster.

They will provide a summary of the discussion during the next meeting to keep things as open and transparent as possible.

#meeting-notes

Accessibility Team Meeting Notes: May 14, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Accessibility discussion around 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/ GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue Post Title Block: add typography formatting options

The focus of this discussion is around whether it’s a good idea to allow underlining of text that is not a link as underline can strongly indicate that the text is a clickable link and may lead to confusion if non-links are underlined.

It was decided that it would be better to remove the underline formatting option from the pull request for now and maybe revisit implementation later if there is a greater need.

How to move forward with Proposal: new workflow keyword to exclude tickets until review is needed

At this point, the proposal was posted a couple weeks ago. The best way forward is likely to choose a keyword name. Another suggestion was brought up to just mark tickets as Future Release milestone. A list of keywords that the team is considering can be found in a comment on the original post: comment posted here.

Updates from the team’s working groups

Due to a time shortage, this agenda item was skipped for today.

Open floor

FSE Updates

Both are part of Full Site Editing Go/No Go: Next steps which makes these crucial for Accessibility team feedback.

Documentation

Accessibility Standards documentation updated via the GitHub PR: Update accessibility.md.

Media

The infinite scroll removal has been committed for 5.8. If you notice any issues during testing, please report them via Core TRAC.

Next Bug Scrub/Meeting (Friday, May 21, 2021)

Because of concurring tasks, @ryokuhi and @alexstine won’t be able to facilitate the Accessibility bug scrub or meeting on May 21. @chaion07 has offered to lead the bug scrub and @joedolson has offered to lead the meeting.

#meeting-notes

Accessibility Team Meeting Notes: May 7, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Updates from the team’s working groups

Only teams that gave updates are listed.

Design

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/

Full Site Editing (FSE)

  • The second Go / No Go Test was cancelled: the list of features that will be included in WordPress 5.8 can be found in the post about Full Site Editing next steps. Here is a list of items included in the scope, shared from the core-editor channel on Slack.
    • 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. theme building
    • Theme blocks (Query, Navigation, Site Logo…)
    • Template editing within the post editor
    • Widgets Editor & Block Widgets in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.
    • Persistent List view in the post editor
    • Duotone design tool
    • Gallery block refactor
  • The Global styles “interface” is not going to be included in 5.8, but Global Styles infrastructure which theme authors can use to build their themes is
  • Query Quest Summary for the latest call for testing. A community member did two different keyboard tests.
  • Round two of questions is open until May 12th and the next round of testing on template editing mode will ship on May 12th as well.
  • Template Editing Mode is gearing up to be an important feature most likely for 5.8 so getting testing done there would be very helpful. Tied to this, I expect testing for the Widgets Editor come up soon too. Of note, the current “opt out” approach seems to be through a new classic widgets plugin with more context in Add a plugin to disable the block based Widgets editor.

Documentation

  • The Documentation working group is working on updating the Working Groups page.

General

  • In the last two weeks the Accessibility team checked all Enhancements / Feature Requests tickets, which are due by May 25. It’s seven tickets, so we should be able to get them committed in time.
  • There are also nine tickets marked as Bugs / Blessed Tasks, we’re starting to address them beginning next week, but still prioritizing Enhancements / Feature Requests.
  • Would like to clear the Awaiting Review queue, but will likely prioritize 5.8 milestone.

Media

Open floor

  • The proposal by the team to add a new workflow keyword was shared during dev-chat, and both the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the Design teams were cross-linked. Feel free to add your thoughts to the post.
  • Because of concurring tasks, @ryokuhi and @alexstine won’t be able to facilitate the Accessibility bug scrub or meeting on May 21. @chaion07 has offered to lead the bug scrub and @joedolson has offered to lead the meeting.

#meeting-notes

Accessibility Team Meeting Notes: April 30, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Advancement status of TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets, 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 and team’s goals for WordPress 5.8

During the last but one meeting, the team agreed to have a general check on how the team’s work for WordPress 5.8 is progressing: the goal is to keep better track of what areas need more help and to decide if extra meetings or bug-scrubs are needed.

Trac Tickets

Here’s the situation for Trac tickets at the time of the meeting.

  • All tickets milestoned for 5.8 have an owner
  • Eight tickets are Feature Requests or Enhancements and, as such, should be committed in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. by the Feature Freeze date (May 25, 2021); during the bug-scrub before the meeting, the team reviewed all but two of them
  • Nine tickets are marked as Bugs or Blessed Tasks, but there are two extra weeks after Feature Freeze date to commit them

While the team has done a good job at reviewing tickets, more contributors or more time would be of great help to solve these issues. Unfortunately, this is one of the biggest issues that the team is facing, but there’s little that can be done to improve this. Anyway, as the situation is under control at the moment, the team agreed not to plan any extra bug-scrubs.

Gutenberg Issues and Pull Requests

Version 10.5 of 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 was released on Wednesday, April 28. The second go / no go test for Full Site Editing should have taken place on Tuesday, April 27, but the final decision about whether Full Site Editing will be included in WordPress 5.8 and at what scope was still pending at the time of the meeting. Contributors are invited to monitor the Make WordPress Core blog to check for updates.

More in general, the only accessibility issue included in the list of “WordPress 5.8 Must Haves” issues was solved two days prior to the meeting.

At the time of the meeting, there were 211 issues / Pull Requests with the “Accessibility (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))” label and 77 issues / Pull Requests with the “Needs accessibility feedback” label. Some team members have been asked to review if some of the older issues are still relevant, hopefully they would find time in the near future.

Team Goals

@ryokuhi still have to start updating the page with instructions on how to test Gutenberg for accessibility: updated instructions will be ready at the latest by the Feature Freeze date.

Work on documentation has slowed down a bit and there are no updates, but work on it can happen also outside of the release cycle, so it’s not a big issue.

Open floor

@joedolson asked for feedback on the latest patch in the ticket to Remove infinite scrolling from the media grid.

@ryokuhi posted the proposal to add a new workflow keyword to exclude tickets until review is needed. The Core team was cross-posted and the link shared during dev-chat.

#meeting-notes

Accessibility Team Meeting Notes: April 23, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Proposal to improve usage of keywords and labels on accessibility tickets, issues and pull requests

Add a new workflow to TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets. This will allow the accessibility team to skip a ticket if there is an in progress or not yet developed UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. from popping up in weekly bug scrubs. The proposal post was published on the Accessibility blog. Our request will be brought up in dev chat.

Updates from the working groups

Only the groups with updates to share are listed below.

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 following updates were provided by @annezazu for Gutenberg.

  • Check out the upcoming FSE Outreach Program schedule. TLDR: call for questions coming next week + the 6th call for testing is planned to be about template editing and the navigation 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. starting May 12th.
  • Read a detailed post sharing next steps after the first go/no go date. TLDR: various testing calls and refinements need to happen before 5.8’s feature freeze on May 25th.
  • Read the IE 11 Support Phase Out Plan. TLDR: officially removing IE11 support in WordPress 5.8.
  • A PR was merged to add focus on the save button in FSE but there’s some feedback indicating that this is a disruptive flow.

Documentation and Patterns

moved the 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) Pattern Library to its own document. 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/. 2.1 Update doc was getting substantial.

Media

not much movement. Requesting opinions on  removing infinite scroll.

General

Regarding general, today we still had a look at the Awaiting Review queue, next priorities are:

  • Assign an owner to all tickets in the 5.8 milestone.
  • Go through tickets milestoned for 5.8 and marked as enhancements and feature requests.

Open floor

It was suggested that the team make the accessibility team working groups more visible this way new contributors could find the list and know what each group’s responsibility is.

#meeting-notes

Accessibility Team Meeting Notes: April 16, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Planning bug-scrubs and meetings for WordPress 5.8 release

Following updates to the 5.8 release cycle timeline and to the 5.8 pre-planning post, the next WordPress release cycle is now more defined.

@ryokuhi introduced the discussion, highlighting the main points.

  • Following the first round of testing on Full Site Editing, the plan is to merge some features in the next release.
  • In earlier releases, work on existing bugs could be done also during 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., but in the latest releases Beta was intended exclusively to fix bugs introduced during each release cycle. To allow specific time to bug squashing, a new “Feature freeze” deadline is introduced two weeks before Beta 1: after Feature freeze, only bug fixing is allowed.
  • At the time of the meeting, without taking in consideration 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 Full Site Editing, there were 17 tickets in the 5.8 milestone: 1 ticket is marked as early , 1 ticket is a feature request , 7 tickets are enhancements  and 3 don’t have an owner (but the team has to address only 2 of them).
  • As the difference between enhancements and bugs is now significant again, the team needs to decide how to prioritize work, given that until now bug-scrubs focused mainly on tickets in the Awaiting Review queue and that new features or enhancements should be ready by May 25.

A discussion followed about how to prioritize work so that all tickets marked for 5.8 will make it in the release.

The main decision was to have to two checkpoints on April 30 (right after the second Go / No Go test on Full Site Editing) and on May 21, to better keep track of what areas need more help and to decide if extra meetings or bug-scrubs are needed.

Also, in the next weeks bug-scrubs will gradually move from focusing on Awaiting Review, to Feature Requests and Enhancements, and then to Bugs and Tasks.

Updates from working groups

Only groups which had updates shared them.

Gutenberg

@annezazu shared a few updates about Full Site Editing and Gutenberg in general.

  • The call for testing on the Query Block was shipped with feedback due by May 5: as the 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. will almost certainly be included in 5.8, contributors are invited to test for accessibility concerns as soon as possible.
  • The post about the first Go / No Go test helps to understand the major areas of focus for Full Site Editing in 5.8, so it can be an interesting reading. According to the post, the main areas in need of tests are template editing and major blocks like the Navigation Block and the Query Block.
  • A Pull Request to add block titles to the block switcher label will be included in version 10.5 of the 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.
  • The Pull Request about focusing the save button when the save panel opens might need some extra feedback.

Documentation

@Jill Mugge reported that the working group is adding more accessible patterns and antipatterns. During the meeting, she suggested that creating a template for documentation could be helpful to stay consistent and improve accessibility, so she volunteered to do it.

Media

@joedolson reported that he did some work and that he should make more progress by next week.

Open floor

A clarification was given about why threads should be avoided on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#meeting-notes

Accessibility Team Meeting Notes: April 9, 2021

These are the weekly notes for the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Quarterly community updates

Every three months, all Make WordPress teams are asked to update the community at large about what they are doing, so that everyone is aware of what’s going on. All updates are collected in a post published in a specific section of the WordPress website.

Previously, discussion about what to write in the post was left to the team reps, but @alexstine and @ryokuhi agreed that bringing it in the wild would be good for the team.

During the meeting, the team discussed about the challenges and big wins for the team in the preceding three months. @ryokuhi offered to integrate the points brought up during the meeting with the team goals for the next release and to write the report. Updates for the first quarter are now available on the Make website.

Updates from working groups

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

@annezazu and @poena shared a few updates regarding Gutenberg and Full Site Editing

Full Site Editing updates

Gutenberg highlights

Documentation

@Jill Mugge has been working on accessible patterns and antipatterns.

Media

@joedolson reported that everybody on the media team has been very busy in the last month, and nobody has done work on any open tickets yet.

Design

@sarahricker had been away for a few weeks and no one else was able to report.

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

@joedolson reported that there were no updates regarding meta.

Themes

@poena left a note after the meeting.

  • There was no progress regarding the workshop for reviewing accessibility-ready themes
  • There was no progress regarding adding more end user information about what accessibility-ready means
  • The list of approved themes waiting for accessibility-ready review is empty, but the Michelle live theme is waiting for it

General

Bug-scrubs are still focused on clearing the Awaiting Review queue as much as possible. As soon as the 5.8 release date is confirmed, focus will move to tickets in the 5.8 milestone (currently, there are 15 of them).

Open floor

@paaljoachim asked for general and accessibility feedback about two Learn WordPress tutorials he wrote. This lead to opening an issue to fix the contrast problem in the Code Block CSS in the Learn WordPress repository.

#meeting-notes