Skip to content

Tabs: added keyboard accessibility. Fixes #3079. Tabs were not accessible #205

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
wants to merge 1 commit into from
Closed

Conversation

eikes
Copy link
Contributor

@eikes eikes commented May 5, 2011

Tabs: added keyboard accessibility. Fixes #3079. Tabs were not accessible

@gnarf
Copy link
Member

gnarf commented May 24, 2011

Please take a look at our coding standards there are a few issues I noticed quickly.

  • Missing empty line before comments
  • Multiple var statements in one function.
  • Tabs on empty lines ( empty lines should be empty, void of tabs )

Also, not sure if you looked at the tabs accessibility requirements on the planning wiki or not, but I don't think you have followed them.

@eikes
Copy link
Contributor Author

eikes commented May 24, 2011

Can you be more specific as to what parts of the accessibility requirements you think have been met? As far as I can tell all the keyboard interactions as described in "4.4 Accessibility recommendations / Keyboard Accessibility" are implemented, because that's what I used as requirements when implementing it, thus fixing the issue described in the bug tracker.

Cleaning the code is of course no problem, but functionality should be discussed first I think.

@gnarf
Copy link
Member

gnarf commented May 25, 2011

  • The entire section of key events while inside tabs.
  • The alt+del functionality.
  • "enter"

@scottgonzalez
Copy link
Member

Thanks, but we're going to wait on adding keyboard accessibility until we can discuss this more. We're considering having delayed activation of tabs as well.

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

Successfully merging this pull request may close these issues.

3 participants