Re: Moving focus to another place after pressing a button

I think there are some buttons that should move focus- so we’d need to tease out the factors.   But in this case from Jake the buttons really sound like checkboxes - and checking those should not move focus.  

Jon

Sent from my iPhone

> On Jul 25, 2019, at 4:28 AM, Alastair Campbell <acampbell@nomensa.com> wrote:
> 
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 
>> On 25/07/2019 07:37, Abma, J.D. (Jake) wrote:
>> - after clicking on a filter button the page filters the results and
>> focus is placed to the first product link
> 
> I agree with Patrick, and I've been wondering if there is a potential SC to help nudge people towards good practice on focus management.
> 
> Marcy Sutton summarised some issues & recommendations for this here:
> https://www.gatsbyjs.org/blog/2019-07-11-user-testing-accessible-client-routing/#common-accessibility-barriers-in-client-rendered-web-apps

> 
> Something to the effect that navigation (links, things with a <nav> that load new content) should move the focus, buttons (controls) should not move focus.
> 
> Too often I've come across teams adding aria-live to a <main> or some such counter-productive solution.
> 
> An SC may not be the answer, but if there is a consensus on the issues & recommendations perhaps something could spring from that.
> 
> Cheers,
> 
> -Alastair

Received on Thursday, 25 July 2019 12:14:25 UTC