alexstine 6:51 pm on October 22, 2021
Tags:   

Accessibility Team Meeting Notes: October 22, 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 shown below.

Design

@chaion07 highlighted these two proposals that might be worth looking in to.

General

  • Today, there was a brief pause on tickets milestoned for 5.9 due to the reviewing of the Awaiting Review queue. It may be worth having an extra bug scrub considering we’re quickly approaching the release deadlines. There will be an extra bug scrub on Wednesday, October 27, 2021 at 16:00 UTC.
  • Currently, there is also not an Accessibility Release Coordinator for 5.9. See the related Slack message here. Please message @audrasjb if you would like to volunteer or have further questions about the role. @alexstine offered to take this role if one other person would assist.

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 official WordPress 5.9 Feature Go / No Go post has been published. There are some Gutenberg items included that the team may be interested in testing.
  • The following 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 needs testing and, if replicated, a patch. accessibility: impossible to add or edit a post’s title with Jaws for Windows screen reader activated

Media

  • @priethor left a comment regarding infinite scroll in the Media Library. Our current plan is to discuss this during next weeks Accessibility meeting.
  • @madtownlems is currently working on a 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 that may improve accessibility of existing images without Alt Text. The plugin is not yet publicly available, but we’ll let everyone know when it is ready for testing. @sabernhardt shared the following TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket, containing some background about reusing Alt Text: improve the user interface to ensure correct usage of the image alt text.

Themes

While there were no updates from the Themes group today, it is likely time to start allocating some focus to the new Twenty Twenty-Two theme. This Twenty Twenty-Two GitHub Issue is currently tracking accessibility.

Open floor

Just a reminder to vote on which meeting time will work best for you. The poll will remain open until Friday, October 29, 2021 16:30 UTC.

#meeting-notes

alexstine 7:21 pm on October 20, 2021
Tags:   

Accessibility Team Meeting Agenda: October 22, 2021

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, October 22, 2021, 16:00 UTC.

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

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

The Accessibility Team bug-scrub will be held on Friday, October 22, 2021, 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).

#agenda

alexstine 5:30 pm on October 15, 2021
Tags:   

Accessibility Team Meeting Notes: October 15, 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 shown below.

General

Going through TRACTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets milestoned for 5.9 in the New Features and Enhancements categories. Will finish this off soon, probably by next week.

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/

Although there were no updates shared from the Gutenberg group today, this post on accessibility improvements in Gutenberg might be worth highlighting for anyone who hasn’t read it yet. This 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 could also use screen reader testing. List View: experiment with only rendering a fixed number of items

Media

@joedolson reported about progress redesigning the image editor and requests feedback on these tickets. View the comment here

Themes

While there were no updates from the Themes group today, it is likely time to start allocating some focus to the new Twenty Twenty-Two theme. This Twenty Twenty-Two GitHub Issue is currently tracking accessibility.

Open floor

Just a reminder to vote on which time zone will work best for you. This is the new time zone which will be used for Bug Scrubs and Meetings. Vote here The poll will remain open until Friday, October 29, 2021 16:30 UTC.

#meeting-notes

alexstine 5:56 pm on October 14, 2021
Tags:   

Accessibility Team Meeting Agenda: October 15, 2021

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, October 15, 2021, 16:00 UTC.

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

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

The Accessibility Team bug-scrub will be held on Friday, October 15, 2021, 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).

#agenda

alexstine 3:00 pm on October 14, 2021
Tags:   

Accessibility Team Meeting Notes: October 8, 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.

Discussion around meeting time as Daylight Saving Time will be changing soon

Most of the contributors in today’s meeting agreed the time could remain the same, but a poll was created to ensure all voices are heard. Take the poll here.

Updates for the working groups

Given the limited time, only @azhiyadev from the Documentation group asked a question about which themes should be referenced in the team’s handbook (in general, the current default theme at the time of writing). She also reported about an audit tool under development by the Training and Docs Teams to capture the version number of WordPress referenced in documentation.

Open floor

@azhiyadev asked what is needed to improve the accessibility of animated gifs and videos without audio. A few suggestions were given, here is a short summary.

  • For videos without audio, captions make no sense, as they are only the transcription of the spoken text of the video. Nevertheless, descriptive transcripts can be useful: they include a text description of the visual information needed to understand the content and are essential if the video is not purely decorative and if part of the content is not available in text form. This is also required by Success Criterion 1.2.1 of WCAG 2.1.
  • Don’t use autoplay on videos.
  • Allow users to pause a gif; an example on how to do this is available in an article on CSS-Tricks.
  • Maybe, show a static image instead of the gif if the user has activated the prefers-reduced-motion preference.
  • Make sure there are no flashing lights.

#meeting-notes

alexstine 2:43 am on October 7, 2021
Tags:   

Accessibility Team Meeting Agenda: October 8, 2021

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, October 8, 2021, 16:00 UTC.

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

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

The Accessibility Team bug-scrub will be held on Friday, October 8, 2021, 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).

#agenda

annezazu 2:36 pm on October 6, 2021
Tags: ,   

X-post: Core Editor Improvement: Continued progress on accessibility

X-comment from +make.wordpress.org/core: Comment on Core Editor Improvement: Continued progress on accessibility

alexstine 6:00 pm on October 1, 2021
Tags:   

Accessibility Team Meeting Notes: September 24, 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 shown below.

Design

@shawnandrews, who has been attending Accessibility Team’s weekly meetings in the past few months, has been nominated Design 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..

General

During the bug-scrub before the meeting, the Team finished to go through all tickets in the Awaiting Review queue which hadn’t been addressed before: a few of them still need decisions, but at least all of them were reviewed.

The 5.9 release schedule has been published a few weeks ago. Following are the dates of greatest interest for the Team.

  • October 12th: Go / No-go meeting about Full Site Editing scope for 5.9
  • November 9th: Feature freeze (only bug-fixing from this point on)
  • November 16th: 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 (only bug-fixing for bugs introduced during the 5.9 release cycle)

At the time of the meeting, there were 14 enhancements and 20 bugs milestoned for 5.9: the team will start to focus on them beginning with the next bug-scrub.

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/

Following discussion on ticket #54075 about disabling the preview of legacy widgets 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, @critterverse created a GitHub issue to allow for turning on and off the preview via the Preferences section of the Option menu. As always, all feedback is highly appreciated.

Also, notifications are now shown in the Accessibility 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 again when a new Gutenberg version is released and when the Needs Accessibility Feedback label is added to an issue or to a pull request.

Media

@joedolson reported that the Media Team has been also continuing to work through awaiting review items and shortlisted a few of them that will be possibily addressed in 5.9.

A few tickets are about very old issues, which may not be relevant anymore (a possible example is #23562, opened in 2013 and in need of testing from people using voice control tools). The first step is to re-test these tickets: a list will be added as a comment to these meeting notes.

Themes

During bug-scrub, the Team reviewed a couple of tickets about the Twenty Twenty-One theme: feedback on one of them was asked to one of the original developers.

Open floor

Given the concurrent WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US happening on Friday, October 1st, the bug-scrub and the meeting are cancelled.

#meeting-notes

alexstine 9:06 pm on September 22, 2021
Tags:   

Accessibility Team Meeting Agenda: September 24, 2021

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, September 24, 2021, 16:00 UTC.

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

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

The Accessibility Team bug-scrub will be held on Friday, September 24, 2021, 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).

#agenda

alexstine 7:37 pm on September 20, 2021
Tags:   

Accessibility Team Meeting Notes: September 17, 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.

Improvements to 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/ contrast checker

Following a suggestion made in a comment to the meeting agenda, the team discussed possible improvements 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. Editor notification shown when the contrast between a text and its background is too low. The full discussion can be found 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, following are the main takeaways.

  • Marking the combination with low contrast as an explicit accessibility concern will help people understand the reason why they should take action.
  • On the other side, it’s also possible that content creators not interested in meeting the needs of people with disabilities would just ignore the issue altogether, instead of considering it.
  • Adding a link to a trusted resource might be a nice way to educate users about color contrast. This is already in place in other parts of the WordPress interface: in the media library, for example, there’s a link to the Alt decision tree right below the Alternative text input field.

The Team agreed to continue discussion about the topic by opening a related issue in the Gutenberg repository.

Updates from the working groups

Given the lack of time, the point is postponed to next weekly meeting.

Open floor

Nothing for open floor this week.

#meeting-notes