Tag Archives: meeting notes

Stefano Minoia 8:30 pm on April 15, 2021
Tags: 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

alexstine 2:27 am on April 6, 2021
Tags: meeting notes   

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

Update from working groups

  • Design: no update.
  • Docs and Patterns: added some notes around tables.
  • General: no update.
  • 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/: no update.
  • Media: no update.
  • 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.: no update.
  • Themes: no update.

Feedback requested

The following items need feedback.

Open floor

Add testing instructions to 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/ pull request template that way instructions are always provided on how to test a change.

#meeting-notes

alexstine 6:21 pm on March 26, 2021
Tags: meeting notes   

Accessibility Team Meeting Notes: March 26, 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.

Update from working groups

  • Design: no update.
  • Docs and Patterns: @Jill Mugge has done some work on the Pattern Library, specifically the Alternative text pattern as well as fleshing out more topics under Content patterns. @azhiyadev has started to work on the accessibility handbook.
  • General: no update.
  • 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/: A few updates
  • Media: lots of planned work but no progress at this point.
  • 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.: no update.
  • Themes: no update.

Open floor

  • Next week @azhiyadev will run the accessibility team meeting and @alexstine will cover the bug scrub.
  • Even though more clocks are changing due to daylight savings time, bug scrub and meeting times will stay the same.

#meeting-notes

Stefano Minoia 11:30 pm on March 25, 2021
Tags: meeting notes   

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

Review of accessibility team’s goals for WordPress 5.8

Following the pubblication of the call foor WordPress 5.8 Accessibility Team’s goals and the decision to postpone the discussion by two weeks, a general discussion took place about some of the proposed goals for next release.

WordPress 5.8 will be out in July 2021, but the exact date hasn’t been set yet.

Here are the main takeaways of the discussion.

  • 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/ development will be followed more in detail. @ryokuhi volunteered to review the page about Gutenberg testing to update it and create a routine to test if users relying on assistive technologies (for example, using only keyboard navigation and/or screen readers) would be able to perform standard tasks in 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. editor.
  • Also, Full Site Editing (which will land in the next release) will be a priority. @critterverse agreed to try to keep up with the FSE outreach experiment by testing using assistive technologies, making sure there’s some accessibility coverage and reporting to the team with the results.
  • Work on documentation will be central even during the next release. @Hauwa Abashiya reported about a discussion regarding the possible audience for the accessibility handbook, which includes both creators (designers and developers looking for resources about accessibility) and contributors (who want to contribute to the project itself). As such, the documentation working group will focus around:
    • the about page (what the team does, the different working groups)
    • the Getting Started or Get Involved chapter (how the team works, onboarding, ways you can contribute, etc.)
    • resources for creators (tools, pattern library, etc.)

It’ll be up to each working group to keep moving towards these (and other) goals during the release cycle, so all contributors are invited to join a working group and become a representative for a working group, in case there isn’t one.

Open floor

@Jill Mugge friendly reminded all WordPress contributors to always add the alternative text to images in posts.

#meeting-notes

alexstine 9:03 pm on March 17, 2021
Tags: , , meeting notes   

Accessibility Team Meeting Notes: March 12, 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.

Meeting time change following Daylight Saving Time introduction

Meeting and bug scrub times will stay the same. Bug scrub at Friday 15:00 UTC and meeting at Friday 16:00 UTC. The day will stay the same on Friday.

Improvement of onboarding for new contributors

Here is a list of ideas that the accessibility team came up with to improve the onboarding process for new contributors to the accessibility team.

  • Add information about the bi-monthly meeting for new core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to the accessibility handbook
  • Ease participation to tickets and issues with good-first-bug and needs-accessibility-feedback labels: make them more discoverable and improve how to ask for feedback from team members about them
  • Add a Slackbot welcome announcement when someone joins 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/.
  • Update the “Get involved” chapter in the accessibility handbook and make the handbook more friendly for new contributors (discussion will happen in the #accessibility-docs channel on Slack)

Open floor

@annezazu informed the team that Taylor Arndt very kindly joined a Zoom meeting to share some feedback around the Full Site Editing experience when using screen readers. Here’s a quick summary of issues to be aware of (she’ll include some of these in a recap post she’s doing for the FSE Outreach Program’s second call for testing):

@annezazu also flagged the following items:

Here are a couple other issues brought up by the team.

If you have time to review/contribute to the new accessibility standards, your feedback is welcome and much appreciated.

#meeting-notes

Stefano Minoia 8:00 pm on March 11, 2021
Tags: meeting notes   

Accessibility Team Meeting Notes: March 5, 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.

Review of accessibility team’s goals for WordPress 5.8

Following the pubblication of the call for WordPress 5.8 Accessibility Team’s goals, a discussion about the proposed goals should have taken place.

Some team members missed the post and it wasn’t clear if existing goals were to be reported again, so no comments to propose new or existing goals were added to the post.

According to the news about the changes to the release plan for 2021, WordPress 5.8 release will be postponed to July 2021, which gives a few more weeks for development: because of that, the team agreed to postpone the discussion about team goals for two weeks. Also, @ryokuhi agreed to summarize goals identified earlier and to add a comment to the call for team’s goals.

Open floor

@Estelaris asked for feedback from the team regarding the redesign of HelpHub (WordPress support documentation for end users). In particular, she asked for feedback on improving the use of the hashtag (#) symbol, which can be found next to each section heading and that links to that same heading, allowing for easy copy-and-paste of a link to that section of the documentation. After some discussion, the team was able to identify the issues of the current design and implementation and some possible paths to improve it. @Estelaris will do some more research and will write a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post, x-posting the Accessibility Team for reference.

@Hauwa Abashiya asked for some extra quick review of the accessibility standards.

#meeting-notes

alexstine 9:10 pm on February 28, 2021
Tags: meeting notes   

Accessibility Team Meeting Notes: February 26, 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

  • Documentation and Accessibility Patterns: updating the existing accessibility standards document. Publishing information about 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 changes. Plan is still to publish the document around the 5.7 release.
  • Media: most 5.8 priorities set. Planning to scrub all old tickets. The most notable change is removing infinite scroll from the media library.
  • Themes: no progress on workshop lesson plans. Two Accessibility Ready tagged themes went live.
  • 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/: persistent list view continues to be a topic of discussion. Full site editing second call for testing. Internet Explorer 11 support could be ending. Post going live Monday or soon after.
  • Design: no updates.
  • 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.: no updates.
  • General: Twenty-one tickets fixed in 5.7.

Call for WordPress 5.8 accessibility team’s goals

The post has been published and is ready for your feedback: Accessibility Team’s goals for WordPress 5.8 and beyond

Open floor

#meeting-notes
alexstine 4:56 am on February 22, 2021
Tags: meeting notes   

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

Final review of WordPress 5.7 goals

  • Accessibility: most tickets have already been handled.
  • Media: starting to plan 5.8 goals.
  • Documentation and Accessibility Patterns: no updates on progress. @joedolson said he would shift some of his focus in to writing 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 docs now that we’ve arrived at RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.. Contributions always welcome. Plan is to have docs done by 5.7 release. Contribute here.
  • 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. Screen: @joedolson created a TRAC ticket. Next week we’ll discuss timeline.
  • Learn WordPress: meeting notes from yesterday.
  • Themes: no update to share.

Open floor

#meeting-notes

alexstine 8:33 pm on February 12, 2021
Tags: meeting notes, training   

Accessibility Team Meeting Notes: February 12, 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

  • Documentation: updating the existing documents for accessibility standards to provide better guidance. Publishing information about 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 changes. Track progress in the WCAG 2.1 WP Update Google Document.
  • Media: #47120 will be committed before 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. 3; #50105 will be deferred to 5.8-early. It’s almost there, but it’s a major 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. change that would require a significant push to have ready by Tuesday, and should really sit in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for longer. Joe Will probably commit as soon as alpha opens for 5.8, however. All media tickets are either committed or already bumped to later.
  • Themes: Accessibility Ready tag reviews in progress, a couple days out of the week. Working on developing workshop on Learn WordPress.
  • Design: good progress with design/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) joint bug scrub.
  • 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 Meta TRACTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket worth checking out: Category archives pages : accessibility improvement (HTML)
  • General: during the bug scrub, we reviewed the five tickets with milestone 5.7 that are still open. 16 tickets in the milestone have been closed.

Open floor

  • WordPress 5.8 is open for development, now is a good time to start coming up with accessibility goals.
  • The next Learn working group meeting is being held in #training on Thursday, 18 February 2021, 19:00 UTC.
  • @mgifford will be giving a presentation at the DC Drupal meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. group about the accessibility of the new White House website (built with WordPress). If possible, consider attending! Drupal NoVA: 10 Things We Can Learn from the New WhiteHouse.gov on Accessibility

#meeting-notes

alexstine 8:49 pm on February 7, 2021
Tags: meeting notes   

Accessibility Team Meeting Notes: February 5, 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.

Review team’s activities during WordPress 5.7 Alpha

Beta1 was released Tuesday. Let’s look back to see what went well, what didn’t go well, and what to improve on next time.

  • It was agreed that working groups did help and should be used in the future.
  • It is important to have one referent per working group.

Plan activities for WordPress 5.7 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.

  • 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/ accessibility testing. Checking the done tickets in https://github.com/WordPress/gutenberg/projects/52. General checks to make sure new features/fixed issues did not result in accessibility regressions.
  • Provide pre-release accessibility testing instructions for main features in Gutenberg. Fit as much in to end to end tests as possible.
  • WordPress updated color scheme checking.

#meeting-notes