Accessibility Team Chat Summary November 16, 2015

Documentation

Discussion of adding information about accessible content management to either the Codex or 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) 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 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. 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.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/.
Suggested fix: removing the title attribute, changing the text to ‘Powered by WordPress’, and leaving the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. on that text.

#accessibility-team-meeting, #team-reps, #weekly-updates

Accessibility Team Update: August 27, 2014

Weekly Testing Meeting

For the last two weeks we’ve been trying something new, a weekly 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 meeting, 17:00 – 19:30 UTC. We meet in the wordpress-ui IRC channel to share our tests. If you want to join in or just see what we are doing just show up in the IRC channel. Read the logs for August 18 and August 25 to get an idea of what we are doing.

#accessibility, #team-reps, #weekly-updates

Mobile Group Update for Feb 24, 2014

iOSiOS The operating system used on iPhones and iPads.: Work continues on version 4.0 with a code freeze on 3/1. There will be 1.5 weeks of time for testing the release after the freeze.
iOS: Work will be done this week to reorganize milestones for the 4.0.1 and 4.1 releases.
Android: Version 2.6.1 was released on Friday to address critical issues. 2.6.2 is planned for the end of this week to fix less severe issues.
Other Platforms: All other platforms are in a state of ongoing hiatus.

#mobile, #weekly-updates

Mobile Group Update for Feb 10, 2014

iOSiOS The operating system used on iPhones and iPads.: Version 3.9.1 submitted to Apple Friday for review. This fixes three major bugs including the time of a post changing upon editing.
iOS: Work will be starting on 3.9.2 this week. This is a follow up bug fix release for less pressing issues not included in 3.9.1.
Android: Version 2.6.1 addresses some crashes detected in 2.6 and will likely be released toward the end of this week or early next week. Translation is the primary hold up right now.
Other platforms: Officially the other platforms (Windows Phone 8, Blackberry, etc) are on hiatus.
GSoC: Three potential mobile projects submitted and a couple of mobile contributors are listed as mentors.

#mobile, #weekly-updates

Docs Team Update – Jan 30, 2014

Howdy folks,

Here’s a recap of the major topics discussed at this weeks Docs Chat:

  1. New Docs Chat Time -We’re changing the time of the weekly Docs Chat (not Support) to:
    • Thursday 4pm PST
    • Thursday 5pm Mountain
    • Thursday 6pm Central
    • Thursday 7pm EST
    • Friday Midnight UTC
    • Friday 7am ICT
  2. Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. -we’re need to choose a new team rep this week, so please go comment on Siobhan’s post, New Team Rep (also, do we need one?).
  3. Docs Sprint -There’s a Docs Sprint  this Saturday, Feb 1 at 10am PST. Join the sprint in Seattle, or on IRC at #wordpress-sfd.
  4. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. -@jazzs3quence and contributors are making progress, but still need help with:
    1. Documentation contributions for tooltips and overviews
    2. Testing and bug/issue reporting.
  5. Docs Project Landing Pages -We’re creating helpful landing pages for each docs-related project that provide an overview of the project and a clear path for contributors to get involved. Each docs project will add a page to the Projects section where @DrewAPicture posted the landing page for Inline Docs. @siobhan would like to have these pages complete by Feb 28th and would like a volunteer to oversee this project.

Full IRC Logs

#docs, #team-reps, #weekly-updates

Accessibility Team Update: January 22, 2014

Ticket Activity Report

@grahamarmfield reported progress on ticket 26602: Insufficient information for screen readers in themes.php. “On the new Themes page in trunk, it is now possible to tab to each of the themes within the list of themes found. However for screen readers there may be no audible feedback to tell the user which theme has focus.” Thanks to @joedolson for the initial patch and everyone else who worked on the solution. The status is now: closed defect (bug) (fixed).

Keyboard Testing

Some of us are proceeding with the keyboard functionality audit of all the admin screens. We have a target deadline of February 5, 2014 to complete the testing. There is a learning curve as each team member learns the routines. Some of us have never done testing so this is a valuable learning experience for us. We are comparing our findings before making them public. @rianrietveld has made a test instance available to us so that we are all using the same environment. She also posted about this on our WordPress Accessibility LinkedIn group. Thanks to everyone who is participating.

#accessibility, #team-reps, #weekly-updates

Accessibility Team Update: January 15, 2014

Testing 3.8 Admin Screens

The team discussed our current project, keyboard testing of 3.8 admin screens. There is now a new page on Make WordPress Accessible named Testing, and a sub-page under that named 3.8 Admin Screens Results. The testing page contains a list of 3.8 admin screens and a sample results table. The results page contains the report we are starting to build. We agreed on a testing methodology and the 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 AA success criteria we will reference. Testing is now underway.

Other Projects

  • During the meeting @jorbin notified us that #26602 is ready for testing after he applied a patch.
  • Also @davidakennedy is still committed to helping out the Widgets project and @grahamarmfield is going to have a look at the AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.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 which is now on the repo.
  • At the same time we are checking the admin screens for keyboard 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) we will also be doing a separate report on all WCAG 2.0 AA issues on the P2 Theme we are using for this blog.

#accessibility, #team-reps, #weekly-updates

Accessibility Team Update: January 8, 2014

Workflow Redux

In 1982, in his Frank and Ernest comic strip, Bob Thaves wrote about Fred Astaire: “Sure he was great, but don’t forget that Ginger Rogers did everything he did, backwards…and in high heels.”

Doing 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) dance is very much like that. Great care is taken to make sure that not only do we produce useful reports and code solutions but that whatever we create is as accessible as possible. For instance, last week we stated that when we produce word processing documents, they will be output as RTF, to preserve formatting between platforms. We also said we’d use Dropbox because it integrates so tightly with operating systems, giving our team access to files while using 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 in familiar ways. Using Dropbox as a staging area for documentation and automatically pushing finished work, including code solutions, to 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/ seemed like a good way to make our work public. The good is often the enemy of the best.

WordPress

This week we discussed this blog and how we can best integrate our workflow into the WordPress environment. Remember when Drupal set up a WordPress blog to publish info about Drupal? Perhaps we should explore our workflow options within our own ecosystem. This week we started working through the issues we face when contemplating using WordPress to publish our findings.

Tables

Mostly all of the accessibility assessments I’ve worked with, both manual and automatic, contain tables to display issues, reference to guidelines, solutions, etc. It might not be absolutely necessary to display this info in tables, but tables sure help to organize this type of tabular data. We just need to code accessible tables in WordPress. You can read how to properly code tables in Creating Accessible Tables by WebAIM.

TinyMCE and Tables

WordPress ships with a WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. editor, TinyMCE. TinyMCE has a table tool. The TinyMCE site does have a page devoted to TinyMCE accessibility with one brief reference to tables. We’d have to test both the back end functionality and the output of that tool before we can say that it can be easily used with a keyboard and that it outputs accessible table code. If we need to, we’ll work with the 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. team to devise an accessible table feature for TinyMCE and it will benefit more than our project.

P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. Template

This page is produced using the P2 Theme. When it comes down to it, if we really want to make sure that our output is accessible, then we should check the P2 Theme for accessibility. This also will benefit more than our project alone.

Action Items

At the end of the meeting we summed up our next actions to work within WordPress to publish our accessibility findings accessibly, and to proceed with our focus on keyboard accessibility of admin pages:

  1. Check TinyMCE table tool function and output, work with the Meta team if needed
  2. Check P2 Theme for accessibility
  3. Proceed with keyboard functionality assessment of admin pages

#accessibility, #team-reps, #weekly-updates

Accessibility Team Update: January 1, 2014

Happy New Year to the entire WordPress community!

Accessible IRC Clients

Thanks to the team members who joined us today, and to @grahamarmfield who reported in while traveling. Just as we got underway we had a question on Twitter asking which IRC clients are accessible plus we found out later that one of our team members, @arush was sidelined when her IRC client “totally choked.” So after the meeting we used the LazyWeb technique and asked @WPAccessibility followers for some suggestions:

  • For Windows, Jennifer Sutton @jsutt suggests Instantbird
  • For Mac, @jsutt also recommends Adium
  • For Unix, Chris Nestrud @IAmChrisN recommends irssi

Much thanks to Jennifer, who is a big help to 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 and to the entire accessibility community, and also thanks to Chris Nestrud for the Unix suggestion. Chris says: “anything with a text UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. on Unix should work. I like irssi.” We can still use suggestions for accessible IRC clients for iOSiOS The operating system used on iPhones and iPads., Android, and Windows Mobile.

Workflow

We are starting the process of auditing 3.8 for keyboard accessibility. Reports are generated in the process of accessibility auditing. We discussed how to handle those reports. A few meetings ago @ceo suggested that we create the reports in RTF format so the formatting is not lost in the platform shuffle and we will do that.

During today’s meeting we finalized plans to create a public 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/ repository where we will store the finished reports and other documents as we produce them. We will also create and update our assignments and to-do lists on Github.

We also finalized plans to create a Dropbox account for the team which we will use to store documents to be reviewed before they are finalized. Tom Harrigan made the suggestion that we set up a directory in Dropbox that will automatically sync from dropbox to github.

@davidakennedy has agreed to set up Github and Dropbox. Thanks David!

#accessibility, #team-reps, #weekly-updates

Accessibility Team Update: December 18, 2013

Focus on Keyboard 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)

The accessibility team met today to discuss a new initiative:

  • We will conduct an audit of keyboard accessibility and make those findings available to everyone
  • We will reach out to other teams to disseminate this information
  • Our short term goal is to add keyboard accessibility to everyone’s toolkit
  • Our long term goal is to institutionalize accessibility.

Support Requests

Two projects have asked for help from the accessibility team:

  • Widget Improvements: @davidakennedy has volunteered to provide support
  • AH-O2: @trishasalas is already providing support

#accessibility, #team-reps, #weekly-updates