W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2014

Re: Usefulness of language annotations

From: Jens O. Meiert <jens@meiert.com>
Date: Tue, 12 Aug 2014 15:58:29 +0530
Message-ID: <CAJ0g8QQ+T7f5FZH6nwL7yn2PhHPYM_5VPQe_y7LBF=hSfv0RCQ@mail.gmail.com>
To: W3C WAI GL <w3c-wai-gl@w3.org>
Cc: Richard Ishida <ishida@w3.org>, John Foliot <john@foliot.ca>, Janina Sajka <janina@rednote.net>, Katie Haritos-Shea <ryladog@gmail.com>
I’d be curious about support across screen readers. I have made the
assumption, perhaps prematurely, that support was still poor.

But to the problem, it seems that

* Developers will never mark up language and changes in language
consistently, for lack of knowledge and discipline reasons (developer =
anyone touching HTML, which includes a vast pool of novices).

* Tools will never get automatic language detection entirely right.


* The cost of manually marking up languages is much higher (recurring) than
of determining them automatically.

(This last point seems to speak against the “easy” solution of just
requiring both.)

So to rephrase the point:

* What is the bigger problem from an accessibility standpoint—all the
developers who don’t mark up languages, or all the tools (rather, instances
in) which don’t detect languages correctly?


* Granted language annotations are useful (given sufficient support), how
strong must any guidelines be in this regard? Developers may/should/must
mark up languages and changes in language?

—I realize I should have gone about this a bit differently, as a different
way of stating the problem was possibly more useful for WCAG and UAAG.

The subject line is misleading… I originally meant this more along the
lines of “useful for a developer to handle.”

Jens O. Meiert
Received on Tuesday, 12 August 2014 10:28:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:16 UTC