W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

More on not using Screen Magnification as an example

From: Wayne Dick <waynedick@knowbility.org>
Date: Thu, 23 Apr 2015 16:48:55 -0700
Message-ID: <CAC9gL76UFKq23EbM9uUJdK0eYPERVMrgsVVFeBbwL1TtO5yh6A@mail.gmail.com>
To: WAI Interest Group <w3c-wai-ig@w3.org>
 The reason screen magnification does not belong in the new
 Accessibility API Mappings 1.1 document is because the primary
 functions of screen magnification and the accessibility APIs are
 disjoint. Screen magnification works just as well on a bitmap as
 it does on a WCAG 2.0 Level AAA document with perfect ARIA.

I am fully aware that modern screen magnification software uses
some features of the DOM supported by WCAG 2.0. These are mostly
used to enable vertical navigation.  I have not experienced any
evidence of screen magnification vendors using ARIA, but maybe
someone knows more on this.

The main point is this. The primary work of a screen magnifier
is enlargement with very intelligent curve smoothing.  While
this requires really smart programming the same effect can be
achieved with a closed circuit TV.   Screen magnification has
no place in a document about APIs that support assistive
technology. CCTVs and magnifying glasses are  just as relevant
screen magnifiers in this context.

In fact, magnfying glasses and closed circuit TV is just as relevant as
screen magnification within the entire context of WCAG.  WCAG is
unnecessary for screen magnification to work.
Received on Thursday, 23 April 2015 23:49:22 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC