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

Accessibility Team meeting notes for 10 January 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 the next WordPress Accessibility Day planning meeting

The next WPAD meeting will be held on Tuesday, January 14, 2020, 16:00 UTC on the #accesibilty-events channel in the Make WordPress Slack (account required). Read this post for a summary of the kickoff meeting that took place on Tuesday, December 17th 2019.

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. Asia 2020 accessibility contributor table

At least one member of the accessibility team is planning on attending WordCamp Asia 2020 next month, this means we’ll be able to host an accessibility contributor table.

Action plan for 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 research work

We need feedback on the observations gathered from the research and testing the accessibility team did on the various focus handling flows in Gutenberg blocks.

The team wants to validate these observations before moving on to creating issues on the Gutenberg repository on 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/.

Focuses for 5.4 and 5.5

The team agreed to have additional bug scrubs to address tickets and 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.. More information on when these bug scrubs will happen will be shared as soon as possible.

For 5.5, the team would like to work on a bigger project, such as the idea of developing accessible color schemes for wp-admin.

Open Floor

Help is needed providing more information and media references on Joseph Karr O’Connor Wikipedia page. Joseph passed away last week. He was a former team representative and an outstanding member of the web accessibility community.

#meeting-notes

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

Meeting plans for remainder of December 2019

The team agreed to take a break from meetings and bug scrubs for the remainder of December 2019 and a such, today was our last meeting and bug scrub of the year.

The team was also reminded of the WordPress Global Accessibility Day initial planning meeting, which will be held on Tuesday 17 December 2019 at 16:00 UTC in the #accessibility-events 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.

Easier testing 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/ PRs with gutenberg.run

http://gutenberg.run is a service by @aduth that provides temporary live preview sites for Gutenberg pull requests.

This will allow us to view and test Gutenberg PRs without the need to have a local development environment set up and running. Testing and providing feedback should be much easier for a lot of us.

It’s important to note that http://gutenberg.run is a work in progress, and as such some bugs can happen. The project is open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., so if you want to report bugs or follow along on its development, you can do so in the project’s GitHub repository.

Status and follow up plans for the Accessibility Audit project board on 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/

The team was reminded of the Gutenberg Accessibility Audit project board on GitHub which was created after the WP Campus accessibility audit that was performed earlier this year.

We noticed how 60 issues have already been closed, 8 are in progress and 27 are still in the To do list.

Now that gutenberg.run is available, we hope that the team can provide the necessary testing and feedback and make some progress on these issues.

Updates on the team’s current projects

@joedolson updated the team on the progress that has been made on the research work of focus handling in Gutenberg blocks we started recently.

Joe noted that now that most of the initial research has been done, some patterns are starting to emerge and we’ve been able to identify predominant behaviors and oddities.

Joe will collate the list and ask follow-up questions to some of the testers for clarification. We’ll add screen-reader testing to the research so we can identify how each scenario is announced.

We also revisited the idea that came up recently of adding accessible color schemes to wp-admin. Now that we have access to the GitHub and SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. 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 repositories we are in a position to make progress.

The team agreed to come back to this project next year after the break.

Open Floor

On the topic of accessible color schemes, @steelwagstaff shared some previous accessible color scheme work done for PressBooks that should be useful to the team.

#meeting-notes

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