Opened 6 years ago

Last modified 3 years ago

#3577 new enhancement

Add Dictonary for Captioner on WordPress Events

Reported by: travel_girl's profile Travel_girl Owned by:
Milestone: Priority: normal
Component: Handbooks Keywords:


At some WordPress Events there are transcribers who type what the speaker is saying on the stage. This allows people to also read what the speaker is saying. This makes the whole conference more accessible, especially for the hearing impaired and non native speakers.

Currently speakers are asked to send their slides in advance, so that the captioners can prepare und understand the technical and WordPress terms which will be used in the talk.

I chatted with the captioners to find out what I as a speaker could do to help them. They showed me, that they had created their own WordPress dictionary from the slides they had received from the speakers. They are also reusing this dictionary for future WordPress conferences and expanding on it with new words, that they get from further slides.

The problem with this workflow is, that

  1. some speakers don't send the slides beforehand or don't have every technical word in the slides.
  2. Questions and last minute changes at the slides could include technical/WordPress specific words, which are not in the captioner´s dictionary.
  3. Sometimes they do not know how some technical written terms are pronounced (like i18n)

Some examples for WordPress related words

  • Jetpack and other common plugins
  • i18n, A11y ... - the captioners don't know how this is spoken out
  • Aria, ....

So I thought that we as the WordPress Community could help the transcriptioners by providing them an dictionary with WordPress related words, which their could use and import into their tool.

I asked them if this would be helpful and they loved the idea. The good side would be that we could give this dictionary to the captioners at every WordPress conference which they can import into their tool.

All they need is the terms and how the term is spoken. An excel sheet would be enough.

To create this table I would suggest to make it like a Wiki, which is Open Source and could be extended from the community. But of course this should be discussed, what the best way would be, if we decide to realizing it.

A starting point could be this Dictionary:

Maybe we could start with a small table and than ask for feedback from the captioners to check, if this is a format their could use (the captioners from WordCamp London said, they would like to give us feedback). In this way we can make sure, that the format is correct, before we continue.

The captioners doing an amazing job and having an big impact to make the WordCamps more accessible. I would love, if we could make their job more easier.

Change History (8)

This ticket was mentioned in Slack in #community-team by travelgirl. View the logs.

6 years ago

#2 @keesiemeijer
6 years ago

I've created a list with all unique words used in WordPress 4.9 functions and hooks. Maybe it could help you find words you want to include in the dictionary. Most words are not that useful though.

Last edited 6 years ago by keesiemeijer (previous) (diff)

#3 @casiepa
6 years ago

For the polyglots we have our dictionnary:

#5 @Travel_girl
5 years ago

Thanks @iandunn, @casiepa, @keesiemeijer for the links!

I think that is a great starting point, I'm just not totally convinced, that those is the exact thing, that captioners. As far as I can see, are those resources mainly for terms inside the WordPress-Software and explain the meaning of the term. Thats great for people who want wo work with WordPress, but not necessary for transcription.

The things that are missing for captioners:

  • Words for terms inside the WordPress-World (also big Plugins, Themes, Companies, Names of WordPress People how are mentioned in talks regularly)
  • hint how you say words. Like WCAG is said in different ways. It can be W-C-A-G or w-cack. Or AA can be AA or Douple A

Those things are not necessary to include into the resources above, but would be really helpful for captioners.

I think an own tool/resource for that purpose would make sense, but I don't know how we could include this into meta or make it maintainable.

Any ideas?

#6 @casiepa
5 years ago

@Travel_girl I'm willing to help setting up something on our side as this seems to relate somehow to . I could also check with the people that we have every year for WCEU (but maybe it are the same ones in London).

If the starting point is a spreadsheet, then if you have an example with some lines, we could see where to start from, then see how to open it up to others.

#8 @coffee2code
3 years ago

The recently-released Documentation Style Guide includes a Word list and usage dictionary section that fulfills a large part of this request.

While that guide would not be appropriate for listing WordPress companies, people, and commonly referenced plugins/themes, it definitely should include technical terms, abbreviations, acronyms, etc that one would expect to encounter in the WordPress sphere.

As @casiepa noted, some of the contributor teams have their own glossaries of terms. (Having a universal glossary has also been proposed in #4522.)

Some existing glossaries:

Obviously there is a definite need for cross-team collaboration to try to create a universal glossary (with each team amending the glossary within the context of their own handbooks for team-related terms).

In that vein, the Make team's handbook seems the most appropriate place for a captioner's glossary. That could pull the general terms from the (hypothetical) universal glossary and supplement it with the companies, people, plugins/themes, etc.

Note: See TracTickets for help on using tickets.