Accessibility Team meeting notes – April 3, 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.

Help testing the WordPress Auto-updates Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.

@audrasjb and @pbiron asked the team for help testing the Auto-updates Feature plugin. This is 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 aims to provide automatic updates for plugins and themes feature as an opt-in feature.

You can find more information about the plugin on the plugin’s page and report any issues you come across to the plugin’s GitHub repository.

Statement on the use of Crowdcast for WP community events

We discussed the Community team’s consideration to use the Crowdcast streaming platform for online events. Knowing how inaccessible Crowdcast is, the Accessibility team wants to help the Community team find better alternatives. @joedolson wrote this post with recommendations for alternative setups and suggestions to make online events more accessible.

Open Floor

Team meeting time change due to DST

@ryokuhi reminded the team that we haven’t made a decision about moving our meeting time to adjust to DST. This is a change we’ve done in the past, and that other teams have done as well.

The consensus from team members present was that it was OK to move the meeting time, but we’d like to give folks who could not attend the chance to have their say.

Please let us know in the comments of this post if you are in favor of or against moving the meeting time an hour earlier to adapt to DST.

We will be making a final decision during our meeting next week.

+make.wordpress.org/core/

#meeting-notes

Accessibility Team meeting notes – March 20, 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.

Discussion and next steps on the team’s position about the new default full screen mode in the editor

Continuing the discussion from two weeks ago, the team agreed to formulate in writing our position opposing this change and the accessibility implications it will have.

@audrasjb volunteered to start a document to summarize our position.

Suggest follow-up tasks and improvements for the Table 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.

The team discussed and agreed to reopen this issue about missing important features in the Table block.

@joedolson volunteered to reopen and summarize what still needs to be done.

Discussion of the new permalink 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.

We discussed this issue about improvements to the permalink UI in the block editor. We feel the new UI works pretty well now and we’d like to see the inaccessible one be removed.

@nrqsnchz will pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the issue and request for the removal of the old UI.

#meeting-notes

Accessibility Team meeting notes – March 6, 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.

Discussion on the accessibility implications of the recent change to the full-screen mode in the editor

The team discussed the recent change to the full-screen mode in the editor. There is a general concern about the usability and accessibility implications this new default setting will have. In particular, this change potentially violates 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/.’s success criteria of Consistent navigation and Consistent identification.

@audrasjb volunteered to summarize the team’s feedback and create an issue on 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/’s 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/ repository.

Planning for the upcoming start and end of daylight saving time (DST) in some countries and regions

The team agreed to not change our meeting times for the time being. We’ll revisit this topic and adjust if necessary once all countries and regions have changed DST observance.

#meeting-notes

Accessibility Team meeting notes for February 21, 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.

Discussion on the Navigation MenuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. 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. testing

A few weeks ago, we started doing a11y testing on a new navigation menu block in Gutenberg. @nrqsnchz will be moving the results of these tests into 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/ issues in 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/ repository.

It’s important to note that the release of the navigation menu block was postponed.

Discussion of team involvement in Gutenberg development

We continued the discussion from last week regarding the team’s participation in the Gutenberg repository in GitHub.

There was a general consensus that being a small team, our time and bandwidth are limited. That being said, we’d still like to add a couple of items to our team process to try to mitigate this.

We agreed to start raising two Gutenberg issues that need accessibility feedback each week during our team meeting.

We’ll also look at adding a 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/. – GitHub integration to our team channel that posts issues that need accessibility feedback. We’ll give this integration a try and keep it if it’s working, or remove it if we find that it adds to much noise to our channel.

Another idea that was suggested was to add an additional Gutenberg-specific bug scrub session to our meeting schedule. This could be weekly, or perhaps every two weeks. Would you be interested in participating in these additional triage sessions? We ask members of the team to add their comments and suggestions in the comments of this post.

Improve the small user sub window at the right corner on the admin bar

We discussed this Trac ticket about usability issues of the ‘My account’ dropdown menu (also known as the ‘Howdy fly-out’) in wp-admin.

The team agreed that accidental triggers are common with this menu, and argued the importance and relevance of its contents.

@danihooven, @joedolson, and @afercia (a.k.a. ‘The Howdy Force Team’) agreed to continue researching this ticket and will be following up.

#meeting-notes

Accessibility Team Meeting Agenda: February 21, 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, February 21, 2020, 16:00 UTC.

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday, February 21, 2020, 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).

#meeting-notes

Accessibility Team meeting notes for February 14, 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.

Discussion of the updated button component in 5.4

We discussed a recent update introduced to the Button component in 5.4. The team agrees that the implementation of fixed heights in buttons will break accessibility. Furthermore, this goes against the recent CSS changes introduced to wp-admin in 5.3

This topic led to a discussion about processes, the pace of development 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/, and communication between teams. We agreed to come back to this concern next week, and address how, if possible, the Accessibility team can be more involved in the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository.

Feedback on the TabPanel component

We discussed this issue in the Gutenberg repository that requires accessibility feedback. A decision needs to be made in terms of how keyboard navigation should behave in a tabbed interface. We currently implement custom navigation for the tabs located in the editor inspector (Gutenberg sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.), while the WAI-ARIA Authoring Practices recommend a different approach. A summary of our feedback will be posted on the issue.

#meeting-notes

Accessibility Team meeting notes for February 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.

Discussion on the accessibility status of 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/ sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.

Discussion continued from last week on the topic of the accessibility status of the Gutenberg 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. inspector (sidebar).

The team had a very productive discussion that addressed the longstanding accessibility issues, recent improvements, and suggestions for solutions.

The team agreed to work together on a proposal that described the problem, suggests needed structural changes, and provides visual concepts.

Once 5.4 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, @joedolson, @afercia, and @nrqsnchz will collaborate to create the proposal.

Status update on 5.4 tickets

@audrasjb shared the status of the accessibility tickets in the 5.4 milestone in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. At the time of writing, there are 36 in the milestone, of which

  • 5 are closed as fixed
  • 4 are open and tagged for commit

Because Beta 1 is planned for February 11, the next 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) bug scrub (February 10, 2020, 17:00 UTC) will most likely focus on punting tickets for future 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..

There are still a few tickets that could be worked on and still make it in. Help on moving these forward is much appreciated.

#meeting-notes

Accessibility Team meeting notes for January 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.

Incorrect cursor used on buttons

The accessibility team has made a final recommendation on this ticket from the WPCampus accessibility report. The pointer cursor should be reserved for links, and an affordance for buttons can be communicated in other ways, such as noticeable hover and focus styles.

Disabled button doesn’t look disabled

The team also shared their recommendation on this ticket about disabled button styles. Because contrast requirements don’t apply to disable interface controls, we don’t have any issues with the design team making a call on changing this.

Video 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. settings for alternate sources

The team agreed to have a more broad-ranging conversation about the accessibility of navigation to and from the block inspector (sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.) in 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/. We’ll continue this discussion at next week’s meeting.

Feedback on the Navigation block

Members of the team are encouraged to try out the Navigation block in Gutenberg and provide feedback. We’ve created a spreadsheet to collect everyone’s results.

#meeting-notes

Accessibility Team meeting notes for January 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.

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

@audrasjb has organized a schedule to run additional bug scrubs in preparation for the 5.4 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.. Last week we were at 40 accessibility focused tickets still open in the milestone, and today we are at 36 open tickets.

We were all reminded that 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 is planned for February 11, 2020, and it is our deadline for committing patches into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

The next bug scrub is planned for Tuesday, January 28 at 17:00 UTC.

Update on the last WPAD planning meeting

Last week we held out third planning meeting for the WordPress Accessibility Day in the #accessibility-events channel in Slack. The team reports that the event organization is taking shape, and we’re considering September 26, 2020, as our intended date.

We’ve considered other WordPress events and mayor global holidays to define this date. That being said, we’d like to let it sit for a couple more weeks in case we’ve missed an important event or holiday.

Big thanks to @joedolson and everyone else who’s volunteered for the organizing team.

Please head over to the #accessibility-events channel in Slack to find out when then next planning meeting will be.

Follow up of 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/ 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 project

Work is underway, and the next steps are converting the team’s observations into actionable 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/ issues in the Gutenberg repository.

Help with testing the navigation block

The design team has asked for our help with performing accessibility testing on the navigation block in the editor. @nrqsnchz will coordinate a document where those available to help can add their feedback and observations.

#meeting-notes

Accessibility Team meeting notes for January 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.

Summary of the second WordPress Accessibility Day planning meeting

Earlier this the week we had our second planning meeting. Planning is well underway and the team has reached out to outside sources for help in order to make some key decisions.

The proposed dates for the next meeting have been posted in the #accessibility-events channel in 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/..

Dates for the upcoming 5.4 bug scrubs

In addition to our weekly bug scrub that happens every Friday at 15:00 UTC, we will be facilitating an addition bug scrub meeting on Tuesdays at 17:00 UTC, to address all TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets and 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/ issues for the 5.4 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..

Continue conversation on 5.5 focuses

As previously discussed, the team would like to start planning and working on our focuses for the 5.5 release. It’s been suggested we start work an accessible color schemes for wp-admin and start looking at the Full-site editing work that is ongoing in the Gutenberg repository in GitHub.

#meeting-notes