Proposal to change the day and time of the Accessibility Team’s weekly meetings

Following the discussion begun during the meeting on August 7, 2020, 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 is reviewing the day and time of the weekly meetings, with the goal to increase participation.

You can find the transcript of the discussion on our Slack channel.

The team agreed to keep together the weekly bug-scrub and the weekly meeting, with the bug-scrub starting one hour before the meeting.

After checking the WordPress meeting calendar, the team agreed to consider both Monday and Tuesday as possible alternatives to Friday.

Also, the team is considering whether to start the meeting one hour later. As usual, the starting time of the meeting will be adjusted after the daylight saving period, so that meetings stay almost always on the same local time.

You can express your preference by filling the form before Friday, August 14, 2020 at 15:30 UTC. To help you with local times, you’ll find a link to a local time converter in the form.

We look forward to seeing you during the next weekly meetings!

Cast your vote!

#weekly-meetings

Accessibility Team Meeting Notes: August 7, 2020

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.

Rescheduling of the extra triage session

After a short discussion, the team agreed to reschedule the triage session to identify tickets to be labelled as good-first-bug for Tuesday, August 11, 2020 at 15:00 UTC. To speed up the process, participants are encouraged to indentify in advance possible CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets and 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 to include in the list.

Discussion about support of non-link elements in Gutenberg navigation

A discussion about the Gutenberg issue on how to support non-link elements in the Navigation block and screen followed. The team agreed that it is really useful to explore solutions to allow WordPress users to create mega menus (complex menus including elements other than lists of links) in a semantical and accessible way, without need of recurring to third-party solutions. @joedolson volunteered to add a comment to the issue about next steps for the Navigation block and screen.

Review of the Accessibility team weekly meeting’s day and time

You can find more details about this point in a self-contained post on the Make website about changing the day and time of the weekly meeting of the Accessibility team.

#meeting-notes

X-post: WordPress 5.5 Core Editor Accessibility Improvements

X-comment from +make.wordpress.org/core: Comment on WordPress 5.5 Core Editor Accessibility Improvements

Accessibility Team Meeting Agenda: August 7, 2020

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, August 7, 2020 at 15:00 UTC.

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, August 7, 2020, at 14: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

Accessibility Team Meeting Notes: July 31, 2020

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.

This week we decided to continue the discussion around 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. focus outlines that started during the accessibility bug scrub right before our team meeting.

Rather than try to summarize it, I encourage those interested to follow the discussion in Slack.

We agreed to revisit this topic and discuss possible proposed solutions during our next extra bug scrub planned for Tuesday, August 4, 2020, at 15:00 UTC.

We also agreed to revisit the agenda items planned for today’s meeting during our meeting next week.

#meeting-notes-2

Accessibility Team Meeting Agenda: July 31, 2020

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, July 31, 2020, at 15:00 UTC.

  • Finalize the date and time for the extra pre-alpha bug-scrub.
  • Review our team meeting day/time and look at options to make it friendlier for folks across the globe.
  • Discussion: update the WordPress accessibility coding standards 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
  • 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, July 31, 2020, at 14: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

Accessibility Team Meeting Notes: July 24, 2020

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 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 marked as accessibility regressions

The first part of the meeting was dedicated to reviewing Gutenberg issues marked as accessibility regressions; it was a continuation of the bug scrub that had started an hour before. In the end, the team analyzed eleven issues and discussed which of them were considered as must-have to be included in WordPress 5.5.

The complete discussion about Gutenberg accessibility regressions (including items addressed during the bug-scrub) is 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/..

Planning of an extra pre-alpha triage session

Following the discussion we had two weeks ago about how to better address accessibility bugs in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and issues in Gutenberg, the team agreed on organizing an extra bug-scrub after WordPress 5.5 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. 1. The scope of the additional triage is to identify easier and self-contained tickets and issues to mark as good-first-bug.

The team agreed to separate the Friday bug-scrub from the extra once-per-releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. triage: half of it will be focused on WordPress Core tickets and the other to Gutenberg issues.

The suggested time for this extra bug-scrub is Tuesday, August 4th, 2020 at 15:00 UTC, but the team will choose the final date and time and the bug-gardener in charge of conducting the triage during next weekly meeting. If we can’t get through all tickets and issues in a single meeting, a follow-up will be planned.

Updates on WordPress Accessibility Day organization

Organization of WordPress Accessibility Day, the 24-hour event about WordPress and accessibility starting on Friday, October 2nd, 2020, is in progress, but the organizing team asked for some help.

They are looking for people to volunteer as Emcees, moderators, and monitors during the event, and a specific call for volunteers will go live in the next few days.

If someone wants to participate to a greater extent, please join the #accessibility-events channel, where discussion about the event is ongoing and a weekly meeting happens every Wednesday at 16:30 UTC.

#meeting-notes

Accessibility Team Meeting Agenda: July 24, 2020

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, July 24, 2020 at 15:00 UTC.

  • Review of Gutenberg issues marked as accessibility regressions and discussion about priorities and steps to take in view of 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. 1
  • Planning of the pre-alpha triage session to identify tickets to be labelled as good-first-bug
  • Updates on the organization of WordPress Accessibility Day
  • 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, July 24, 2020, at 14: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

Accessibility Team Meeting Notes: July 17, 2020

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.

Removal of aria-labels for links opening in new tabs

We discussed this Gutenberg PR that removed the aria-label property from links set to open in a new tab. It was previously suggested by the team to remove since the old implementation was doing more harm than good.

That said, a proper solution has yet to be implemented and we’d like to discuss all the alternatives with the relevant teams.

@ryokuhi volunteered to create a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket so we can follow up and start the conversation.

Create “Accessibility Statement” tool with features equivalent to Privacy Policy Tools

We also looked at this Trac ticket that proposes to mimic the tools already in place for creating Privacy Policy pages, but for Accessibility statements.

We discussed the pros and cons of such a tool and agreed that if done well, it can be a great medium to help spread accessibility awareness and education.

@sarahricker volunteered to summarize our discussion and add a comment to the ticket.

Initial implementation of <details>
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.

We then discussed this 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/ PR that looks to add a <details> block and agreed that we should follow the ARIA Authoring Practices implementation for an accordion component instead.

We added our feedback to the parent issue the PR is linked to.

#meeting-notes-2

Accessibility Team Meeting Agenda: July 17, 2020

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, July 17, 2020, at 15:00 UTC.

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, July 17, 2020, at 14: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