Title: team reps – Team Updates – WordPress.org

---

#  Tag Archives: team reps

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
7:23 pm _on_ November 16, 2015     
Tags: [accessibility team meeting ( 21 )](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
team reps, [weekly updates ( 244 )](https://make.wordpress.org/updates/tag/weekly-updates/)

# 󠀁[Accessibility Team Chat Summary November 16, 2015](https://make.wordpress.org/updates/2015/11/16/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](https://core.trac.wordpress.org/ticket/34681).

Decided to gather user experience data. Four questions to ask:

 1.  a. 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?
 2.  a. If no, please try and figure out how, and tell us how that experience was for 
        you.
 3.  a. If yes, give us your thoughts about your experience using that feature.
 4.  a. 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](https://core.trac.wordpress.org/ticket/34625).

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](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](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
[#team-reps](https://make.wordpress.org/updates/tag/team-reps/), [#weekly-updates](https://make.wordpress.org/updates/tag/weekly-updates/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2015%2F11%2F16%2Faccessibility-team-chat-summary-november-16-2015%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
8:17 pm _on_ August 31, 2015     
Tags: [accessibility ( 36 )](https://make.wordpress.org/updates/tag/accessibility/),
[accessibility team meeting ( 21 )](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
team reps   

# 󠀁[Team Chat Summary August 31, 2015](https://make.wordpress.org/updates/2015/08/31/team-chat-summary-august-31-2015/)󠁿

### Headings

More work is being done on headings in admin. [Jeffrey de Wit created some tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&description=~%23a11y-headings&order=priority)
some of which are already patched and committed. [Follow the headings discussion](https://wordpress.slack.com/archives/accessibility/p1441044260000352)
in [#accessibility](https://make.wordpress.org/updates/tag/accessibility/) on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

### Handbook

Devised a strategy for building out the [Make WordPress Accessible Handbook](https://make.wordpress.org/accessibility/handbook/).
Page leaders will help others build out the handbook.

### Twenty Sixteen

[Twenty Sixteen is on Github](https://make.wordpress.org/core/2015/08/29/twenty-sixteen-is-now-on-github/).
[Twenty Sixteen is also available in the theme directory](https://make.wordpress.org/core/2015/08/31/twenty-sixteen-in-the-theme-directory/).
It’s not in trunk yet. According to David Kennedy ” I did a 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)-ready review before it went
on 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 by the repository owner. [https://github.com/](https://github.com/)
and the directory to make sure nothing was way off accessibility-wise. It’s solid.
Takashi knows the drill.” We will ask the testers to test it. David Kennedy did 
[an #accessibility-ready audit of Twenty Sixteen](https://cloudup.com/cSxoSFIzLcB).

### Select2

We continued a discussion about [Select2](https://github.com/select2/select2/issues/2499)
as an alternative to the autocomplete/tagging input field types. There are two main
accessibility issues: it doesn’t do a good job of providing feedback to screen readers
and it requires the ‘enter’ key to begin typing for autocomplete, a non-standard
interaction. The testers have tested Select2 and it is not very accessible. Rian
Rietveld will collect all the data and report next week.

### 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](https://central.wordcamp.org/about/)󠁿. US

Several of us are [submitting proposals for talks at WordCamp US](https://2015.us.wordcamp.org/speakers/)
and depending on funding assistance some of us will be attending. Today is the last
day for submitting proposals.

[#accessibility-team-meeting](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
[#team-reps](https://make.wordpress.org/updates/tag/team-reps/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2015%2F08%2F31%2Fteam-chat-summary-august-31-2015%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
5:07 am _on_ August 13, 2015     
Tags: [accessibility team meeting ( 21 )](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
team reps   

# 󠀁[Team Chat Summary August 10, 2015](https://make.wordpress.org/updates/2015/08/13/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/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) 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 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.
 * 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](https://github.com/wpaccessibility/a11ythemepatterns).
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.

[#accessibility-team-meeting](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
[#team-reps](https://make.wordpress.org/updates/tag/team-reps/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2015%2F08%2F13%2Fteam-chat-summary-august-10-2015%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
8:47 am _on_ July 8, 2015     
Tags: [accessibility ( 36 )](https://make.wordpress.org/updates/tag/accessibility/),
team reps, [weekly meetings ( 2 )](https://make.wordpress.org/updates/tag/weekly-meetings/)

# 󠀁[Accessibility Team Meeting July 6, 2015](https://make.wordpress.org/updates/2015/07/08/accessibility-team-meeting-july-6-2015/)󠁿

### H1 in the admin

For 4.3 there will be an H1 in the admin. [#31650: Missing H1 heading in the admin](https://core.trac.wordpress.org/ticket/31650).
Assistive technologyAssistive technology **Assistive technology** is an [umbrella term](https://en.wikipedia.org/wiki/Umbrella_term)
that includes assistive, adaptive, and rehabilitative devices for [people with disabilities](https://en.wikipedia.org/wiki/Disability)
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](https://en.wikipedia.org/wiki/Technology)
needed to accomplish such tasks. [https://en.wikipedia.org/wiki/Assistive_technology](https://en.wikipedia.org/wiki/Assistive_technology)
users look for the H1 for way finding. Though there is the page title, when AT separates
out elements such as links, lists, and headings, the info needs to be there too.
Two weeks ago we ran this by [Mika Epstein @Ipstenu](https://profiles.wordpress.org/ipstenu)
and she helped us understand heading levels and plugins. Mika spot checked some 
plugins and it showed that they are using H2 and her opinion is that “[we can post about that in make/plugins to try and spread the word](https://wordpress.slack.com/archives/accessibility/p1434996747000162).”
Thanks Mika. More work will be done on the rest of the hierarchy.

### Main Open Tickets

We also briefly discussed:

 * [#31661: Quicktags: Can’t add them using just a keyboard in IE](https://core.trac.wordpress.org/ticket/31661),
 * [#26601: Inappropriate content in headings on admin screens](https://core.trac.wordpress.org/ticket/26601),
 * [#32152 List table: sortable column headers accessibility](https://core.trac.wordpress.org/ticket/32152),
 * [#26601: Inappropriate content in headings on admin screens](https://core.trac.wordpress.org/ticket/26601),
   and
 * [#31336: Customizer: separate navigation from options UI for better UX by removing accordion behavior](https://core.trac.wordpress.org/ticket/31336).

[#accessibility](https://make.wordpress.org/updates/tag/accessibility/), [#team-reps](https://make.wordpress.org/updates/tag/team-reps/),
[#weekly-meetings](https://make.wordpress.org/updates/tag/weekly-meetings/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2015%2F07%2F08%2Faccessibility-team-meeting-july-6-2015%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
8:24 am _on_ February 16, 2015     
Tags: [accessibility ( 36 )](https://make.wordpress.org/updates/tag/accessibility/),
[accessibility team meeting ( 21 )](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
team reps   

# 󠀁[Accessibility Team Update: February 11, 2015](https://make.wordpress.org/updates/2015/02/16/accessibility-team-update-february-11-2015/)󠁿

### Testing

We had a report by Rian Rietveld on testing results. Things are going very well.
Rian said: “I’m getting test results back on the tab order of the post table, it
seems to work ok, but they found a ton of other problems, I have to check the current
tickets and open new if necessary.”

### Pattern Library

David Kennedy told us that [the repos are set up for contributions to the theme pattern library](https://github.com/wpaccessibility).
See the [Accessible Theme Pattern Library Update for February](https://make.wordpress.org/accessibility/2015/02/11/accessible-theme-pattern-library-update-for-february-2015/)
for more info.

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

Andrea Fercia reported on a discussion he had with the Core team. He asked about
menu bar admin focus and non-link links (28599 and 26504). Joe Dolson said “the 
link/button question really requires specific cases; I’m not sure how we could approach
giving any kind of global comments on the topic.” Andrea said that he also updated
the Core team about [the first testing round on customizer theme switcher](https://make.wordpress.org/accessibility/2015/01/31/theme-switcher-accessibility-test-result/).

### Theme Checking

Joe Dolson updated us on the state of checking themes requesting the accessible-
ready tag.”We’re now up to 29 live themes carrying 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)-ready tag which have been
tested and passed. There’s one outstanding theme live that does not pass (_tk); 
it’s undergoing the review process now, and will either be suspended or updated 
soon.I’ve got two pending theme reviews to do, and know of at least 1 theme that’s
currently approved and waiting to go live.”
 Joe has also trained two of the theme
review team admins on reviewing for accessibility. Additionally Joe has shifted 
support for landmark roles into a required feature for accessibility-ready themes,
rather than recommended.

#### Landmarks

Discussion turned to the over-abundance of landmarks. The current proposed code (
[#23089](https://core.trac.wordpress.org/ticket/23089)) outputs too many landmark
roles. A theme may add numerous landmark roles without the ability to control where
and how many there are. Andrea noted “currently, _s outputs one aside (mapped to
complementary) for each 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., nested inside a general complementary area for widgets.” [Jared Smith of WebAim recently said](http://twitter.com/jared_w_smith/status/561285223220912128)“
Easy accessibility check: Search for “role” in source code. If 0 instances, probably
bad. If 1-20, probably OK. If greater than 20, definitely awful.”

### Other Items

Morten Rand-Hendriksen asked: “What is the best tool for computer voice control (
in particular, voice controlled browsing) on both Windows and MacOS? Are there any
workable free tools or are we confined to things like Dragon?” There is a demo mode
in JAWS and NVDA is free. If there is a free way for developers and designers to
experience things using voice control it will help them understand the issues better.
Sam Sidler noted that “OS X has voice control built-in, so I’d call that free, but
not 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.-level free.”

We finished off by discussing Shiny Updates (see ticket 29820 now landed in core).
According to Andrea Fercia there are two main accessibility issues:

    - focus handling
    - absolutely no feedback for screen reader users when an install/update action
      starts, ends, fails, etc.

About the latter issue Andrea said “I’d like to propose a solution based on Graham
Armfield’s idea (see [#28892](https://core.trac.wordpress.org/ticket/28892)) but
done in a way that it would hopefully be a useful tool for developers.”

[The entire conversation from February 11](https://wordpress.slack.com/archives/accessibility/s1423683720001542)
is available in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
archives for the [#accessibility](https://make.wordpress.org/updates/tag/accessibility/)
channel.

[#accessibility-team-meeting](https://make.wordpress.org/updates/tag/accessibility-team-meeting/),
[#team-reps](https://make.wordpress.org/updates/tag/team-reps/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2015%2F02%2F16%2Faccessibility-team-update-february-11-2015%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
6:11 am _on_ August 30, 2014     
Tags: [accessibility ( 36 )](https://make.wordpress.org/updates/tag/accessibility/),
team reps, [weekly updates ( 244 )](https://make.wordpress.org/updates/tag/weekly-updates/)

# 󠀁[Accessibility Team Update: August 27, 2014](https://make.wordpress.org/updates/2014/08/30/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](https://irclogs.wordpress.org/chanlog.php?channel=wordpress-ui&day=2014-08-18&sort=asc)
and [August 25](https://irclogs.wordpress.org/chanlog.php?channel=wordpress-ui&day=2014-08-25&sort=asc)
to get an idea of what we are doing.

[#accessibility](https://make.wordpress.org/updates/tag/accessibility/), [#team-reps](https://make.wordpress.org/updates/tag/team-reps/),
[#weekly-updates](https://make.wordpress.org/updates/tag/weekly-updates/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2014%2F08%2F30%2Faccessibility-team-update-august-27-2014%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
7:58 am _on_ March 29, 2014     
Tags: [accessibility ( 36 )](https://make.wordpress.org/updates/tag/accessibility/),
team reps, [weekly meetings ( 2 )](https://make.wordpress.org/updates/tag/weekly-meetings/)

# 󠀁[Accessibility Team Update: March 26, 2014](https://make.wordpress.org/updates/2014/03/29/accessibility-team-update-march-26-2014/)󠁿

### Meeting Time Change

We will be going back to a meeting time of 19:00 UTC next Wednesday, April 2.

### Progress

The meeting this past Wednesday was interesting. Now we’re getting to the heart 
of the matter.

So far, we have compiled a [keyboard-only report on most of 3.8](https://make.wordpress.org/accessibility/testing/3-8-admin-screens-results/)
and have some data to rely on.

The first pattern we identified from the testing is poor visual keyboard focus in
the Admin. Rian created a ticket dealing with keyboard focus. [Better visual indication of focus on elements in the Admin](https://core.trac.wordpress.org/ticket/27173)(
[#27173](https://core.trac.wordpress.org/ticket/27173)). This ticket is now closed(
fixed.) Thanks Rian!

### Testing 3.9

We have to quickly change gears because 3.9 is due out in 18 days and we have to
test and create tickets where we find issues. A [list of items to concentrate on](https://wordpress.org/news/2014/03/wordpress-3-9-beta-1/)
will help guide us.

Contact [@AccessibleJoe](https://profiles.wordpress.org/AccessibleJoe/) for details
if you want to help test 3.9.

[#accessibility](https://make.wordpress.org/updates/tag/accessibility/), [#team-reps](https://make.wordpress.org/updates/tag/team-reps/),
[#weekly-meetings](https://make.wordpress.org/updates/tag/weekly-meetings/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2014%2F03%2F29%2Faccessibility-team-update-march-26-2014%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/sewmyheadon/) [Eric Amundson](https://profiles.wordpress.org/sewmyheadon/)
6:57 pm _on_ January 30, 2014     
Tags: [docs ( 227 )](https://make.wordpress.org/updates/tag/docs/),
team reps, [weekly updates ( 244 )](https://make.wordpress.org/updates/tag/weekly-updates/)

# 󠀁[Docs Team Update – Jan 30, 2014](https://make.wordpress.org/updates/2014/01/30/docs-team-update-jan-30-2014/)󠁿

Howdy folks,

Here’s a recap of the major topics discussed at this weeks [Docs Chat](https://irclogs.wordpress.org/chanlog.php?channel=wordpress-sfd&day=2014-01-30&sort=asc):

 1. **New Docs Chat Time** -We’re [changing the time of the weekly Docs Chat](https://make.wordpress.org/docs/2014/01/26/changing-the-docs-chat-time/)(
    not Support) to:
 2.  * Thursday 4pm PST
     * Thursday 5pm Mountain
     * Thursday 6pm Central
     * Thursday 7pm EST
     * Friday Midnight UTC
     * Friday 7am ICT
 3. **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?)](https://make.wordpress.org/docs/2014/01/30/new-team-rep-also-do-we-need-one/).
 4. **Docs Sprint** -There’s a [Docs Sprint](http://www.meetup.com/SeattleWordPressMeetup/events/159149032/)
    this Saturday, Feb 1 at 10am PST. Join the sprint in Seattle, or on IRC at #wordpress-
    sfd.
 5. **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](https://make.wordpress.org/)** -@
    jazzs3quence and contributors are making progress, but still need help with:
 6.  a. Documentation contributions for tooltips and overviews
     b. Testing and bug/issue reporting.
 7. **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](https://make.wordpress.org/docs/projects/)
    where @DrewAPicture posted the landing page for [Inline Docs.](https://make.wordpress.org/docs/projects/inline-docs/)
    [@siobhan](https://profiles.wordpress.org/siobhan/) would like to have these pages
    complete by Feb 28th and would like a volunteer to oversee this project.

---

[Full IRC Logs](https://irclogs.wordpress.org/chanlog.php?channel=wordpress-sfd&day=2014-01-30&sort=asc)

[#docs](https://make.wordpress.org/updates/tag/docs/), [#team-reps](https://make.wordpress.org/updates/tag/team-reps/),
[#weekly-updates](https://make.wordpress.org/updates/tag/weekly-updates/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2014%2F01%2F30%2Fdocs-team-update-jan-30-2014%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/)
12:55 am _on_ January 28, 2014     
Tags: team reps   

# 󠀁[Team Reps](https://make.wordpress.org/updates/2014/01/28/team-reps/)󠁿

We’re a little overdue to re-up/choose/elect team reps again based on the last round.
We can do that, or we can go back to a longer term for reps, or we can revisit the
concept of team reps.

 * Some teams are better than others about getting the updates posted.
 * On some teams the rep also acts as a lead, while on others it’s just posting 
   updates.
 * The job description is to post updates and to be a liaison between your team 
   and the rest of the contributor groups via this site. There are a lot of weekly
   updates, but not so much liaising. When I’ve posted things for comment, it has
   appeared that people are responding based on their own opinion rather than getting
   their team’s group opinion and relating it back.

So! Can everyone check with their team to see what they think and report back here?
If we want to go with the status quo, then each team should choose their early 2014
rep this week. How the team chooses is up to the team. If any teams want to propose
a different approach, hit the comment sections (please speak for your team rather
than putting out suggestions that haven’t been run by them first).

Thanks!

[#team-reps](https://make.wordpress.org/updates/tag/team-reps/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2014%2F01%2F28%2Fteam-reps%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/accessiblejoe/) [Joseph Karr O'Connor](https://profiles.wordpress.org/accessiblejoe/)
5:44 am _on_ January 25, 2014     
Tags: [accessibility ( 36 )](https://make.wordpress.org/updates/tag/accessibility/),
team reps, [weekly updates ( 244 )](https://make.wordpress.org/updates/tag/weekly-updates/)

# 󠀁[Accessibility Team Update: January 22, 2014](https://make.wordpress.org/updates/2014/01/25/accessibility-team-update-january-22-2014/)󠁿

### Ticket Activity Report

@grahamarmfield reported progress on [ticket 26602: Insufficient information for screen readers in themes.php](https://core.trac.wordpress.org/ticket/26602).“
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](http://www.linkedin.com/groups/WordPress-Accessibility-4415968?home=&gid=4415968&trk=anet_ug_hm&goback=.gmr_4415968)
LinkedIn group. Thanks to everyone who is participating.

[#accessibility](https://make.wordpress.org/updates/tag/accessibility/), [#team-reps](https://make.wordpress.org/updates/tag/team-reps/),
[#weekly-updates](https://make.wordpress.org/updates/tag/weekly-updates/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2014%2F01%2F25%2Faccessibility-team-update-january-22-2014%2F%23respond&locale=en_US)

# Post navigation

[← Older posts](https://make.wordpress.org/updates/tag/team-reps/page/2/?output_format=md)