WordPress.org

Make WordPress Accessible

Tagged: weekly meetings Toggle Comment Threads | Keyboard Shortcuts

  • Trisha Salas 2:26 pm on April 27, 2017 Permalink |
    Tags: weekly meetings   

    Week in WPa11y – April 24, 2017 

    Topics of Discussion

    • Settings API project
    • Gutenberg editor plugin
    • Browser support changes
    • Screen reader text PR
    • Tickets
    • New Widgets to test

    Settings API

    https://github.com/wpaccessibility/settings-api-enhanced

    The current approach involves a redesign of the settings pages that is being discussed with some members of the design team.

    The next step is to process the thoughts @helen gave use on the CSS naming conventions. See: https://github.com/wpaccessibility/settings-api-enhanced/issues/6#issuecomment-294011891

    Gutenberg Editor Plugin

    https://github.com/WordPress/gutenberg

    @afercia recommended that we install and test the plugin. Instructions are here: https://github.com/WordPress/gutenberg/blob/master/CONTRIBUTING.md

    Note that it is not a conventional plugin so there are some specific steps to follow.

    @afercia has submitted a few issues based on the mockups but real (a11y) testing has yet to start.

    Changes in Browser support

    https://make.wordpress.org/core/2017/04/23/target-browser-coverage/

    We discussed how the browser support changes would impact the screen reader text PR. @sami.keijonen said we should not use our time so much of finding things to remove at this point. But test new things like settings API and editor and make changes as needed.

    Screen reader text PR

    https://github.com/wpaccessibility/a11ythemepatterns/pull/10

    @ffood submitted a PR to update the screen reader class in the A11y Theme Patterns repo in Github.

    There was some discussion about updating the class in core as well.

    We agreed to merge the PR and also open a new issue in core to modernize the class. The changes in core should take into account end of support for IE 8-9-10

    Tickets

    Two tickets were closed this week.

    Widgets

    There are 2 new widgets to test

    Next meetings in Slack

    • Team meeting on Monday, May 1 at 17:00 UTC in the Slack #accessibility channel.
     
  • Rian Rietveld 8:03 am on April 4, 2017 Permalink |
    Tags: weekly meetings   

    Week in WPa11y, March 29 – April 4 2017 

    New keyword a11y-task

    @afercia created a new tickets keyword a11y-task. These tickets aim to start a discussion and spread awareness about a11y issues that maybe can’t be resolved so soon. It’s also a way of being able to find accessibility tasks that we aren’t actively working on.

    Current work a11y team

    Gutenberg: as soon as the featured plugin is released we will test it.

    Tag Cloud adjustments (tag-cloud): #35566 #40187 #40186 #40184 #40138
    @samikeijonen and @davidakennedy

    Settings API plugin: @flixos90
    Felix released the plugin on GitHub: https://github.com/wpaccessibility/settings-api-enhanced which at the moment does exactly the same as the latest patches on #39441
    We can work on this plugin to iterate to the one-column layout we aim to have for admin forms.
    The advantages of developing in GitHub are:

    • Users can easily test the latest changes without us being required to do extra work.
    • Better diffs (because of individual commits) so that we can easier see what has changed over the last “patch”.
    • Easier collaboration (more people are familiar with git).

    Once we get to a first version of the one-column layout that is ready for testing, we should consider also adding the plugin to the wordpress.org plugin repo and formally announcing it as a feature project. This will allow us to hopefully get more voices on the honestly quite drastic changes and also to ask for user testing.

    Colour contrast in the Admin: @adamsoucie

    Required fields @rianrietveld

    Non-link links: @cheffheid

    Remove title attribute in the Admin: any volunteer

    To be worked on later

    Test requests (keyword a11y-feedback)

    Homework

    Test the patches for

    • #35497: List tables: Post format links improvements
    • #31476: Semantic elements for non-link links: /wp-admin/includes/widgets.php

    Test the plugin Settings API Enhanced

    Interesting reads this week

    Next meetings in the Slack #accessibility channel

    • Team meetings are on Mondays at 17:00 UTC in the Slack #accessibility channel.
    • Trac ticket discussions (bug scrub) are on Mondays at 16:00 UTC
     
  • Rian Rietveld 6:35 pm on April 12, 2016 Permalink
    Tags: , weekly meetings   

    Team Meeting April 11, 2016 

    Just before the 4.5 release we looked back and ahead on the work we do as a team. The following idea’s where discussed:

    We need more coders (Andrea Fercia is doing way to much on his own), and we have to find a way to find and keep new coders for our team.

    Be less focused on specific tickets, and more focused on tasks. And have somebody responsible for managing a goal, and keeping on top of all tickets pertaining to that goal. That may include asking somebody else to write it or work on it, but that person is keeping on top of that particular goal and whether it’s on track.

    Start a mentor program for new contributors, teach them accessibility and have someone available to answer questions, assign a coder a ‘mentor’ to ping on Slack.

    Find a way to get funding for the team. Almost all the work is done in our free time and this is part of the reason we are short of hands. Brainstorming about funding:

    • Crowd fund, for example Patreon.com
    • WordPress Agencies
    • Universities
    • WordPress Foundation
    • Accessibility organizations

    Joe Dolson is preparing a survey regarding WP and Accessibility, so we can gather data. What AT are people using (they should complete the survey once for each combination they use with WP), their pain points, where they feel WordPress is strong/weak, overall impressions of how WordPress has changed since they started using it including data about when they started using it, what version they’re currently using, if they haven’t updated, etc…

    Tickets cleaup

    To investigate which tikets need work and which goals we need to set for future releases we organize a tickets focussing accessibility review session on Saturday. A bug gardening, ticket cleaning, bug scrub meeting on Saterday April 16 at 13:00 UTC in the accessibility channel in Slack. Everyone is welcome to join us.

    Review the meeting at Slack

     
  • Rian Rietveld 4:20 pm on February 9, 2016 Permalink
    Tags: , weekly meetings   

    Summary Team Chat for Februari 8, 2016 

    Core accessibility coding standards

    After discussion with @jorbin some last changes where made on the Accessibility Coding Standards. @jorbin will bring it up at the next Core meeting to make sure there are no objections there.

    Documentation

    @hearvox finished the Quick Start Guide in our Handbook. @rachievee is working to add other pages to expand on topics from the Quick guide that need longer explanations.
    @trishasalas organizes a one time meeting on Februari the 22nd 17:30 UTC to discuss finalizing (for now) the structure for the handbook. In the meantime Trisha is going to begin writing the Plugin section of the Handbook.

    Accessibility Test Team

    Nimbus Hosting is so generous to sponsor the #wpa11y team with a VPS server. Here we can install a production, nightly and trunk version of WordPress and also have SVN and SSH access.
    We will set the server up next week, then we’re up and running again and resume sending tests to our team.

    Accessibility-ready themes

    Joe started to work on a fork of the theme unit test data, focused on accessibility testing – a smaller set of data, eliminating false positives in the data, etc. He will let us know when it’s usable.

    The post with the requirements for the accessibility-ready tag has been improved. There is now more information on how to test a theme to help theme authors better.

    Tickets

    @afercia: Investigation about color contrast continues.

    #26601: Inappropriate content in headings on admin screens.
    @trishasalas will write an new, refresed patch, keeping the add new link visually on the same place but placing it in the HTML outside the h1 heading

    From Februari 16 on we will have an extra meeting to work on tickets. The group has grown so much last year that we need more time to discuss and work on core tickets then we have now in the regular meeting. This ticket meetings will be every Tuesday on 18:30 UTC.

    And from everybody in the a11y team:
    We wish @accessiblejoe a good and quick recovery!

     
  • Rian Rietveld 10:23 am on January 19, 2016 Permalink
    Tags: , , weekly meetings   

    Summary Team Chat for January 18, 2016 

    Documentation

    @trishasalas and @rachievee have been working to organize the docs and create some new drafts in the handbook. Work in progress.

    Tickets

    #34780: Updates screen: Plugin and Theme tables improvements
    We discussed removing the scope from the th and td first and then think of a way to set up the layout, not in a table but in another, more semantic way.

    #34625: wp-login.php site title link points to wordpress.org
    We need to research if themes and plugins would break if the title attribute on the logo is removed. Maybe an option is to have no title output by default for the filter. @arush volunteered to own the ticket.

    #35313: Remove title attributes: Posts, Pages, and CPTs screens
    What to do with icons with a title attribute? For a sighted desktop user, the title attribute is the only indication what the icon means. There are many places where the link is just shown as an icon, and here the totle attribute was useful. We discussed how to solve this: we need to develop a core method to handle tooltips effectively. Andrea will open a ticket for this.

    Color contrast: Some browsers do not support the styling of checkboxes and radio buttons. This means that in some browsers give that borders a poor contrast by default.

    @afercia started to open tickets about the color contrast like #35497: List tables: Post format links improvements
    @rianrietveld will make a list of all the color issues in the Admin, we can use as a reference to open new tickets.

    Accessibility guidelines for core

    @joedolson had some comments on the core a11y guidelines; just a couple, minor changes for clarity. Basically well received by the core team. Joe is waiting for a few more comments from members of the core team that did not have to chance to look at them yet.

     
  • Trisha Salas 6:47 am on January 8, 2016 Permalink
    Tags: , weekly meetings   

    Summary Team Chat for January 4, 2016 

    Tickets

    #33952: get_search_form() accessibility improvements

    The main issue when using `get_search_form()` is redundancy.  A lot of  “search, search for… search… search button”

    Given that `get_search_form()` is used in both the admin & the front end as well as by themes it was determined that we will look at a uniform search for the 4.6 release.  In the meantime, we will remove the `title` attribute for a quick ‘win’.

    #35187: Remove title attributes: the terms List Table

    The current structure is semantically inaccurate but fixing it will require some design input to rework the list table layout. We have decided to stick with the original plan to remove the title attributes and find solutions for other issues at a later time.

    Accessibility standards for core

    @joedolson posted an updated link to the Accessibility Standards for Core document from last week. https://docs.google.com/document/d/1iySvDJ4duHYt6YlnnjnBNbU5LKAn1uRBMH8FKAfmswE/edit He has asked anyone who is interested to review and make comments.  He will eventually communicate with the core team to get this information into the Core Handbook.

    Documentation

    During the next week I will begin adding sub categories to the sections in this spreadsheet. https://docs.google.com/spreadsheets/d/1tOYzFn9vc7Ff4yGBmDajelrl7XMDUz4PR5H2lB4exI4/edit.

    The hope is to get more of a structure in place to make it easier to contribute.  So that, rather than needing to figure out where content will go you can pick a subcategory page and focus on the content for that page.
    We also discussed consistency as well as what the need to be sure that any of the content we link to from the handbook is vetted by the Accessibility Team as a whole.

    Next meeting

    Next meeting will be in January 11, 2016 at 18:00 UTC

     
  • Rian Rietveld 3:09 pm on December 28, 2015 Permalink
    Tags: , weekly meetings   

    Summary team chat, December 21, 2015 

    Accessibility standards for core

    There where several comments on the post with the accessibility code standards for core.
    @joedolson will add the relevant remarks. These standards will be added to the WordPress Coding Standards of the core Handbook.

    Documentation

    @trishasalas made a Google Doc with an overview of all the documentation that needs to be written for our handbook. More details about how to help her and contribute to the documentation in the blogpost Accessibility Handbook and Docs Update.

    Tickets

    #34957 #a11y-focus: Standardizing the handling of :focus and :hover
    Moving forward, we’ve established that :focus is the primary transition for when a user interacts with a link or button. :hover is an extension of :focus that comes from a direct action, whereas :focus comes from an indirect action. Because :focus lacks a direct action, it needs to be styled in a way that brings clear visual attention to the element. Michael Arestad (@michaelarestad) is working on the visual update and we’ll move forward with implementing it once we have that complete.

    #26601: Inappropriate content in headings on admin screens
    Consensus is: ‘Add New Button’ === burn it with fire (agreed on by @michaelarestad)
    @trishasalas will write a refreshed patch for this.

    Next meeting

    Next meeting will be in January 4, 2016 at 18:00 UTC

     
  • Rian Rietveld 10:34 am on December 15, 2015 Permalink
    Tags: , , weekly meetings   

    Team meeting summary December 14, 2015 

    The last month, especially after WordCamp US we’ve got a lot more people contributing to the wpa11y team.
    Welcome Robert Jolly, Morten Rand-Hendriksen, Cheo Walker, Sakin Shrestha, Barret Golding, Adam Soucie, Scott Mann and Rachel Vasquez!

    We want to keep all the new people involved, not make them feel lost or left out and leave.
    Therefore we decided to form working groups, assign one lead and divide the new people in the workgroups, so they know what to do and who to ask for help/work. People can jump in and out of groups as work ebbs and flows.

    Working groups

    Core

    • Task: Find accessibility issues, write and discuss tickets on core trac and code patches for WordPress core.
    • Lead: Andrea Fercia
    • Contributors: Joe Dolson, Jeffrey de Wit, Sergey Biryukov, Cheo Walker, Trisha Salas, Adam Soucie, Robert Jolly, Rian Rietveld.

    Documentation

    • Task: Write documentation about accessibility in our Handbook and on other relevant places on WordPress.org
    • Lead: Trisha Salas
    • Contributors: Joseph O’Connor, Barret Golding, Richard Senior, David Kennedy, Rachel Vasquez.
    • Joe Dolson and Robert Jolly volunteered to review written content.

    Theme team

    Meta

    • Task: Find accessibility issues, write and discuss tickets on meta trac and code patches for the website WordPress.org and WordPress.tv
    • Lead: Joe Dolson
    • Contributors: Morten Rand-Hendriksen, Barret Golding, Trisha Salas

    WordCamp themes

    • Task: Review of the WordCamp themes and help with fixing the accessibility
    • Lead: David Kennedy
    • Contributors: Jeffrey de Wit, Adam Soucie

    Test team

    • Task: Test the accessibility of new and exsisting functionallity in and for WordPress core, at the request of the other workgroups and teams
    • Lead: Rian Rietveld
    • Contributors: > 75 volunteers, with different kind of assistive tecnology and/or accessibility expertise

    Accessibility code standards for core

    During the WCUS community summit in Philadelphia we made a start with accessibility code standards for core.
    Joe Dolson put a concept for the a11y code standards together.
    Please look at the concept and comment on it.

    Documentation

    Barret and Trisha are working on a good outine for the documentation, lots of good ideas, work in progress, more next week.

    Core

    The last #a11y-headings ticket is #26601 Inappropriate content in headings on admin screens.
    Joe Dolson will look into this, make a decision on how to solve this issue. On the WCUS contributors day we discussed this and the outcome od this was: First get the link out of the heading, without changing the visual design. And after that is committed, start the discussion of removing it conpletely from the post-new.php / post.php pages.

    Next big project for 4.5: Color contrast ratio of the colors used in the WordPress Admin.
    The official colors to use are on make.wordpress.org/design/handbook/foundations/colors/
    Related ticket: #31234 closed Update wp-admin default colors.

    We need to review them and fix contrast ratios for text and background lower than 4.5.
    The tickets we file for this will be labeled #a11y-color.

    Also related:
    #34957 #a11y-focus: Standardizing the handling of :focus and :hover
    Any feedback on this ticket for the project is appreciated by Adam Soucie

    Meta

    Ideas for meta.trac tickets from Barret:
    1. the skip-to link needs to be closer to.
    2. the skip-to link-text should be visible on focus.
    3. the headings hierarchy is far from W3C standard.

    Idea from Morten: Start a campaign to get WordCamp speakers to caption their own talks.

    To-do for next week

    Read and comment on Accessibility code standards for core.

    Tickets that needs work/discussion
    If you want to work on core, grab one of these tickets and help solving them

    • #31195: Add a user-friendly way to preview site responsiveness in the Customizer
    • #34625: wp-login.php site title link points to wordpress.org
    • #31195: Add a user-friendly way to preview site responsiveness in the Customizer
    • #35029: Remove title attributes: the revisions limit in the Publish box
    • #35050: Remove title attributes: Plugin Cards
    • #35064: Remove title attributes: options-general.php
    • #35076: Remove title attributes: the Featured Image postbox
    • #34957 #a11y-focus: Standardizing the handling of :focus and :hover
    • And every other ticket that focusses accessibility
     
    • RachieVee 4:18 pm on December 16, 2015 Permalink | Log in to Reply

      Looking forward to helping out with documentation. It’ll be awesome getting those standards that were just posted into the handbook.

  • Joseph Karr O'Connor 7:21 pm on November 16, 2015 Permalink
    Tags: , , weekly meetings   

    Team Chat Summary November 16, 2015 

    Documentation

    Discussion of adding information about accessible content management to either the Codex or the Accessibility Handbook. Decided to add it to Handbook. Keyboard shortcuts will go in the Codex with a link from the Handbook.

    Tickets

    #34681 Consider removing the “Disable the visual editor when writing” option.
    Decided to gather user experience data. Four questions to ask:

        Do you know how to switch between the visual and HTML editor in WordPress?
        If no, please try and figure out how, and tell us how that experience was for you.
        If yes, give us your thoughts about your experience using that feature.
        Do you use the option “Disable the visual editor when writing” in your profile?

    #34625: wp-login.php site title link points to wordpress.org.
    Suggested fix: removing the title attribute, changing the text to ‘Powered by WordPress’, and leaving the filter on that text.

     
  • Joseph Karr O'Connor 5:03 am on August 13, 2015 Permalink
    Tags: , , weekly meetings   

    Team Chat Summary August 10, 2015 

    New Structure Proposed

    Rian Rietveld wrote a proposal on how to structure our work better and plan ahead longer and we discussed it. What follows is examples from the proposal.

    Goals and Issues

    This will be a separate page on make/accessibility and also a main menu item. It gives an overview of our goals for the accessibility of WordPress, the work we (want to) do, how this is organized, how we test, a roadmap for the next year and how we track the progress of issues we are working on. An example of the roadmap for release 4.4:

    Release 4.4 (December 2015, Scott Taylor)
    • Finish still open issues focus from 4.3
    • Semantic heading structure Admin
    • The customizer
    • Handbook
    • Twenty Sixteen (?)

    Central Ideas

    Some central ideas also included in the proposal are keyboard focus, work on the handbook, color contrast, system to better follow tickets including splitting up tickets among team members on which to concentrate, and continue to develop code pattern library. Much more is included in the proposal and for now we will continue to work on the proposal to make it a more formal document to cover our activities over the next year.

    We also talked about the fact that having a planning document to refer to does not obviate the need to address all new features since there is a tight turn around towards the end of a cycle because that’s when the features going into the release are announced. If we don’t follow all new features we might miss one or more that advance to release at the very end.

    When we have it shaped up we will add the planning documentation to this blog in the form of pages and sub-pages to make it a community resource.

     
    • Samuel Sidler 1:43 pm on August 27, 2015 Permalink | Log in to Reply

      Just wanted to say that I love the idea of a longer term goals for this team! Short term goals are great, but it’s nice to be able to see the short term goals in context of where everything is headed. 🙂

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar