I'm currently working on a Large accessibility sensitive project using bootstrap, which is a similar framework.
In general there were not to many issues with using the framework. There are a few things you should check though.
Semantic mark up. For example Bootstrap uses the i tag for icons. We rewrote the icons styles to use background images on other elements using pseudo elements.
It seems Foundation have worked through this problem: http://www.zurb.com/article/1047/bigger-stronger-new-accessible-foundation
Js reliance. For example Foundation shows hidden content when the tab is selected using javascript. Dependence on JS may well fail your accessibility requirements. You may need to alter the code to display elements by default and hide if JS present. Use Modernizer to control that. There may be other JS dependency issues with zurb you will have to alter.
A user on github identified some issues with zurb .
https://github.com/zurb/foundation/issues/428
These could be worth checking. zurb by default doesn't use aria codes. Error messages are indicated with color.
All these things are the sort of issues you would have to work through without a framework. The framework isn't blocking you from achieving accessibility compliance - but it isn't all done for you.