WordPress Accessibility Meeting notes for 25 October 2019

Meeting transcript on Slack

Update on WP 5.3 Progress

@audrasjb reported that reactions from the French 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/. team on admin CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes have been pretty good. Feedback also from Jetpack/WooCommerce teams who’ve fixed a few minor things, but reactions generally positive.

@afercia reported that an un-named large 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 had to fix a few minor glitches related to custom form controls. Also noted that these changes cause some issues with custom selects such as select2 or chosen.

Continuing work on CSS: #48420

Ticket to standardize form control heights and alignments. Patch already exists, but didn’t make it in time for RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.. These problems have existed since WP 3.8; in WP 3.7 form controls were aligned consistently.

Need some feedback from design to make decisions about inconsistent border radii 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/.

Agreed to schedule this for 5.4-early, with the possibility that we’d try to push it into 5.3.1.

Update on 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) at WCUS

@nataliemac Reported that @rianrietveld and @nrqsnchz would be helping her in her workshop, which is just finishing up prep.

@nrqsnchz reported that he’s got a plan for format and activities at the contributor table. @nataliemac will also be at the contributor table.

Proposal: cancel team meeting for 1 November

We’ve routinely cancelled meetings that occur during WCEU or WCUS, and we’ll do that for this date as well. Many members would be unable to attend.

Proposal: Change team reps at meeting 8 November

Team reps haven’t changed since October 2018; we’ll plan to vote in reps at meeting on 8 November. @audrasjb will make a post to announce this. Existing reps are still eligible to run; there are no term limits.

Open Floor

@afercia would like to remove Segoe 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. from the system fonts stack per #48423. Reasoning: Segoe UI has significantly different leading boundaries from other fonts, creating layout issues in vertically centered contexts like input fields.

Agenda for Accessibility Team Meeting for 25 Oct 2019

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 25 October 2019 at 15:00 UTC.

  • Update on WP 5.3 RC2.
  • Continuing work on admin CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. (#48420)
  • Accessibility at WCUS update
  • Proposal: Cancel meeting for Nov. 1, 2019 due to WCUS
  • Advance notice: Proposal to discuss team representatives for the next year at Nov. 8th, 2019 meeting. If you have thoughts on the topic or interest being a team representative, please plan on attending that meeting.

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 25 October 2019 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 for Accessibility Team Meeting for 8 November 2019

Note: there will be no 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 1 November 2019.

This is the proposed agenda for the weekly accessibility team meeting on Friday 8 November 2019 at 15:00 UTC.

  • Discuss & Elect Accessibility Team representatives for next year.
  • Update Team & Contributor profile badges (last updated 12 April 2019).
  • WCUS report
  • WordPress 5.3: pre-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 comments & status.

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 8 November 2019 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).

WordPress Accessibility Meeting Notes for 27 Sept 2019

Meeting transcript on Slack

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

31 open tickets in 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) focus remaining. There are a total of 138 open tickets in the 5.3 milestone. 6 tickets relating to contrast and focus have been reopened for continuing work. 32 tickets in the accessibility focus have been fixed.

CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. Changes related to link focus style

After the focus and contrast changes, the link focus style is a dotted outline. This is a regression against the previous 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., which used a blue glow focus. Discussed options and agreed that switching to a solid outline and adding and outline offset of 2 pixels will improve. Also noted that the admin nav menu is using the same color as the main focus, needs to be reversed.

This change will also need to be ported to 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 that may not be able to happen by 5.3.

Off-agenda: discussion on whether we have time to complete changes.

@karmatosed raised a question whether we should focus on moving continuing changes to 5.4 rather than attempt to complete this for 5.3

After discussion, generally agreed that the continuing changes for focus and contrast are minor tweaks, and while there are a large number of tweaks, we should have time to complete them.

Noted that while 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. status closes trunk to new enhancements, tweaks to the contrast changes are bugs, and can continue through the RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. stage.

Next accessibility bug scrub

Next bug scrub will happen on Tuesday 1 October 2019 at 16:00 UTC 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.

Twenty Twenty Status

Twenty Twenty has 9 accessibility labelled issues awaiting attention. @poena raised the menus as the biggest concern, needing review. There’s a PR by @acalfieri waiting to land on the menus – we’ll take a look at it after this is finished.

New EU accessibility standards

Note: on 23 September 2019, the first stage of the European Union directive on accessibility of websites and mobile applications came into force. This stage requires all public sector new websites to be accessible. Existing websites have until 23 September 2020 to be made accessible; all public sector mobile apps have until 23 June 2021.

The EU directive uses 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 at level AA as their reference for a harmonized standard.

After WordPress 5.3, we will discuss updating the WordPress accessibility standards to WCAG 2.1. This was last discussed in October 2018, and was inconclusive.

WordPress 5.3: Accessibility focus progress report

For reference, full WordPress 5.3 release schedule is available here.

TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets progress reports and next steps

For now, milestone 5.3 contains 63 accessibility focused tickets:

  • 32 tickets are closed as fixed
  • 31 tickets are still open, distributed as follows:
    • 23 defects/bugs
    • 8 blessed tasks/enhancement, reopened for iteration during 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. cycle

For easy reference, all admin interface CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes are now grouped under the “5-3-admin-css-changes” keyword.

Next steps

  • Tuesday 1st, October:
    • Extra bug scrub scheduled at 16:00 UTCStart to punt defects/bugs without enough progress or still waiting for patch/testing/feedback
  • Friday 4, October: bug scrub and weekly meeting
  • Thursday 10, October (5 days before 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):
    • Milestone should be cleared
    • All the approved changes should be ready for 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.

Any help on the remaining tickets is welcome, including testing current patches. Discussion about tickets/patches/current implementation can happens at any time on the #accessibility channel in 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).

Twenty Twenty 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) focused issues

For now, Twenty Twenty has 20 accessibility focused issues:

Any help on the remaining issues is welcome.

+coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
+make.wordpress.org/core

#5-3

Accessibility Team Meeting Agenda: 27 September 2019

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 27 September 2019 at 15:00 UTC.

  • Progress on WordPress 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets (and next bug scrubs)
    • Discuss CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes related to links focus style (it’s now just a dotted outline)
    • Links focus style on the admin menu needs improvements (barely visible)
    • Twenty Twenty
  • Upcoming Bug scrubs
  • Information: 23 September 2019 was the first stage of the European Union directive on accessibility of the websites and mobile applications of public sector bodies

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 27 September 2019 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).

#5-3

X-post: Core Widgets: new aria-current attribute in WordPress 5.3

X-comment from +make.wordpress.org/core: Comment on Core Widgets: new aria-current attribute in WordPress 5.3

WordPress Accessibility Meeting Notes for 20 Sept 2019

Meeting transcript on Slack

Open Floor

There was no set agenda for this meeting.

The meeting opened with a discussion of ticket #30180. The ticket, while not of itself a crucial task, was a kicking off point for a deeper conversation about trying to work more effectively across teams.

This was a complicated conversation, so in this summary I aim to do my best to convey the essence of the conversation, primarily focusing on the experience from within 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. For a detailed picture, please read the meeting transcript.

The overall point was the difficulty the accessibility team in specific – and all teams in general – have had in making progress on tasks that fall across other team’s responsibilities. This is particularly difficult in the more specialized areas of code, such as the Media Library, where specific knowledge of the inner workings are more rare.

The problem we would like to solve is, at root, the challenge of balancing goals with labor in a realistic manner. We, as a team, have very limited time that can be committed to any given task as well as having expertise primarily in accessibility, which may not benefit us mechanically when working in a specific idiosyncratic technology. To help meet goals, we have tried to work with other teams to delegate responsibility on tickets to people with more specialized experience, while remaining available to consult on the results.

The experience we have had with this has been poor, leaving us feeling that our only ability to accomplish goals is the technical tasks we have the bandwidth to complete ourselves. While many people do step forward and help, this doesn’t result in an overall feeling of forward momentum.

Among the challenges shared are the fact that many contributors to the project cannot plan their time effectively due to the lack of a structure 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. schedule. While employees of a company will have their hours structured such that they can dedicate the necessary time to a project after that project is scheduled, voluntary contributors inevitably have other responsibilities and commitments. Short notice of a release schedule does not allow those contributors to arrange their availability such that they can contribute in a healthy manner.

The meeting discussed four separate major challenges:

  1. Meeting specific goals for the accessibility tickets planned for WordPress 5.3.
  2. Communicate more effectively across teams.
  3. Component maintainence priorities.
  4. Release scheduling and the budgeting of goals over time.

It is important to us, as a team, to state that this is a problem we see throughout the WordPress project, and is not unique to this release or to our team. We don’t feel that these problems reflect individual failures; it’s the result of a systematic failure stemming from a lack of collaborative processes and insufficient opportunity to plan during the times between releases.

Better long-term planning and better release schedule pre-planning to set goals and define the capabilities across teams would be a critical step in making each team be more capable of meeting their individual goals.

The Accessibility Team would like to continue to move forward to work across teams to make this a better experience. We’re continuing to explore ways to improve the process through cross-team collaborations and shared meetings, and hope that we can all collaborate more effectively with improved processes.

Accessibility Team Meeting Notes: 13 Sept. 2019

Meeting transcript on Slack

Update on 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Tickets & Upcoming Bug Scrubs

There are now 49 open tickets in the 5.3 milestone report. Some of these are close to commit, a few more have patches but need finalizing. Still some tickets without owners.

Scheduling an additional bug scrub for Tuesday 17 September 2019 at 15:00 UTC to work through them further.

Review: 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/ Navigation/Edit Mode.

The team discussed the practical experience of using the mode switching in various AT we’ve tested. The call for testing did not yield any responses.

Several people noted that the new 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. works quite well for keyboard users.

For screen readers, it’s more mixed: requires double escape to exit edit mode, the experience with NVDA/Firefox is buggy. NVDA has some known issues right now with Firefox, so this should be tested with FF 71 Nightly, which is anticipated to fix some issues.

Overall:

– It’s a good improvement for keyboard 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) and some assistive tech.
– Doesn’t work well with Firefox and NVDA: this needs to be investigated and addressed before 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..
– Add audible messages, e.g.: “WordPress edit mode activated” and “WordPress navigation mode activated”.
– The button text needs to communicate the available action. 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. type is not an action. Should probably be ‘Edit [block name]’ That would be much more clear for all users.

Twenty Twenty: Should main menu and search be ARIA modal dialogs?

The accessibility team discussed ticket #80.

Team agreed that yes, this is an appropriate choice and would make a good model for implementation of an ARIA modal for menus. The source order should be retained in logical order rather than moving the menu source elsewhere so that child theming isn’t made excessively complicated.

Feedback on Gutenberg Proposal for Content Block Areas

Commented that the use of modes has potential for good UI, as discussed for Navigation/Edit in the editor, above.

No other new comments, other than reiterating that the 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. continues to be a concern in Gutenberg.

Open Floor

  • Discussed accessibility of 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/. threads. They are now navigable and readable. Notifications are limited, but this is also true for all other users. Slack threads can be used, but (as always) are not the right place for primary topics of conversation.
  • @nataliemac needs volunteer teaching assistants for WCUS.

Accessibility Team Meeting Agenda: 13 September 2019

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 13 September 2019 at 15:00 UTC.

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 13 September 2019 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).

#5-3, #gutenberg, #twenty-twenty