W3C home > Mailing lists > Public > public-indie-ui@w3.org > February 2013

Re: Proposed Set of Needs/Preferences for v1

From: Sangwhan Moon <smoon@opera.com>
Date: Thu, 7 Feb 2013 01:33:29 +0900
Message-Id: <67CF43F9-5E75-4594-926F-130FC3E604A8@opera.com>
To: Indie UI <public-indie-ui@w3.org>

On Feb 6, 2013, at 11:30 PM, Andy Heath wrote:

> Attached are the proposed preferences for V1 as promised.  They are distilled/smplified from the IMS AfA 3.0 preferences.  A very few small ones added. Apologies for the slight lateness and for the zip file but it was tricky to maintain the style sheets/macros used in editing the document without doing that.

I've reviewed the document for the last hour, and must point out that almost none of
these preferences are available on a user agent level implementation. Either they
need to be propagated from the host OS or accessibility software. (in which case,
introduces the question of "via what protocol?")

At the moment, the only information that Opera (sorry for making Opera the example)
can provide from this perspective is "screen reader active and exists?" = true | false.
I don't think other browsers are significantly more advanced in this regard either.

Some operating systems provide this information on a system level, but not all OSes
provide ways to determine this in a reliable manner. And for certain properties (e.g. tactile),
I'm afraid there isn't a standardized way to know if such a device exists - making it quite
challenging to implement for browser vendors.

Would there be any possibility to revise this to a level where we have a common set
of things that are readily available on at least the three major operating systems?

-- 
Sangwhan Moon, Opera Software ASA

P.S. Will there be real "browser preferences" in the spec too?
Received on Wednesday, 6 February 2013 16:34:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 February 2013 16:34:05 GMT