Re: Footnotes and Tooltips

--00000000000036e31105a45c2b4f
Content-Type: text/plain; charset="UTF-8"

It isn't the mose hover functionality that is the problem in the popup
method. In mouse use it doesn't matter if the popup overlays other content
on hover because the user simply moves the pointer away to stop the hover
and they can see the content again.

The issue of obscuring content potentially occurs in keyboard navigation
where users use the Tab key to jump from one link or button to the next. If
the popup/tooltip appears as soon as keyboard focus lands on the footnote
reference, then that is an accessibility issue for those users as it hides
what's underneath (and also because it foreces them to see the popup text
when they haven.t asked to do so). That is why the references must be
marked up as buttons that only reveal the popup if the keyboard user
presses Enter or Spacebar. That way the keyboard user can read the ordinary
content first, and they only get to see the popup text if they specifically
ask to, i.e. if they operate the button.

So I hope that makes it clearer, and maybe it also explains why Caroline's
vendor found an issue with it? (- if they had some other problem with it
perhaps you could share exactly what they actually said about it so we can
consider that. But I am not clear why you say the mouse user has to "click
away" to see the underlying content if they used hover to see it? It looks
like they weren't looking at a hover case).

Jeanna, I suggested the popup method (and your client asked for that) as an
alternative to showing footnotes, not in addition to them. There is no
actual need to show the footnotes at all if the same texts are shown as
popups. You might feel that it is good to show the footnotes at the bottom
as well (and if the footnotes are specially important legally your legal
people might insist on it), but in that case there would be no need to
provide any mechanism to jump down to them from the references because the
popup texts do that job for all users including blind and keyboard users -
if marked up correctly. I agree trying to make the references both open a
popup and provide a link to a footnote certainly would be difficult, but
that is not the intention of this method.

Finally, screen reader users can hear what's in the popup boxes when they
appear. In your case the developer must give the popup container an
aria-labelledby attribute that references the text in the popup (i.e. what
you originally has as a footnote). Then when the popup appears they must
use the JavaScript focus() function to place focus on the container; that
triggers screen readers into announcing the text inside it. That is just
standard practice for all popup dialogs. So all users are accounted for by
this method, no one has to navigate down to footnotes at the bottom of the
page.

Regards,
Guy Hickling

--00000000000036e31105a45c2b4f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif;font-size:small;color:#4c1130">It isn&#39;t the mose hover =
functionality that is the problem in the popup method. In mouse use it does=
n&#39;t matter if the popup overlays other content on hover because the use=
r simply moves the pointer away to stop the hover and they can see the cont=
ent again. <br></div><div class=3D"gmail_default" style=3D"font-family:treb=
uchet ms,sans-serif;font-size:small;color:#4c1130"><br></div><div class=3D"=
gmail_default" style=3D"font-family:trebuchet ms,sans-serif;font-size:small=
;color:#4c1130">The issue of obscuring content potentially occurs in keyboa=
rd navigation where users use the Tab key to jump from one link or button t=
o the next. If the popup/tooltip appears as soon as keyboard focus lands on=
 the footnote reference, then that is an accessibility issue for those user=
s as it hides what&#39;s underneath (and also because it foreces them to se=
e the popup text when they haven.t asked to do so). That is why the referen=
ces must be marked up as buttons that only reveal the popup if the keyboard=
 user presses Enter or Spacebar. That way the keyboard user can read the or=
dinary content first, and they only get to see the popup text if they speci=
fically ask to, i.e. if they operate the button. <br></div><div class=3D"gm=
ail_default" style=3D"font-family:trebuchet ms,sans-serif;font-size:small;c=
olor:#4c1130"><br></div><div class=3D"gmail_default" style=3D"font-family:t=
rebuchet ms,sans-serif;font-size:small;color:#4c1130">So I hope that makes =
it clearer, and maybe it also explains why Caroline&#39;s vendor found an i=
ssue with it? (- if they had some other problem with it perhaps you could s=
hare exactly what they actually said about it so we can consider that. But =
I am not clear why you say the mouse user has to &quot;click away&quot; to =
see the underlying content if they used hover to see it? It looks like they=
 weren&#39;t looking at a hover case).<br></div><div class=3D"gmail_default=
" style=3D"font-family:trebuchet ms,sans-serif;font-size:small;color:#4c113=
0"><br></div><div class=3D"gmail_default" style=3D"font-family:trebuchet ms=
,sans-serif;font-size:small;color:#4c1130">Jeanna, I suggested the popup me=
thod (and your client asked for that) as an alternative to showing footnote=
s, not in addition to them. There is no actual need to show the footnotes a=
t all if the same texts are shown as popups. You might feel that it is good=
 to show the footnotes at the bottom as well (and if the footnotes are spec=
ially important legally your legal people might insist on it), but in that =
case there would be no need to provide any mechanism to jump down to them f=
rom the references because the popup texts do that job for all users includ=
ing blind and keyboard users - if marked up correctly. I agree trying to ma=
ke the references both open a popup and provide a link to a footnote certai=
nly would be difficult, but that is not the intention of this method.</div>=
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif;f=
ont-size:small;color:#4c1130"><br></div><div class=3D"gmail_default" style=
=3D"font-family:trebuchet ms,sans-serif;font-size:small;color:#4c1130">Fina=
lly, screen reader users can hear what&#39;s in the popup boxes when they a=
ppear. In your case the developer must give the popup container an aria-lab=
elledby attribute that references the text in the popup (i.e. what you orig=
inally has as a footnote). Then when the popup appears they must use the Ja=
vaScript focus() function to place focus on the container; that triggers sc=
reen readers into announcing the text inside it. That is just standard prac=
tice for all popup dialogs. So all users are accounted for by this method, =
no one has to navigate down to footnotes at the bottom of the page.<br></di=
v><div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif=
;font-size:small;color:#4c1130"><br></div><div class=3D"gmail_default" styl=
e=3D"font-family:trebuchet ms,sans-serif;font-size:small;color:#4c1130"></d=
iv><div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_=
signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><di=
v><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><span s=
tyle=3D"font-family:trebuchet ms,sans-serif"><span style=3D"color:rgb(76,17=
,48)">Regards,<br>Guy Hickling<br><br></span><br></span><br></div></div></d=
iv></div></div></div></div></div></div></div></div></div></div></div></div>

--00000000000036e31105a45c2b4f--