{{!
    @template local_kid/tabs

    Real page-to-page navigation between sibling screens (each tab is a full
    URL, not a same-page panel switch), so this uses DSFR's fr-nav (the
    component meant for exactly that — a nav with aria-current="page" on the
    active link) rather than fr-tabs, which assumes ARIA tablist/tabpanel
    semantics and same-page JS-driven panel visibility that don't apply here.

    * tabs - array of { label, url, isactive }
}}
<nav class="fr-nav fr-mb-4w" role="navigation" aria-label="{{#str}}tabs_nav_label, local_kid{{/str}}">
    <ul class="fr-nav__list">
        {{#tabs}}
        <li class="fr-nav__item">
            <a href="{{url}}" class="fr-nav__link" {{#isactive}}aria-current="page"{{/isactive}}>{{label}}</a>
        </li>
        {{/tabs}}
    </ul>
</nav>
