[Athen] Website accessibility

[joe at a11yeval.com]

>From WCAG 2.1:


changes of context

major changes in the content of the Web page <https://www.w3.org/TR/WCAG21/#dfn-web-page-s>  that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously 

Changes in context include changes of:

1.      user agent <https://www.w3.org/TR/WCAG21/#dfn-user-agents> ; 

2.      viewport <https://www.w3.org/TR/WCAG21/#dfn-viewport> ; 

3.      focus;

4.      content <https://www.w3.org/TR/WCAG21/#dfn-content>  that changes the meaning of the Web page <https://www.w3.org/TR/WCAG21/#dfn-web-page-s>  

Note

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

So, a change of context COULD be a change of content.

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.

 

From: athen-list <athen-list-bounces at mailman12.u.washington.edu> On Behalf Of Steve Green
Sent: Friday, April 22, 2022 10:17 AM
To: Access Technology Higher Education Network <athen-list at u.washington.edu>
Subject: Re: [Athen] Website accessibility

 

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.

 

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.

 

Steve

 

 

From: athen-list <athen-list-bounces at mailman12.u.washington.edu <mailto:athen-list-bounces at mailman12.u.washington.edu> > On Behalf Of Robert Spangler
Sent: 22 April 2022 14:40
To: Access Technology Higher Education Network <athen-list at u.washington.edu <mailto:athen-list at u.washington.edu> >
Subject: Re: [Athen] Website accessibility

 

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.  

 

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.

 

Thanks,

Robert

 

 

On Fri, Apr 22, 2022 at 9:09 AM Steve Green <steve.green at testpartners.co.uk <mailto:steve.green at testpartners.co.uk> > wrote:

Opening a new tab *is* considered a change of context. WCAG specifically defines a change of viewport as a change of context. See https://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html#dfn-changes-of-context 

 

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.

 

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.

 

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.

 

Steve Green

Managing Director

Test Partners Ltd

 

 

From: athen-list <athen-list-bounces at mailman12.u.washington.edu <mailto:athen-list-bounces at mailman12.u.washington.edu> > On Behalf Of Katherine Deibel
Sent: 22 April 2022 13:55
To: Access Technology Higher Education Network <athen-list at u.washington.edu <mailto:athen-list at u.washington.edu> >
Subject: Re: [Athen] Website accessibility

 


> There’s plenty of evidence that it does not confusion in some users, notably those with cognitive issues.


Argh… not enough caffeine yet. That should be:

          There’s plenty of evidence that it does create confusion in some users, notably those with cognitive issues.

 

Katherine “Kate” Deibel, PhD

Library Accessibility Specialist

Twitter:  <https://twitter.com/metageeky> https://twitter.com/metageeky
GitHub:  <https://github.com/metageeky> https://github.com/metageeky

 

From: athen-list <athen-list-bounces at mailman12.u.washington.edu <mailto:athen-list-bounces at mailman12.u.washington.edu> > On Behalf Of Katherine Deibel
Sent: Friday, April 22, 2022 8:44 AM
To: Access Technology Higher Education Network <athen-list at u.washington.edu <mailto:athen-list at u.washington.edu> >
Subject: Re: [Athen] Website accessibility

 

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. 

 

Once again, a good example of how WCAG is the barest minimum of accessibility.

 

Katherine “Kate” Deibel, PhD

Library Accessibility Specialist

Twitter:  <https://twitter.com/metageeky> https://twitter.com/metageeky
GitHub:  <https://github.com/metageeky> https://github.com/metageeky

 

From: athen-list <athen-list-bounces at mailman12.u.washington.edu <mailto:athen-list-bounces at mailman12.u.washington.edu> > On Behalf Of glen walker
Sent: Friday, April 22, 2022 12:58 AM
To: Access Technology Higher Education Network <athen-list at u.washington.edu <mailto:athen-list at u.washington.edu> >
Subject: Re: [Athen] Website accessibility

 


> Strictly WCAG, you need to provide an indication of this unexpected behavior as it creates a change of context for the user.


 

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.  

 

We had a discussion about this recently on the WebAIM forum - https://webaim.org/discussion/mail_thread?thread=10383#post0

 

 

_______________________________________________
athen-list mailing list
athen-list at mailman12.u.washington.edu <mailto:athen-list at mailman12.u.washington.edu> 
http://mailman12.u.washington.edu/mailman/listinfo/athen-list




 

-- 

Robert Spangler

Disability Services Technical Support Specialist

Office of Learning Resources

Ryan C. Harris Learning Teaching Center (LTC)

Roesch Library Room: 023

Phone: 937-229-2066

For Deaf/Hard of Hearing, call 711 (Ohio Relay)

For office hours and further OLR information, please visit go.udayton.edu/olr <http://go.udayton.edu/olr> 

CONFIDENTIALITY NOTICE

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.

 

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