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

Re: [user-context] What are the use cases for exposing screen reader or magnifier version info?

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Fri, 1 Feb 2013 14:09:39 -0600
To: Jason White <jason@jasonjgw.net>
Cc: public-indie-ui@w3.org
Message-ID: <OFFBAAC864.BC6BC72F-ON86257B05.006F1EF3-86257B05.006F2E74@us.ibm.com>

I am extremely worried about privacy issues around exposing the AT a person
is using.


Rich Schwerdtfeger

From:	Jason White <jason@jasonjgw.net>
To:	public-indie-ui@w3.org,
Date:	12/06/2012 08:04 PM
Subject:	Re: [user-context] What are the use cases for exposing screen
            reader  or magnifier version info?

James Craig <jcraig@apple.com> wrote:

> Assistive technology vendors are not beholden to W3C specifications (and
> most AT vendors are notoriously uninvolved in the standardization
> so exposing this information when it's absolutely necessary, (and only
> user content), is one attempt to reduce the unreliability of AT
> on the Web.

At a Web accessibility conference last week, a content author mentioned
to me as a highly desired feature due to bugs and limitations (often
version-specific) in various screen readers.

I am concerned however that the information is open to misuse: content
may start designing for the "most popular" ATs instead of writing according
spec. They can also ascertain which ATs are "most popular" for their
particular content by gathering data, which is not possible now, since the
name/version of the AT are not revealed.

Thus I have decidedly mixed feelings about this proposal and, frankly, I'm
sure whether the practical benefits of being able to work around certain
bugs/differences outweigh the opportunity to "design for the UA and AT
implementation" instead of designing to standards.

(image/gif attachment: graycol.gif)

Received on Friday, 1 February 2013 20:10:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:09:15 UTC