Accessibility Team meeting notes for 6 December 2019

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.

Proposed times for the Global WP Accessibility Day initial planning meeting

A set of dates have been proposed for the upcoming planning meeting for the Global WP Accessibility Day. Folks interested in participating are encouraged to join 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/. (requires registration) and vote for a date.

Advancing 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. Interface

At last week’s meeting, we brought up this Gutenberg GitHub issue that is exploring the current constrains of the block’s toolbar and is proposing some updates that will make it more usable and robust. Being a long issue that goes into a lot of depth, we agreed last week to give everyone some time to digest it and revisit the topic during this meeting.

Those who had time to review it shared their thoughts. The conversation also touched on process and how there’s still room for improvement when it comes to these kind of proposals.

Folks are encouraged to leave feedback and comments on the issue.

Updates on 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/ focus handling research work

We revisited the research work that started a few weeks ago on focus handing of Gutenberg blocks. The team made a lot of progress and we’ll revisit the topic next week once we’ve had more time to go over the results.

New Welcome Guide modal in Gutenberg

This pull request from the Gutenberg GitHub repo was brought up because there are still some implementation issues that need to be addressed.

It was suggested that the modal component be set with a role=dialog, and since we can’t predict what kind of content will live within the modal, a role=document be used for the content.

The team also discussed usability issues present on the modal. All this feedback has been summarized and added to the PR.

WAI-ARIA compliant custom select

While extensive accessibility testing has been performed on this component, there are still improvements to be made.

The conversation also touched on accessibility testing process and documentation and ways we could improve it. We agreed to explore the idea of creating documentation for baseline accessibility testing procedures and expectations.

#meeting-notes

Accessibility Team meeting notes for 29 November 2019

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.

Notice to discourage use of IE11

The team discussed this Trac ticket that proposes to encourage users, through a message or notification, to upgrade from IE11.

The team agreed that having a permanently dismissible notice is a good idea but we should however be mindful of folks who can’t upgrade due to work requirements or version of assistive technologyAssistive technology Assistive technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the technology needed to accomplish such tasks. https://en.wikipedia.org/wiki/Assistive_technology being used. Ending support for IE11 should be a separate issue.

Remove aria-label from links

We also discussed this GitHub PR that is attempting to fix a problem when creating a link 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 and is set to open on a new tab.

Currently, the link gets an aria-label with the link’s label and a string appended that indicates that the link will open in a new browser tab. The issue is that the appended string is not being set to the document’s language, but to the language wp-admin is set to.

The team agreed that removing the currently broken functionality to add the aria-label is good first step, but would like to see a solution implemented as well.

We think that making the string visible would be ideal, since all users would benefit from this piece of information. It should also be set to the document’s language, because this string will be used in a public context.

Advancing the block interface

This recent 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/ GitHub issue that explores refinements to the block toolbar was shared with the team for awareness. It’s a long read, so we’ll revisit the item next week once everyone has had time to digest it.

Global WordPress Accessibility Day

We revisited the idea of having a global WordPress accessibility day. This had been discussed earlier in the year and a spreadsheet for those interested in participating was created.

Since this was discussed a while ago, we ask those who had already signed up to confirm their participation, or remove themselves from the spreadsheet if they won’t be participating anymore.

Anyone who’s not on the list and wants to participate is welcome to add their details.

The organizing team will be coordinating to set up a planning meeting. Folks are also welcome to join the #accessibility-events 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

This week in WordPress Accessibility, September 4th, 2017

Transcript of the meeting

Agenda

  • ARIA roles in Underscores theme.
  • CodeMirror.
  • Automated 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) testing.
  • 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/
  • Open floor / Go crazy.

ARIA roles in Underscores theme

We removed ARIA roles from Underscores theme couple months ago. But WAI-ARIA 1.1 and HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. 5.1 specifications have been updated. Here is good overview of the ARIA changes in Firefox. This is the biggest change for ARIA roles:

<headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.> and <footer> elements will now only be exposed as header and footer, and banner and ContentInfo landmarks respectively, if these elements are direct descendants of the body tag, and therefore are scoped for the whole page.

In _s header and footer are not direct descendants of the body tag, they are inside #page wrapper. Discussion about this continue in Underscores repo.

Codemirror

It’s hard to create 100% accessible code editing tool. With Codemirror we are happy with two main points:

  1. Avoid keyboard trap inside code editor.
  2. Easy way to disable Codemirror.

We also looked at how Help text section could be easier to find in the Additional CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site.. Help text section is now auto-expanded when first opening the panel, when the CSS is empty or at its placeholder value.

We encourage everybody to test Codemirror, development is still in Github before CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. merge.

Automated accessibility testing

Automated accessibility testing is a big topic. @joedolson proposed four ideas where we could start:

  1. How will core builds be mounted so the DOM gets tested.
  2. What method will we use to execute tests.
  3. What tests will we execute.
  4. How much manual testing will we continue to do regardless of passed tests.

Gutenberg

Before the meeting there was Gutenberg bug scrub. In the meeting we mainly discussed about landmark regions.

Open floor / Go crazy

Me and Joe went to sleep, Andrea had something to eat 🙂

#meeting-notes, #weekly-meetings

This week in WordPress Accessibility, August 28th, 2017

Transcript of the meeting

Agenda

  • Handbook, progress so far
  • CodeMirror
  • 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/
  • Open floor

CodeMirror was moved up in the discussion by request of @samikeijonen.

CodeMirror

CodeMirror will be incorporated into WordPress 4.9 in theme and plug-in editing, the HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. text widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user., and the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. editor. Discussed how to provide access to Help for keyboard users who will need some instruction on how this will work from the keyboard. The 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/theme editors and the CSS editor have logical places to provide information, but HTML widget doesn’t have a place for this information.

Conclusion: WordPress needs an inline help implementation. Lacking that, we’ll use the Help tab to hold the information for now, with the eventual goal to implement inline help and move the information.

Handbook

Report: Work on the Handbook has started. Trying to write at least one topic per week. Discussed how to handle some complex topics, and agreed that where applicable, we’ll refer directly to external examples and recommend the most official example for a given specification. E.g. tab panels.

Progress on Handbook

Gutenberg

Simply Accessible has offered to provide support for developers on Gutenberg. Discussed effectiveness of this and ability to help with solutions. Problems mostly have to do with gathering consensus then finding somebody to implement. Tried to generalize how Simply Accessible can best be leveraged. Suggested they focus on keyboard interactions with blocks.

Discussed labeling some 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) issues as high priority to try and focus efforts.

@afercia commented that one coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. problem is that technical solutions have gotten decided without a preliminary accessibility evaluation which have had significant impacts on accessibility.

Open Floor

@rianrietveld will be on holiday for the next four weeks, and asked for a volunteer to lead meetings during her absence. @samikeijonen volunteered for at least next week’s meeting.

#meeting-notes, #weekly-meetings

IRC Meeting: September 25, 2013

Most of the time was spent discussing https://core.trac.wordpress.org/ticket/21334 3.7, grahamarmfield->helen, closed, Row actions are not always keyboard accessible. Helen Hou joined us for the discussion.

1. When mouse hovers over a page/post row in main Pages/Posts screen ‘quick links’ appear. Suggesting that they also are made available for keyboard-only users and screen reader users.

2. When using the QuickEdit panel the time/date controls have separate tabindex and no labels. Suggesting that the tabindex be removed from those controls, and that labels be used.

Discussion centered around the need to reduce verbosity for screen reader users, while still making the controls available to them.

It was decided to test the latest build and come back with a recommendation.

#accessibility, #meeting-notes, #team-reps