Skip to content

Tabs - Clicking a Tab should allow the user to start using keyboard navigation #1053

Open
@SiTaggart

Description

@SiTaggart

I think the markup is out of date, which is why this is happening.

Each tab has 2 focusable elements; the list item and it's nested anchor.

For keyboard navigation the list item is wired up to be the tab which get's aria-selected and listens to key events.

A mouse user will click the tab, but because it has a nested anchor element, the anchor takes the users focus, which has no semantic meaning and does not respond to key events.

If you match SLDS markup this should go away

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions