my test samples were just trying to recreate a base magellan component. Odd thing is I am having problems when hand coding it with F6.2 in that the first link is always active because it gets stickied of the section scrolls to it. I think I have the sticky stuff wrong. CC works, except for the active class thing.
The code I posted earlier will work on your project, with the addition of Alter Eagle's fix included here;
<style media="screen" type="text/css">
.active {
color:yellow !important;
background: red; }
</style>
Jamo's idea goes right to the specific element, but I wanted to find a more clean fix that would be more congruent with the Magellan's plugin features. For instance, you can specify a specific class for the active class, it does not have to be ".active" Foundation has a default styling for .active and that is what Magellan defaults to. And if you change the classes of the links, or rename them, you won't have to rename the your substitute active class.
The above code needs to be added in a external stylesheet your create and add to the project, or add it to the page in the header section. I tested the attribute:
data-active-class="YourSpecialClass"
and that will work too so you can have different classes than just one class of "active" with this solution. I am pretty sure there are only two properties for the default active class in Foundation, so anything else you add to it should be good. For styling in RSD, you might was to duplicate the menu line, then style it how you want for the active class - preview in a browser, view the source code, find the class and copy it o your style sheet.