Rian Rietveld 3:42 pm on July 31, 2017
Tags: accessibility ( 3 ), summit 2017

Accessibility Team Community Summit Notes

Review and update 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) coding Standards

Considering the shift towards JS-based interfaces, we should consider to review and update the accessibility coding Standards.

Announcing dynamic content

We have:

wp.a11y.speak()
a non WP dependant solution: a11y-speak()

For complex interaction wp.a11y.speak() may not be the best solution. When in doubt discuss solutions with the 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) team.

Resources

Accessibility handbook has not enough recourses
How to handle ARIA for screen readers
Fact is that traditional web apps reload gives feedback, that JS only apps can not provide. Are there tools we can leverage to help standards adoption?
JS interfaces still should be build with semantic 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.
ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. tends to use divs, but that’s not React itself, that’s bad programming
10UP now released a complete library for WP . It’s in GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/, so this is expandable
For the handbook we should refer to existing libs or someone to build them
There is a need for good information and components that are accessible

Workflow

Important: The a11y team needs to do more teaching and sharing, instead of fixing things themselves. Specifications within accessibility tickets should contain code examples

We should share accessible components
Is it possible to abstract cases and give examples of good practices
Part of the standard tooling should be testing software react/axe
Give 10 point list of things to check
We should publish about for example audio feedback, focus management, ARIA

Discussion

Should we 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. things? Are we okay with keeping that statement: 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.0.
Have things met the standard? Probably not.
What happens in tickets if it’s raised that it doesn’t work for WCAG?
How do we help in that situation? Someone should review major patches.
We don’t want to be a blocker. Accessibility has purification levels. Shoot high, but compromise.
What happens when someone blocks a ticket. It depends, no one really has.
Where’s the acceptable bar? Should work with keyboard only (arrow keys, etc. too). Semantic elements too. Labeled. This is a baseline expectation.
Struggled to know when/where discussions take place sometimes.

How to involve more developers with accessibility tickets

This is about how to bring more people into this team?
Why do some people stick around and others not stick around? Interesting, important. Time is valuable.
How do we maximize people’s time? Maybe story points, like in Scrum.
People don’t know how best to contribute.
Something like “good first bug” but for accessibility.
Short interview/onboarding for people interested.
Better way to manage priorities. Maybe spreadsheet to try it?
Non-CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. items: Testing, theme reviews, tickets, documentation, support, education
Maybe use more keywords for this? Make list public so people know.
Best way to address is when teams ask for help.
Accessibility slows progress down when it comes at the end.
We need a mental shift of where accessibility fits. We need to let them know they can do it.
Works properly vs. get working.
Get people from outside community. Make a list and ask. Things they can do and achieve. Make a list of people we could bring in.
MITs: Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., 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/, Media Views, Unified Search – Who?

How to proceed with the handbook

Make two pages: Tools and resources. Also, how to get involved.
Would potentially be easier to maintain.
Has been hard to get done because everyone is busy.

Good examples of ARIA, etc.

How to test resources.
List of what we’re working on.

What topics?

ARIA
Keyboard accessibility
Color contrast
Semantics

How should we divide topics?

By topic or need? Probably both.
Try to find resources that go beyond accessibility as it relates to disabilities.

Who can work on this?

Make small workgroup
Do Google Spreadsheet

Summary on make/accessibility

Takeaways from Paris

#accessibility, #summit-2017

Tammie Lister 7:03 pm on July 26, 2017
Tags: design, summit 2017

Design Team Community Summit 2017 Recap

The design team made several posts from the focus team sessions and we are sharing them here as part of the recap. Each of these contains more details about what occurred and the decisions made on the day:

#design, #summit-2017

Ipstenu (Mika Epstein) 11:25 pm on July 25, 2017
Tags: plugins, summit 2017

Plugins Team Community Summit 2017 Recap

While a recap of our various talks (including hallway) have been collected in the link below, our primary conversations revolved around the following:

New Reviewers: There are some technical issues we’re working on that must be resolved before we can add new people. They include security ones, but also our rather archaic SupportPress tool. This is the biggest and has a lot of small steps and some weirdly large ones (like the idea of a dashboard, automated security checks, and more) so it’s not going to be anywhere near as fast as I want… Well. Release and iterate.
How to safely publicly disclose 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 closures (without dog shaming developers). This is logistically something to be concerned over, as the last thing we want to do is make WP and users a bigger target.
How to allow frameworks with the least pain for end-users as possible.

In order to meet our goals, we’re going to be discussing the improvements on many fronts at once, and I’m planing out times and dates for meetings for everyone to come and talk about one at a time. Think of it like town-halls. You can read the details of everything in the linked post:

2017 Community Summit Notes

#plugins, #summit-2017

Rocio Valdivia 4:27 pm on May 23, 2017
Tags: attendees, summit 2017

WordPress Community Summit 2017: Attendees and Agenda Summary

The 2017 WordPress Community Summit (CS) is almost here. It will take place on Tuesday, June 13th and Wednesday, June 14th, the two days before contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at 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. Europe in Paris, France. All attendees should have received an email with venue and other important details. If you haven’t received such an email, or if you’re not able to attend, please let us know asap at community@wp-europe.org

We would like to remind all teams and contributors the purpose and goal of the Community Summit:

“The main purpose of the summit is to move the WordPress project forward before and after the event, with the event being a milestone in a larger set of work.

With this main goal in mind, we’ll touch base with all team reps to figure out which of the topics proposed can be handled beforehand, and come up with topics that would be:

1) of importance to the project as a whole

2) would benefit from cross-team collaboration

3) will leave us in a better position than when we started”

How Attendees Were Selected

Unlike WordCamps or Contributor Days, the Community Summit has limited capacity both because of the venue size and the type of work that is required. The list of nominations was reviewed by a committee composed of experienced contributors, chosen for their broad overview of the project and its community: @aaroncampbell @petya @chanthaboune @helen @ipstenu and @_dorsvenabili

The committee reviewed the list of nominated contributors that we received from the original call for nominations (more info on the process and criteria).

In voting on each person, we kept several things in mind:

Active contributions to the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ project and that specific team
Influence/reach in the broader WordPress ecosystem (not just within WordPress.org)
Employer (to prevent an overwhelming presence by one or few select companies)
Location (to have a decent international contingent and not be solely US-focused)
Differing Points of View (to ensure minority voices can be heard)

Attendees

The list of attendees was formed from all those who were invited and confirmed their attendance:

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)

@afercia @rianrietveld @davidakennedy @mor10 @samikeijonen

CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.

@schlessera @borekb @danielbachhuber @miyauchi

Community

@andreamiddleton @andrescifuentesr @iaaxpage @mbigul @courtneypk @thewebprincess @jennybeaumont @emanuel_blagonic @francina @mayukojpn @hlashbrooke @ibonazkoitia @miss_jwo @kcristiano @lanche86 @travel_girl @markgazel @imath @paolal @remediosgraphic @sptorabi @_dorsvenabili @mahype @thabotswana @00sleepy @xibe

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@adamsilverstein @boonebgorges @chriscct7 @desrosj @dd32 @iseulde @flixos90 @jjj @joehoyle @joemcgill @joen @johnbillion @kadamwhite @matt @marcs0h @matveb @voldemortensen @azaozz @swissspidy @rmccue @stevenkword @westonruter @peterwilsoncc @codebykat

Design

@empireoflight @folletto @michael-arestad @melchoyce @saracannon @sonjanyc @karmatosed @liljimmi

Docs

@atachibana @kenshino @milana_cap

Hosting

@aaroncampbell @andrewtaylor-1 @ddsucurinet @joostdevalk @mikehansenme @mikeschroder @stephdau

MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.

@tellyworth @coreymckrill @pento @iandunn @obenland @mapk

Mobile

@catehstn @mbiais @kwonye

Plugins

@ipstenu @otto42

Polyglots

@glueckpress @chiragpatel @carl-alberto @ocean90 @imnok @lasacco @openstream @petya @tacoverdo @vannkorn

Support

@bethannon1 @cristianozanca @imazed @macmanx @clorith @sergeybiryukov @zoonini

Themes

@acalfieri @grapplerulrich @sakinshrestha @ionutn @poena

Training

@wpaleks @chanthaboune

Summary of Community Summit Agenda

Day 1 (Tuesday, 13 June):

Individual team and cross-team discussions* which need in-person discussions

Day 2 (Wednesday, 14 June):

Continuing cross-team discussions*

Writing recaps for the make/summit p2 blog

Proposed Discussions

A few months ago, each team proposed topics that need in-person discussion ( List of proposed topics ). If teams need to amend or update their list, post any changes as a comment, please. The deadline is Friday, June 9th, at which point we will close comments and publish the list of topics for WordPress Community Summit 2017.

Travel Assistance Program Applicants

All guests, selected for the travel assistance program have been contacted via email by the organizing team, who will follow up in the next few days. Thanks so much to all our sponsors for making this Travel Assistance program possible!

#attendees, #summit-2017

Rocio Valdivia 2:52 pm on January 26, 2017
Tags: 2017, summit 2017

Community Summit 2017

The 2017 WordPress Community Summit (CS) will take place on Tuesday-Wednesday, 13-14 June, before 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. Europe in Paris, France (the venue will be in the XV district of Paris).

The CS is now in the planning stages, and this site will grow in the coming weeks to include information for attendees as well as event sponsorships, agenda, etc.

Based on the feedback and discussion p2 post (https://make.wordpress.org/community/2016/11/03/wordpress-community-summit-2017/) about a new approach for the 2017 CS, these are the next steps for every make.wordpress.org contributor team.

Next Steps:

Team reps, please post the following in a comment to this post.
The deadline is March 3rd, 2017.

A list of topics/issues which are relevant for the progress of the team and the WordPress 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. project as a whole, prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion.
A list of representatives to attend the Community Summit (not limit-determined, but please keep in mind that our venue capacity limit is of 130 attendees), with selections based on several factors, including: representation of a wide, diverse range of opinions (based on the agreed-upon topics selected by each team), diversity, inclusion, and activity of the contributors.
One or two contributors who are willing to help with the organization of the event: posts, communication, travel assistance, finding sponsors, etc. The intention of this approach is to propose a more open and team-focused Community Summit with transparent participation from all active contributors and reps of each team. This way we can hopefully anticipate barriers and cross-team difficulties that might come up, and avoid them.

Notes:

The contributors who are willing to work on the summit (referenced in #3, above) will join the WCEU team working on the Community Summit. If there are not enough contributors available to help organize, the WCEU team has volunteers available to help.
We’ll work on finding sponsors to cover travel expenses for those contributors who face financial barriers. We’ll open a call for CS sponsors in the next days.
For those teams with sub-teams, for example, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., security, etc. the representation of these sub-teams will depend on the list of discussion topics provided by the team.
In the next days, we’ll open an application form for people who aren’t invited as contributors, but who represent other interests within the wider WordPress Community.

—
Pinging all team reps:
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): @rianrietveld, @joedolson, and @afercia
Community: @francina and @hlashbrooke
Core: @jeffpaul, @helen
Design: @melchoyce, @karmatosed, @joen, @michaelarestad
Documentation: @kenshino
Test: @designsimply
Hosting: @mikeschroder
Marketing: @rosso99
MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. (WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Site): @samuelsidler
Mobile: @astralbodies, @rachelmcr
Plugins: @ipstenu
Polyglots: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
Support: @macmanx
Themes: @jcastaneda, @grapplerulrich
Training: @bethsoderberg
TV: @jerrysarcastic, @roseapplemedia
Cli: @danielbachhuber

#2017, #summit-2017