Having the original language in bold text in the node "TRANSLATIONS" tab is not semantic. make representation accessible.

I'm unable to find what you are referring to.

I think this is a <b> to <em> thing in the output of the language in the entity translation HTML.

I like links where we can go to see it and sample HTML myself.

...see if you like the updated issue summary better now ;)

...and a better issue title perhaps?

Steps to replicate:
1. Add additional languages.
Configuration > Regional and Language > Languages

2. Make content type translatable. (In this case, Article.)
Configuration > Regional and Language > Content and Language Settings

3. Add a piece of content that is translatable. (In this case, an Article titled "Sample.")
4. View the "Translations" tab to see bold text in question.

@YesCT :
1. Location: I agree that the location should be after the language. (In the example above, English.)
2. Word choice: How about 'original'? Or "origin language"?
I could mock up different options.

Here's a patch that just adds the Default source text.

My question:
I'm not sure if the issue is that the bolded text doesn't convey that the language is the default source language or if the issue is that the bolding doesn't convey its intent to blind users. If both, then just adding the "Default source" text would be the solution. If only the latter, what about adding the aria-label attribute for a description instead of the visible text?

I think adding this is useful:
<strong>English (Default source)</strong>

Although the text "Default source" actually makes me think of the defaults for the content type admin/config/regional/content-language rather than the initial language that the content was written in. Defaults are system wide. I prefer the text "(Source language)"

There is a User interface change, so tagging this.

I like the idea of appending a clarification in brackets and I also prefer "(Source language)".

Before patch:

After patch:

I think its technically true that this is the default source. When you go add a new translation, this is taken as source by default. You can change it to another source language though. That is why its the default source. That could however be an obscure detail :) What is also true that that language is the original/initial submission language of the content. For example, what the contrib http://drupal.org/project/config_translation module does now is it appends (original) to the language name. That might be simpler to express, because it refers to a workflow step earlier (when the content was created) then "default source" which is reference to a workflow step happening later (when a translation is being submitted). Re @YesCT in #6 that the original may have been a different language since you could have changed the language later, I think that is not typical, and I'm not sure a more obscure wording is worth it to cover that case properly too.

Using "(original)" is pretty concise. Seems like it might be part of an existing pattern too.

I thought I'd just re-roll the simple patch with the text change "(Original language)" which I do think conveys what we're looking for.

Fine for me as said above.

Committed and pushed to 8.x. Thanks!