<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1284996801;
mso-list-template-ids:-124599420;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>From WCAG 2.1:<br><br><i>changes of context</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>major changes in the content of the <a href="https://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web page</a> that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>Changes in context include changes of:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><a href="https://www.w3.org/TR/WCAG21/#dfn-user-agents">user agent</a>; <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><a href="https://www.w3.org/TR/WCAG21/#dfn-viewport">viewport</a>; <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>focus;<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><a href="https://www.w3.org/TR/WCAG21/#dfn-content">content</a> that changes the meaning of the <a href="https://www.w3.org/TR/WCAG21/#dfn-web-page-s">Web page</a> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Note<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in'>A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the context, unless they also change one of the above (e.g., focus). <o:p></o:p></p><p class=MsoNormal>So, a change of context COULD be a change of content.<br><br>Also, if new content appears on the page it could fall under 4.1.3 Status messages depending on the new content and if it is persistent.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> athen-list <athen-list-bounces@mailman12.u.washington.edu> <b>On Behalf Of </b>Steve Green<br><b>Sent:</b> Friday, April 22, 2022 10:17 AM<br><b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br><b>Subject:</b> Re: [Athen] Website accessibility<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>I regard changes to content on the same page as being a WCAG SC 1.3.1 issue on the basis that visual changes to content should be conveyed programmatically. We usually recommend ARIA live regions for this, with their assertiveness depending on the circumstances.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>We would not usually move the focus because that would be a change of context. If the change of content has been adequately described by the live region and the page contains appropriate headings or other landmarks, it should be easy for a screen reader user to navigate to the new content, assuming they want to do so. There may be situations where it would make sense to move the focus automatically, but I can’t think of any other that simulating a page loading in a single-page application.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Steve<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu">athen-list-bounces@mailman12.u.washington.edu</a>> <b>On Behalf Of </b>Robert Spangler<br><b>Sent:</b> 22 April 2022 14:40<br><b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu">athen-list@u.washington.edu</a>><br><b>Subject:</b> Re: [Athen] Website accessibility<o:p></o:p></p></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-GB>Hey Steve, how about when activating a link causes new content to appear elsewhere on the page? How is that supposed to be handled? I notice quite frequently when this happens, the screen reader says nothing and the focus isn't moved to the position on the page with the new content. I'm left wondering if the link was activated at all (links not activating is an issue at times) or searching the page for the new content. <o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>In regards to links opening in new tabs, I don't care much for the practice, but at least a message stating, "Link opened in new tab" or something like that would alleviate the annoyance. I'm not sure of the best way to handle this for other situations, but at least for screen readers this would be appropriate.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Thanks,<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Robert<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><div><p class=MsoNormal><span lang=EN-GB>On Fri, Apr 22, 2022 at 9:09 AM Steve Green <<a href="mailto:steve.green@testpartners.co.uk">steve.green@testpartners.co.uk</a>> wrote:<o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>Opening a new tab *is* considered a change of context. WCAG specifically defines a change of viewport as a change of context. See <a href="https://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html#dfn-changes-of-context" target="_blank">https://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html#dfn-changes-of-context</a> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>However, for links, it’s an expected change of context. Everyone knows that it can happen, even if they don’t expect it to in a particular circumstance.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>I am certainly not advocating opening links in new tabs – I have seen it cause plenty of problems during user testing with screen reader users, screen magnifier users and dyslexic people. But it’s only an annoyance, not a complete barrier.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>And WCAG 2.1 AA is hardly the barest minimum of accessibility – a website that is fully conformant will be accessible to the vast majority of disabled people.<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>Steve Green<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>Managing Director<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB>Test Partners Ltd<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu" target="_blank">athen-list-bounces@mailman12.u.washington.edu</a>> <b>On Behalf Of </b>Katherine Deibel<br><b>Sent:</b> 22 April 2022 13:55<br><b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br><b>Subject:</b> Re: [Athen] Website accessibility<span lang=EN-GB><o:p></o:p></span></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-GB> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>> There’s plenty of evidence that it does not confusion in some users, notably those with cognitive issues.<br><br>Argh… not enough caffeine yet. That should be:</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'> There’s plenty of evidence that it does create confusion in some users, notably those with cognitive issues.</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'> </span><span lang=EN-GB><o:p></o:p></span></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Katherine “Kate” Deibel, PhD</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Library Accessibility Specialist</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Twitter: <a href="https://twitter.com/metageeky" target="_blank"><span style='color:#0563C1'>https://twitter.com/metageeky</span></a><br>GitHub: <a href="https://github.com/metageeky" target="_blank"><span style='color:#0563C1'>https://github.com/metageeky</span></a></span><span lang=EN-GB><o:p></o:p></span></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'> </span><span lang=EN-GB><o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu" target="_blank">athen-list-bounces@mailman12.u.washington.edu</a>> <b>On Behalf Of </b>Katherine Deibel<br><b>Sent:</b> Friday, April 22, 2022 8:44 AM<br><b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br><b>Subject:</b> Re: [Athen] Website accessibility<span lang=EN-GB><o:p></o:p></span></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>I’ll stand corrected but it greatly bothers me that opening a new tab is not considered a change of context. There’s plenty of evidence that it does not confusion in some users, notably those with cognitive issues. Plus, it creates a whole new browsing context in terms of browser history. </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'> </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Once again, a good example of how WCAG is the barest minimum of accessibility.</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'> </span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Katherine “Kate” Deibel, PhD</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Library Accessibility Specialist</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'>Twitter: <a href="https://twitter.com/metageeky" target="_blank"><span style='color:#0563C1'>https://twitter.com/metageeky</span></a><br>GitHub: <a href="https://github.com/metageeky" target="_blank"><span style='color:#0563C1'>https://github.com/metageeky</span></a></span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:12.0pt;font-family:"Tahoma",sans-serif'> </span><span lang=EN-GB><o:p></o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu" target="_blank">athen-list-bounces@mailman12.u.washington.edu</a>> <b>On Behalf Of </b>glen walker<br><b>Sent:</b> Friday, April 22, 2022 12:58 AM<br><b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br><b>Subject:</b> Re: [Athen] Website accessibility<span lang=EN-GB><o:p></o:p></span></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=EN-GB><o:p></o:p></span></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>> Strictly WCAG, you need to provide an indication of this unexpected behavior as it creates a change of context for the user.<span lang=EN-GB><o:p></o:p></span></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=EN-GB><o:p></o:p></span></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>That's a matter of interpretation. If you're alluding to WCAG 3.2.2 On Input, clicking a link and going to a new page (whether in the existing tab or a new tab/window) is *expected* behavior because that's what a link does. You don't have to tell the user you're going to do that. <span lang=EN-GB><o:p></o:p></span></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=EN-GB><o:p></o:p></span></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>We had a discussion about this recently on the WebAIM forum - <a href="https://webaim.org/discussion/mail_thread?thread=10383#post0" target="_blank">https://webaim.org/discussion/mail_thread?thread=10383#post0</a><span lang=EN-GB><o:p></o:p></span></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=EN-GB><o:p></o:p></span></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <span lang=EN-GB><o:p></o:p></span></p></div></div></div><p class=MsoNormal><span lang=EN-GB>_______________________________________________<br>athen-list mailing list<br><a href="mailto:athen-list@mailman12.u.washington.edu" target="_blank">athen-list@mailman12.u.washington.edu</a><br><a href="http://mailman12.u.washington.edu/mailman/listinfo/athen-list" target="_blank">http://mailman12.u.washington.edu/mailman/listinfo/athen-list</a><o:p></o:p></span></p></blockquote></div><p class=MsoNormal><span lang=EN-GB><br clear=all><o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-GB>-- <o:p></o:p></span></p><div><div><div><div><div><div><div><div><p class=MsoNormal><span lang=EN-GB>Robert Spangler<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Disability Services Technical Support Specialist<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Office of Learning Resources<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Ryan C. Harris Learning Teaching Center (LTC)<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>Roesch Library Room: 023<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-GB>Phone: 937-229-2066<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>For Deaf/Hard of Hearing, call 711 (Ohio Relay)<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>For office hours and further OLR information, please visit <a href="http://go.udayton.edu/olr" target="_blank">go.udayton.edu/olr</a><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>CONFIDENTIALITY NOTICE<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB>The information contained in this electronic message is confidential and intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail or any of its components is strictly prohibited. If you have received this email in error, please "reply" to the sender.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div></div></div></div></div></div></div></div></div></div></body></html>