SOLVED: Accessibility: Skip link doesn't take keyboard focus after hitting enter

Bugs
1

Should be a relatively simple one here…

On loading a page and hitting tab, the first item to appear is the skip link (which is awesome, great work), but hitting enter on the skip link does NOT move keyboard focus into #bricks-content-wrapper, and hitting enter again returns to the header, and focuses on the first link after the skip link.

The desired behaviour should be: tab, skip link displays, enter, jump to #bricks-content-wrapper WITH keyboard focus, next tab goes to the first link in, or after, #bricks-content-wrapper

2

Hello @Pete could you please share the URL where this problem is happening?

Thank you

3

Don’t have a public URL to share unfortunately. But it should happen on any page on 1.3.

Test procedure:

  1. Load page
  2. Hit tab
  3. Hit enter
  4. Hit tab

Expected behaviour:

  1. Page loads
  2. Skip link appears
  3. Page moves to skip link # target
  4. Focus moves to first link within content

Actual behaviour:

  1. Page loads
  2. Skip link appears
  3. Page moves to skip link # target
  4. Focus goes back to nav menu and undoes skip
4

Ok, Now I got the issue. Thank you. We’ll investigate.

1 Like
5

Just needs the skip link # target to grab keyboard focus - I’m not at a computer right now to check, but it should be possible to set tab-index=“0” via attributes for the # main section

6

Hi @Pete

Bricks 1.3.1 is out and it has a fix for the issue you reported. It should now work as supposed.

Thank you for your report!

1 Like
7

@luistinygod

This issue is happening again in 1.5

Exactly the same as outlined above. I didn’t test it to confirm it was working between 1.3 and 1.5

8

Was early in a project so ended up just nuking and restarting, and it’s working. No clue what happened previously

1 Like
9

I’m glad you sort it out. Let us know if you find any other a11y issues!

Thank you
Luis

1 Like