<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body smarttemplateinserted="true">
<div>Late to follow up on this; but wanted to add my two cents.</div>
<div>By default, I think it would make less confusion for most to
open a link in the same tab. However, others, like me, prefer
lots of tabs, "tabittis"; they can right click or (on windows
keyboards, context menu key) or another custom or browser command
(e.g. command click in Safari) to open in a new tab. <br>
</div>
<div>Lastly, much of the default behavior of opened links and
tabs/windows can be customized per the browser settings.<br>
</div>
<div><br>
</div>
<div>Chris Johnson<br>
Accessibility Consultant<br>
expressABLE<br>
150 East B St #44<br>
Casper, WY 82602<br>
<a class="moz-txt-link-abbreviated" href="mailto:chris@expressable.org">chris@expressable.org</a><br>
<a href="https://www.facebook.com/Expressable-405824279606760/">Facebook</a><br>
<a href="https://twitter.com/eableorg">Twitter</a><br>
<a href="https://www.linkedin.com/in/chrisjohnson1expressable">LinkedIn</a><br>
<br>
"Express, Educate & Employ your Abilities with the right
technology and training!"<br>
<br>
<p> </p>
</div>
<div class="moz-cite-prefix">On 4/22/22 10:28 AM, glen walker wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANcjB1=7Tr6QN_sMOPskTM0Pjsi_=k1xpcoJtoppwEBpDOH=FQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>The general result of many WCAG success criteria is that
they don't define *exactly* what passes or fails. This is
where experience comes in but is still subjective. All I was
saying is that when you click on a link, you expect a change
of context. That's the whole point of a link. Does WCAG
require notifying the user that it opens in the same tab vs a
new tab? Again, subjective. The "<a
href="https://www.w3.org/TR/WCAG21/#dfn-change-of-context"
moz-do-not-send="true">change of context</a>" link within
the normative definition of WCAG 3.2.2 makes the definition
normative too. And that definition includes other definitions
(user agent, viewport, and content) which makes those
definitions normative. So you're getting closer to having an
*exact* meaning but not quite. For example, the <a
href="https://www.w3.org/TR/WCAG21/#dfn-viewport"
moz-do-not-send="true">viewport definition</a> is "object in
which the user agent presents content". That seems kind of
vague. And then a <a
href="https://www.w3.org/TR/WCAG21/#h-note-139"
moz-do-not-send="true">subsequent note</a> says "Viewports
include windows, frames, loudspeakers, and virtual magnifying
glasses". Loudspeakers? They lost me there. But "windows",
maybe that's closer to what we're talking about.</div>
<div><br>
</div>
<div>So I try to be careful if I state that WCAG *requires*
something or doesn't require something in absolute terms.
It's usually not that simple.</div>
<div><br>
</div>
<div>Should you indicate a link opens in a new window? Does it
matter if WCAG requires it or not? Does WCAG need to be the
big stick to convince you to have a "new window" indicator?
What if you just discussed it from a UX perspective? If you
think it'll be good for your user, then do it (provided it
doesn't make the interface inaccessible to some people).</div>
<div><br>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
athen-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:athen-list@mailman12.u.washington.edu">athen-list@mailman12.u.washington.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman12.u.washington.edu/mailman/listinfo/athen-list">http://mailman12.u.washington.edu/mailman/listinfo/athen-list</a>
</pre>
</blockquote>
</body>
</html>