Issue 637: Keyboard access, tabbing
Status:  Released
Owner: ----
Closed:  Aug 2014
Reported by n8cs...@gmail.com, Sep 9, 2010
I am using fullCalendar on a project that requires Section 508 compliance. It appears that fullCalendar does not currently comply, as it does not support keyboard access. If I select an element on my page before fullCalendar and then a I try to tab to it, it skips right over it. 

I added tabindex="0" to the div in which fullCalendar is rendered, so I can now tab to it, but when I tab again, it skips over everything inside of fullCalendar.

I would love to see keyboard support added to fullCalendar. As it is now, we have to provide an alternative interface to be 508 compliant.
Oct 7, 2010
Project Member #1 adamrs...@gmail.com
will look into this
Summary: keyboard access (section 508 compliance)
Status: Maybe
Dec 26, 2010
#2 emil.hul...@gmail.com
This would be awesome. I hope you find the time to look into it. 

Allt the best,
em
Jan 28, 2011
#3 emil.hul...@gmail.com
Any progress on this? It would allow a much wider usage of your great work. 
Jul 31, 2013
#4 JohnnyFu...@gmail.com
I'm working on an adding compliance to an existing application that uses FullCalendar 1.4.3 and it would be great if we could just upgrade instead of completely rewriting the calendar portion of the app, which is the central feature.  I suspect that more and more sites will be looking add compliance.  
Aug 13, 2013
Project Member #5 adamrs...@gmail.com
(No comment was entered for this change.)
Summary: Keyboard access (section 508 compliance) (was: keyboard access (section 508 compliance))
Status: Discussing
Labels: Type-Feature
Aug 16, 2013
#6 manjunit...@gmail.com
I am working on a federal project and the one reason I can't use FullCalendar is because it is not fully accessible via keyboard. This enhancement will be very nice to have. Thank you.
Aug 18, 2013
Project Member #7 adamrs...@gmail.com
 Issue 1396  has been merged into this issue.
Aug 18, 2013
Project Member #8 adamrs...@gmail.com
(No comment was entered for this change.)
Summary: Keyboard access, tabbing (was: Keyboard access (section 508 compliance))
Status: Accepted
Apr 1, 2014
#9 laurent....@gmail.com
Hi 
since wich version is this feature implemented ?
Thanks
Apr 4, 2014
#10 Mestopho...@gmail.com
I'm using 1.6.4

The change wasn't in there, but I fixed it myself.

Line 797 : I changed the <span tag to <a href=#
Line 804 : I changed the </span> to </a>

This made the navigational bar tabbable and works in IE-8 as well.

Jun 15, 2014
Project Member #11 adamrs...@gmail.com
(No comment was entered for this change.)
Labels: milestone-skeleton
Jul 23, 2014
Project Member #12 adamrs...@gmail.com
In v2.1 (beta), the buttons are now rendered with real <button> tags and tabbing is now possible

http://blog.arshaw.com/1/post/2014/07/fullcalendar-210-beta.html

I would really appreciate if you could verify this. Thanks a lot!
Aug 14, 2014
Project Member #13 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Implemented
Aug 26, 2014
Project Member #14 adamrs...@gmail.com
This issue has been resolved with the official release of v2.1.0:
http://blog.arshaw.com/1/post/2014/08/fullcalendar-210-released.html

Please post any follow-up bug reports or feature requests as separate issues. Thanks.
Status: Released