Skip to content

Accessibility: Notification drawer expand & collapse links are inaccessible via keyboard navigation #599

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
benjaminapetersen opened this issue Aug 28, 2017 · 6 comments · Fixed by #621
Assignees

Comments

@benjaminapetersen
Copy link
Member

The a ng-clicks in the header of the notification drawer need an empty href="" to be keyboard accessible (expand/collapse links).

Re this comment on origin-web-console PR 1326

Is there accessibility guidelines in upstream patternfly? This would be a great topic @ that level.

@jeff-phillips-18

@benjaminapetersen benjaminapetersen changed the title Notification drawer expand & collapse links are not accessible Accessibility: Notification drawer expand & collapse links are inaccessible via keyboard navigation Aug 29, 2017
@amarie401 amarie401 self-assigned this Sep 12, 2017
@cdcabrera
Copy link
Member

cdcabrera commented Sep 12, 2017

Quite a few potentials for this fix:

  • Per @amarie401 , href="javascript:void(0)"
  • dump a tab-index="0" on there (last resort)
  • ng-href="" ng-click="someEvent"
  • ng-href="" ng-click="someEvent($event)", and look at preventDefault in some form and maybe a hash in ng-href... though routing may be a concern

@jeff-phillips-18
Copy link
Member

href="" will work just fine (in angular)

@cdcabrera
Copy link
Member

cdcabrera commented Sep 12, 2017

href works... within some past projects, for future proofing, seen, and let Angular generate all of the attributes

@jeff-phillips-18
Copy link
Member

I assume you mean you'd prefer to go with ng-href ? If so, I'm ok with that as well.

@jeff-phillips-18
Copy link
Member

we don't want to simply tab-index="0" and we don't want to prevent default since we want to be able to activate these via the keyboard as well.

@cdcabrera
Copy link
Member

cdcabrera commented Sep 12, 2017

agreed, the potential for funkiness is well, funky

Edit: for consistency if we haven't been using ng-href and defaulting to href probably a good idea to keep it the same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants