Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

TAB key Focus on disabled elements - Pagination #5151

Closed
iamvenkat45 opened this issue Jan 6, 2016 · 5 comments
Closed

TAB key Focus on disabled elements - Pagination #5151

iamvenkat45 opened this issue Jan 6, 2016 · 5 comments

Comments

@iamvenkat45
Copy link

When use TAB key to focus elements, it is able to focus on disabled elements like “Previous” insteading of focus on only enabled elements like 1, 2, "Next".

Can we know on how to remove the focus on "previous" when this is disabled.

@icfantv
Copy link
Contributor

icfantv commented Jan 6, 2016

@iamvenkat45, the pagination component does not have any key or focus handling code - everything you're talking about is handled via the browser. For UI Bootstrap's part we do set the disabled class on the component when ng-disabled is true.

Some quick googling yielded this link, which may be what you're looking for.

In the future, if you think you've found a bug, please follow these instructions as we do not use our issues forum for support requests. Rather, those should be directed towards SO as documented here. Thanks.

@iamvenkat45
Copy link
Author

@icfantv thanks for the quick reply.

Disabled class is set on the component but not on anchor tag and so the previous button is disabled but sill focussed.
The problem is when we use the TAB key, still the "previous" button is highlighted or focused on TAB navigation which shouldn't be.

As per your suggestion for this link, This only makes the outline to none.
Actually the navigation should jump to next enabled link/element not with only making it focus none when disabled.

@icfantv
Copy link
Contributor

icfantv commented Jan 6, 2016

@iamvenkat45, marking the anchor tag as disabled does not rectify the issue as you can see here.

I'm not yet convinced there's anything for us to do here. @wesleycho or @Foxandxss, thoughts?

@wesleycho
Copy link
Contributor

This does sound like an accessibility issue to me.

@wesleycho
Copy link
Contributor

Forgot to put the issue # in the commit, but this is addressed via 1a870a3.

@wesleycho wesleycho added this to the 2.0.0 milestone Jun 13, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants