W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > March 2016

Re: conflicting ARIA functionality

From: Wayne Dick <wayneedick@gmail.com>
Date: Tue, 22 Mar 2016 06:34:50 -0700
Message-ID: <CAJeQ8SBmSp7+WLn6R8ANpdCmQHh1wYs3S1K-ScA2Bm78KPkR-w@mail.gmail.com>
To: "Rochford, John" <john.rochford@umassmed.edu>
Cc: ALAN SMITH <alands289@gmail.com>, Jonathan Avila <jon.avila@ssbbartgroup.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
‚ÄčARIA is really for screen readers and non-visual users. There are many of
these ambiguities. For example, developers may use aria-hidden so that
screen reader users don't hear something ugly like automatically generated
MathJax images of math. The effect of this is to remove the content from
the accessibility API.  Is that content important to a user of another AT?‚Äč

I found the "learn more" issue important because reasonable enlargement can
remove the "learn more" from it's context even visually.  What does an
enlargement system do. Can it know the context text is no longer on the
screen?

This sounds like an issue for the LVTF. Ambiguity of accessibility.

Right now I can only remember aria-hidden as an issue, but when I was
working on digital high stakes assessment I ran into a few more.

Wayne
Received on Tuesday, 22 March 2016 13:35:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:23:18 UTC