[Athen] Website accessibility

[Chris Johnson]

Late to follow up on this; but wanted to add my two cents.
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.
Lastly, much of the default behavior of opened links and tabs/windows 
can be customized per the browser settings.

Chris Johnson
Accessibility Consultant
expressABLE
150 East B St #44
Casper, WY 82602
chris at expressable.org
Facebook <https://www.facebook.com/Expressable-405824279606760/>
Twitter <https://twitter.com/eableorg>
LinkedIn <https://www.linkedin.com/in/chrisjohnson1expressable>

"Express, Educate & Employ your Abilities with the right technology and 
training!"

On 4/22/22 10:28 AM, glen walker wrote:

> 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 "change of context 

> <https://www.w3.org/TR/WCAG21/#dfn-change-of-context>" 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 viewport definition 

> <https://www.w3.org/TR/WCAG21/#dfn-viewport> is "object in which the 

> user agent presents content".  That seems kind of vague.  And then a 

> subsequent note <https://www.w3.org/TR/WCAG21/#h-note-139> 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.

>

> 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.

>

> 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).

>

>

> _______________________________________________

> athen-list mailing list

> athen-list at mailman12.u.washington.edu

> http://mailman12.u.washington.edu/mailman/listinfo/athen-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20220502/87060455/attachment.html>