-
Notifications
You must be signed in to change notification settings - Fork 754
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
Keyboard Accessibility #260
Comments
Hi robb2! I'm a bit embarrassed to say, but I had no clue about the section 508 compliance. I'll read up on it and fix any recommendations they suggest. Thanks! |
Just wanted to note that the grouping headers are not keyboard accessible. Obviously, full Section 508 compliance would be the end goal, but adding keyboard accessibility to the grouping headers would be a big deal for my organization. Thanks for all the work on a great tool. |
Hi @cnccnc! Group headers are now keyboard accessible (in the master branch), thanks! |
@cnccnc, if there are any other accessibility issues, please don't hesitate to share them with me. Thanks! |
AMAZING. I hoped to get that issue on the radar for some later date, and it was fixed in a couple hours. A quick test says it works perfectly. Will test/implement in live environment soon. This issue was holding up some content reorganization we wanted to do. Thank you! |
Has anyone had experience with keyboard tabbing through tablesorter, or satisfying accessibility issues such as Section 508 compliance with table sorter? any issues? Thanks, Rob
The text was updated successfully, but these errors were encountered: