Comment 1 by dkager on 2015-03-18 20:13
I'd rather see "lmk nav", "lmk main" and so on. This way you can quickly verify that you're dealing with a landmark, then read on to find out its type if you care about that information, or else whiz right past it to the page's main text.
Either way I agree that shortening is a very good idea.

This still looks relevant. A summary of my thoughts:

• Shorten the word landmark to something like lmk (taken from SuperNova).
• Shorten landmark names, preferably all to the same length. @LeonarddeR also had some good ideas for that.
• Swap the word landmark and the name, e.g. "landmark main", because the word landmark is the more signifcant part.

This is a bold idea, feel free to shoot it down. But what about putting the word main and just put dots seven and eight below it all the way across?

Sent from a mobile device.
Please disregard errors as this is a smaller device.

On Jul 9, 2016, at 05:06, Davy Kager notifications@github.com wrote:

This still looks relevant. A summary of my thoughts:

Shorten the word landmark to something like lmk (taken from SuperNova).
Shorten landmark names, preferably all to the same length. @LeonarddeR also had some good ideas for that.
Swap the word landmark and the name, e.g. "landmark main", because the word landmark is the more signifcant part.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

But what about putting the word main and just put dots seven and eight below it all the way across?

This would be a little confusing because that is also the selection indicator, and the word main could be the start of the line (e.g. "main menu").

An alternative to explore is to use indicators for all element types or even for all widgets, but that's a different discussion.

My current preference is "lm main". But most other widget names are three letters long (edt, btn, lst, cbo), so maybe we should use a three-letter abbreviation for the word landmark? On the other hand users with a smaller braille display will appreciate the brevity of "lm". The same goes for the landmark names: "mn" is nice and short but "main" is a bit easier to understand. Thoughts?

I want to pick this issue up again so have been reading about the ideas we had.

One more bold question: is the word landmark (or lmk, or whatever) even required? Would it not be enough to see just "main", "nav", etc? Or could this be confused with the webpage's actual text?

We might have labeled regions, I.E. "Fried items Region"

Could you give a real-world example or some HTML to reproduce this? If I read the code correctly this would include the word "region", so it's still unambiguous.
I'm keeping the (abbreviated) word "landmark" in for now, but would still like an example of named regions to make sure I get them right.

I came up with the following abbreviated landmark names. Please feel free to shoot them down:

landmarkLabels = {
	"banner": "bnnr",
	"complementary": "comp",
	"contentinfo": "cinf",
	"main": "main",
	"navigation": "nav",
	"search": "srch",
	"form": "frm",
	"region": "rgn",
}

Minor problem with "main" and "form" landmarks.
They should have separate translatable strings for braille and speech.
In english, they don't need to be abbreviated in braille since they have 4 characters.
It is different in other languages, so, like other landmarks names, they should have a separate translation for braille and speech.

These should be translatable already. In braille.py:

	# Translators: Displayed in braille for the main landmark, normally found on web pages.
	"main": _("main"),

I suppose this goes wrong because it has the same name in braille as in speech. Is this a use case for pgettext with a context?