Accessibility Team Meeting Agenda: March 15, 2024

This is the proposed agenda for the weekly AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Friday, March 15, 2024, 16:00 UTC.

Updates from working groups

  • Design
  • Documentation
  • General
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Media
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub has moved to Tuesdays, 16:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#accessibility, #agenda

X-post: Discussion: Bringing accessibility-first approaches into content development

X-comment from +make.wordpress.org/training: Comment on Discussion: Bringing accessibility-first approaches into content development

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

Team Updates

Documentaton Working Group:

General Working Group:

  • @joedolson shared that 6.5 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. is out and in testing, so please take a look! There are still some important bug fixes in hoping to get in.

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:

Outside of the chaos and joy of 6.5, some quick items to note for you all:

Also want to flag up whether anyone is game to write a recap of accessibility improvements for 6.5.

Open Floor for Discussion:

  • Joe asked for more feedback on the Accessibility Vision Document;
  • @joesimpsonjr asks due to attending 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. Asia (in transit March 1), should we cancel our next regularly scheduled meeting?
  • Joe Jr also shared a message from @bethannon1: I’m reaching out to see if you think there might be interest in exploring the idea of having an accessibility-specific “happiness table” at WCUS – potentially alongside the more generic happiness table. Even if it was only for one morning or one afternoon, it might be a great way to raise awareness about accessibility. One morning or afternoon could be staffed by 4 to 6 people. One whole day might require 10 to 12 people. With my existing commitments around the event I don’t think I would be able to help staff it – but we could plan for Meg Miller from our team to help. Maybe there would be a handful of other folks from the accessibility team that might be interested?

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

Accessibility Team Meeting Agenda: February 16, 2024

This is the proposed agenda for the weekly AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Friday, February 16, 2024, 16:00 UTC.

Updates from working groups

  • Design
  • Documentation
  • General
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Media
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub has moved to Tuesdays, 16:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#accessibility, #agenda

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

Team Updates

General Working Group:

  • @joedolson shared: #51870 is just pending second opinions. This removes a ton of placeholders and replaces them with real labels. Will hopefully be updated today.

Gutenberg Working Group:

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

  • Design draft shared for the highlight grid for 6.5.
  • Section Styling: this work has been punted due to some blockers in resolving CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. specificity questions.
  • Font Library: biggest work continues to be the Font Library: refactor REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. which was merged into Gutenberg following this merge criteria for this feature and had a quick PR to follow up on feedback. Outside of that, a discussion is underway around making the font library more discoverable.
  • Pattern overrides: there are some current questions around how this features ties to 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. Renaming 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. and how the internal block ids are generated and used. Right now, we can find the block names through block ids, but we cannot do the same the other way around.
  • Data Views: a recap of what’s planned and stable for 6.5 has been shared along with a PR to add sync status by default for Patterns, matching the current experience.
  • Link Control: A bigger PR was merged for Implementing new UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. for invoking rich text Link 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. by requiring explicit activation before displaying the Link UI interface.
  • Block Bindings: the experimental flag was removed along with an outline of next steps for Gutenberg RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., 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., and what’s out of scope for 6.5 (including when to backport). For out of scope, this includes a UI for users to add bindings. A ~4 min video walks you through the current status in trunk!

Outside of 6.5, an issue was opened for Media workflows around patterns that any media minded folks will find interesting.

  • @joedolson said he’s really looking forward to the new link UI. It’s a significant improvement. @jeryj added that the interactions and states feel so much more consistent and predictable.

@chaion07 also shared this for discussion:

  • The bug-scrub schedule for 6.5 release has been updated with the dates for the alpha phase. I’d really appreciate if we get this link shared during the meeting.

Media:

  • Joe reported that there’s a major planning meeting for strategizing the new media library on Thursday the 8th, so that’s the biggest thing coming up. Did get a minor fix shipped yesterday.

Themes:

  • Joe reported I have a new volunteer who wants to work on theme reviews & documentation; he’s going to touch base with @poena and @travel_girl to discuss.

  • @travel_girl shared the first draft for the testing guideline. https://wp-coworking.de/draft-cheat-sheet-testing-for-accessibility-ready-tag/

Open Floor for Discussion:

  • Joe is head down trying to finish some things before beta 1, which is coming up very soon now;
  • @joesimpsonjr asks if anyone is attending 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. Asia and 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/.?
  • Jeff Chi asked “Did someone answer to this request regarding the WordPress 6.5 release?”

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

Special Accessibility Team Meeting Notes: January 19, 2024

This was a special meeting to discuss items key to the group moving forward, including but not exclusively: Discuss new times for the bug scrub and weekly meetings but also an 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) Vision for WordPress.

Opening/Introduction by Joe Dolson

To start this off, I’d like to make a few comments. WordPress Accessibility has, for years, worked on a catch-up schedule. Fixing historic issues in the software, then scrambling to keep up with the pace of work 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. and site editor.

But we haven’t had a solid long-term vision of what we want to achieve.

That may sound very simple: we want the most accessible software we can achieve. However, having concrete goals needs more than some vague abstraction.

The primary purpose of having an accessibility team – as opposed to independent accessibility contributors – is to set an overall goal. The “team” part is about coordinating efforts and having some kind of consensus.

Having a vision is about documenting our mutual goal and the process for reaching it.

You can read the full transcript of all the thoughts and discussion points here.

#accessibility-ready, #design, #website-redesign

X-post: Incident Response Team: Call for Nominations

X-comment from +make.wordpress.org/project: Comment on Incident Response Team: Call for Nominations

Accessibility Team Meeting Agenda: February 2, 2024

This is the proposed agenda for the weekly AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Friday, February 2, 2024, 16:00 UTC.

Updates from working groups

  • Design
  • Documentation
  • General
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Media
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • Themes

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub has moved to Tuesdays, 16:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#accessibility, #agenda

Special Accessibility Team Meeting Agenda: January 19, 2024

This is the proposed agenda for the weekly AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting on Friday, January 19, 2024, 16:00 UTC.

I. Accessibility Vision for WordPress

We’re planning a Special Meeting to discuss the accessibility vision for WordPress and changing the bug scrub. We’d love your input so please plan to attend and share with other contributors.

II. Changing the Bug Scrub

The team is looking to conduct the weekly Bug Scrub at a different time to increase the involvement of contributors who may not be able to join at its current day and time (Fridays 15:00 UTC).

III. Updates from working groups (time permitting)

  • Design
  • Documentation
  • General
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • Media
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • Themes

IV. Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will also be held on Friday, January 19, 2024, 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#accessibility, #agenda

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

Design Working Group:

  • @joedolson shared: Probably the biggest design change in the last couple weeks is the launch of the new Developer Resources design: https://developer.wordpress.org. It could use a little accessibility attention, though it’s not super complicated, and there aren’t a lot of problems. Something I noticed right away is duplicate ‘View all’ links on https://developer.wordpress.org/reference/; those need to be differentiated, but mostly it just needs some people to go over it and check for things like that.

General Working Group:

  • @joedolson shared For general, it’s mostly about rebooting the bug scrubs; which is a topic for later in the meeting. The main goal in General in the next few weeks is to try and get some patches and testing done in preparation for 6.5; currently the 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. is expected on Feb. 13th, so it’s a very short amount of time left.

Gutenberg Working Group:

  • @annezazu shared the following update for the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Team: Update for you all, including the items for the broader CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. meeting. Feel free to take or leave :slightly_smiling_face:

FYIs:

  • High priority labeled items for the Gutenberg repo has been triaged with an open convo around whether to add the label to 6.5 priority items to help improve project organization and communication.
  • New overview issue: Pattern / Template Part Unification – the technical challenges.

6.5 related updates:

  • Data Views: check out an early prototype of inline editing to explore what will be needed for a future 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., add list layout to templates PR merged, align 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. implementations PR merged, new issue for show total count in menu item, and new issue for implement Kanban layout.
  • Font Library: add global configuration variables for font directory, which enables the option to set a custom directory as font directory. Interactivity API: check out on experiment with Comments 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.: client-side form submission. Design tools: early draft PR to add backgroundSize feature with implicit repeating backgrounds to add more functionality to the Group block’s background image support that was added in 6.4.
  • Command Palette: please share feedback around whether it would be helpful to enable the command palette feature everywhere in WordPress.
  • Navigation: Check out the latest prototype for being able to customize the navigation overlay with a template part, enabling a separate menu experience for mobile.
  • Performance: loads of recent performance improvements particularly from ellatrix (too many to link to) with more to come that should greatly improve both the post and site editor experience. Please share feedback as these fixes and enhancements land!
  • 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.: the PR to integrate style book is close to landing and the PR to show change summary on selected item landed for GB 17.3.
  • Pattern overrides (new working name for the previous partial sync patterns): the UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. of the experience is being established and refined with the PR to edit source pattern in focus mode in post editor.
  • Work continues to align page editing features in Site and Post Editor with the latest update here.
  • HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. API: Backport updates from Core and HTML API: Add support for H1-H6 elements in the HTML Processor.

Accessibility additions:

  • [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)] Fix: Use spans instead of headings on dataviews table view page title
  • [a11y] Apply focus style to revision items
  • Reconsider the ‘Accessibility’ section in the Preferences modal dialog discussion.

Media:

  • Joe reported that the Media team is making plans to coordinate a meeting to discuss the media library redesign. Figuring out the timeframe and goals for that remain a top priority, since it’s going to make a big difference to how we approach existing issues. We’ve got a draft proposal to have a meeting, but no specific date yet.

Open Floor for Discussion:

  • For the next meeting:
  1. Talk about scheduling a special meeting for discussing the accessibility vision for WordPress; and
  2. Changing the bug scrub (possibly 10am CT on Tuesdays).

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