Another example are issue boards. They represent elegant use of a good infrastructure ­— it is all just a smart use of labels. It would be very complex feature without the use of labels.

Culture

Chord Labels

Half the time I begin typing something, I'm not even sure what I'm writing yet. Writing it out is an essential part of thinking it out. Once I've captured it, re-read it, and probably rewritten it, I can then worry about what to label it, what it connects to, and where it should 'live' in my system.

Actually, I've decided to stop using labels for a while. A "bug" label gives the impression that someone else is going to fix the problem. We don't have enough volunteers for that (new contributors welcome!). I try to help people working on issues, though. I've spent many hours on this one.

You don’t need to do any tricky cursor stuff, because it’s all semantically wired up already.

I’d say if the form is short and an obvious pattern (like sign up or log in), you could use the placeholder visual pattern, but use real labels instead.

If they click the area taken up by the label, it will activate the input. If they click the input, it will activate the input. Both correct.

I like to keep the ‘verb’ + ‘noun’ structure when writing button labels — this makes the action more prescriptive, e.g. ‘Save post’, ‘Next step’, etc, as opposed to ‘Save’, ‘Next’

priority: 5 (nice to have) semver: Minor severity: 5 (confusing) type: Feature

A 2015 clip about vaccination from iHealthTube.com, a “natural health” YouTube channel, is one of the videos that now sports a small gray box.

Priority labels

Type labels are very important. They define what kind of issue this is. Every issue should have one and only one.

Sometimes it's useful to refine the type of an issue. In those cases, you can add facet labels.

Labeling is a task for everyone.

Labeling Issues

The “universal” label that has been slapped on to it is superfluous, but it does have its merits. Now that we have a commonly known term to refer to environment agnostic JavaScript code, it allows library authors to list it as a feature and be fashionable doing it. I’m happy with the term “universal” being fashionable because it makes developers think about their dependencies on the runtime environment. In the end this will help the JavaScript ecosystem mature and allow libraries to be used everywhere.

The “universal” label that has been slapped on to it is superfluous

or semantic value, is crucial to the production of information visualization. But any sense that “data” has an inherent “visual form” is an illusion.

a label will inform the program “this is a cat,” and not a cheeseburger - despite some visual similarity and the former perhaps having the latter.

It seems like everyday you wake up something has changed … Do you say Jew? Or Jewish? Is it a black guy? African-American? … You are on your toes because you never know what to say. So political correctness in that sense is scary.

directions provided with TITLE

For example, if there are multiple "Submit" buttons on a screen, the Name for each must be unique

Check each input form field for an ID and a corresponding LABEL or a descriptive TITLE. Fieldset and Legend may be used for grouping and associating two instructions to one input field.

A web page that has multiple form controls (e.g. buttons) with the same visual label must include unique identifiers that describe their unique purpose.