- Tickets for 4.8
- A11y 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) Tasks tickets
- Testing Gutenberg 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 others?)
- Tickets for Future Releases
- WCEU Contributor’s day
Andrea Fercia @afercia
Sami Keijonen @samikeijonen
Joe Dolson @joedolson
Trisha Salas @trishasalas
…and others possibly lurking
Tickets for 4.8
- tag cloud widget 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.
- custom logo alt attribute fallback
Both of these tickets are very close to commit.
@flixos90 dropped in during the meeting to say 38768 is done! 🎉
@afercia is currently fixing the tests for the custom logo alt attribute, thanks to @flixos90
@afercia helped to define the a11y-task tickets for us.
- A11y-task tickets are more related to a11y “topics”. (infinite scrolling, proximity, placeholders, CSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. generated content, etc)
- A11y-task tickets have an educational purpose 😀
- A11y-task tickets are something we don’t have the resources to address right now, but something we should talk about with other people, to increase awareness.
- A11y-task tickets are something to point people to when they ask about big a11y pending issues… hey look, there’s this Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. report you can have a look at.
- A11y-task tickets are something that should be brought to other teams attention (Design Team, for example)
- A11y-task tickets can be used as tracking tickets for separate smaller tickets.
Current A11y-Task Tickets
Everything needs to be tested, from the most basic text operation to the most complex interactions. For example: navigation in text with the keyboard, select text, select all, etc.
Installing the plugin 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 is very easy if you already use VVV and are familiar with GitHub 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/
See instructions for installing the plugin here: https://github.com/WordPress/gutenberg/blob/master/CONTRIBUTING.md
The plugin is not complete yet, but feedback should be given as soon as possible.
As a reminder: today is May 22nd and the Gutenberg deadline for a first 1.0 version is the end of June, as far as I know.
There are already several issues open on GitHub with the `accessibility 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)` label.
Discussion about tickets for Future Releases will be put on hold until we are more comfortable with the state of accessibility in Gutenberg.
The WCEU Committee has requested that each team come up with a list of goals due by June 9th for contributor day.
@sami.keijonen asked how we should prioritize and organize tasks given that we will have 30-40 people in attendance.
@joedolson mentioned “Training is frequently the most valuable part of contributor days – just trying to get people better educated about a11y. Getting a patch done is nice, but getting 40 people to know a11y better has more long-term value. I’d suggest segmenting the group according to experience, and have different plans for groups with more or less experience.”
The plan is to do both workshops and training along with identifying some simple tickets to have ready.
Homework for the team is
- Have a list of goals ready for next week (5/29/2017)
- Identify some ‘good first bug’ accessibility tickets