Docs

Main site

Installation Browser support Extend config MCP server
Validation Page speed testing Responsive design
Accordion Aspect Ratio Avatar Badge Banner Bento Grid Blockquote Breadcrumbs Button Callout Card Drawer Dropdown Link Modal Navbar Navblock Pagination Popover Progress Separator Tabs Timeline Toast Tooltip
Checkbox Datepicker File upload Form field Input Label OTP Radio Range Select Textarea Toggle
Header Footer
Accordion Auth Checkbox & Radio Content Drawers Features Modals Statistics & Metrics Teams
Address Contact number Currency symbol Date Emirates ID Name
Close
Home Documentation Components Footer

Footer

A Footer is the standardised bottom-of-page region for UAE Federal Government websites — a highlights row, a brand and navigation column grid, and a bottom bar for copyright and legal links, rendered as a single footer landmark region. Use exactly one per page, placed at the very end of the document.

Navigation Layout
Status
Active
Introduced
4.0.x
View source code

Introduction

aegov-footer renders a single top-level footer element — the page's contentinfo landmark. Use exactly one per page, placed at the very end of the document, not nested inside main or any other landmark.

Internally it embeds aegov-footer-highlights as its hero row — the same relationship aegov-header has with aegov-header-banner — forwarding the highlights slot straight through to it, along with the entity-contact-* properties in the API Reference below. aegov-footer-highlights can also be used entirely on its own wherever just the hero row is needed.

The highlights slot's start-side card is completely open — put anything you want in it. The component applies no chrome to this card at all: no background, no shadow, no border, no radius, no padding. Your own wrapper div supplies all of it, so the card can be a newsletter signup (as in the example below), a promotional banner, a set of quick links, or anything else worth surfacing above the fold of the footer.

The government Tawasul contact block is mandatory and fixed. It renders inside the embedded highlights card on every UAE government site and is identical everywhere — there is no property or slot to remove, hide, or restyle any part of it, including the logo. The entity's own contact number and email, if it has them, go in the same card via entity-contact-number / entity-email (and their -label overrides) — never by editing the fixed card itself.

Below the highlights row, a responsive grid holds the brand slot (logo, description, social links) alongside the author-written link columns. Set app-store-href and/or google-play-href to add a "Download our app" badge block right below the brand slot content, in the same first column — provide either alone, or both; nothing renders unless at least one is set.

The bottom bar carries copyright and legal slots for the "© … All rights reserved" line and legal links (privacy policy, accessibility statement, and similar). The copyright line updates every year — author it yourself; the component does not generate or track the year for you.

Neither aegov-footer nor aegov-footer-highlights emits any custom events.

Authoring link columns

Each footer link column is plain HTML — a title element (any tag; h2–h6 recommended) as the group's first child, followed by the rest of the column's content:

<div class="aegov-footer__group">
  <h2>The Ministry</h2>
  <ul role="list">
    <li><a href="/about">About the ministry</a></li>
    <li><a href="/careers">Careers</a></li>
  </ul>
</div>

No button, no disclosure markup — nothing beyond .aegov-footer__group for you to write. The component owns the mobile/desktop behaviour entirely: below the sm breakpoint (640px), with the default nav-variant="collapsible", it synthesizes a button around the title's own content and moves everything after it into an auto-managed panel the button toggles — the first column starts open, the rest closed. At sm and up — and always with nav-variant="flat" — that button is unwrapped again: the title goes back to being exactly the plain element you authored, with no button anywhere in the DOM in that state at all — not hidden, not disabled, never created.

This is deliberate, not incidental: a disclosure control that's merely hidden or neutralised (for example, role="presentation" on a still-focusable button) is not reliably suppressed by assistive technology — WAI-ARIA's Presentational Roles Conflict Resolution rule requires user agents to fall back to native semantics on anything that remains focusable. Only genuinely not having a button in the DOM guarantees the title reads as a plain heading everywhere it isn't interactive.

Add role="list" to your list yourself — the component's CSS removes list markers for layout, which strips the implicit list semantics in some browsers unless role="list" is present. This lives in your own slotted markup, so the component cannot add it for you.

The full example below shows several link columns together, alongside every other slot and property.

Nav variant

The nav-variant property controls how link columns behave below the sm breakpoint (640px) — independent of the grid's own 2-to-4-column switch at lg. Both values render identically at sm and above, and neither requires any extra authored markup.

  • collapsible (default) — below sm, each column toggles independently via the synthesized button described above; the first column starts open, the rest closed.
  • flat — columns are always expanded, at every screen size. No button is ever synthesized, so there is nothing to toggle.

The full example below uses the default collapsible value — resize your viewport below 640px to see the toggle behaviour. Set nav-variant="flat" on the same markup for the always-expanded alternative.

The brown newsletter card in the example below is just one illustration of the open highlights slot, not a fixed pattern. The component applies no chrome to it at all — no background, no shadow, no border, no radius, no padding — so replace it with whatever your entity actually wants to promote there. The card beside it, with the Tawasul logo and "Comments or complaints" details, is the only fixed part of the highlights row.

Complete example

Every property and every slot on aegov-footer — including the ones forwarded to the embedded aegov-footer-highlights and the app-store-href/google-play-href badge pair — used together at once: a newsletter signup in the highlights row, a branded logo and social links, download-app badges, three link columns, and a bottom bar with a last-updated link and legal links.

Newsletter

Stay in touch

The latest updates, roughly once a month.

Subscribe
Example Federal Entity logo

An entity of the UAE Federal Government, delivering services across the country.

© 2026. Example Federal Entity. All rights reserved. Last updated on 24/04/2026 at 15:45

<aegov-footer
  nav-variant="collapsible"
  entity-contact-number="800 8877"
  entity-contact-number-label="Toll free, 24 hours"
  entity-email="info@example.gov.ae"
  entity-email-label="General enquiries"
  entity-contact-href="/contact"
  app-store-href="https://apps.apple.com/example"
  google-play-href="https://play.google.com/example"
>
  <div slot="highlights">
    <div class="relative overflow-hidden rounded-xl shadow-lg border border-primary-700 dark:border-primary-800 bg-primary-900 dark:bg-primary-950 flex items-center p-6 sm:p-10">
      <div class="relative max-w-sm w-full">
        <p class="text-xs font-semibold uppercase tracking-wide text-secondary-300">Newsletter</p>
        <h2 class="text-xl font-bold text-whitely-50 mt-2">Stay in touch</h2>
        <p class="text-sm text-primary-200 mt-2">The latest updates, roughly once a month.</p>
        <form class="mt-5">
          <label class="block text-xs text-primary-200 mb-1.5" for="footer-email">Email address</label>
          <div class="flex gap-2">
            <aegov-input id="footer-email" type="email" placeholder="name@example.ae" class="flex-1 min-w-0"></aegov-input>
            <aegov-button appearance="solid" variant="neutral-min" is-full="true">Subscribe</aegov-button>
          </div>
        </form>
      </div>
    </div>
  </div>

  <div slot="brand">
    <img src="https://designsystem.gov.ae/assets/site-logo/AEGov-DesignSystem-Logo-Color.svg" alt="Example Federal Entity logo" class="h-14 w-auto" />
    <p class="text-sm text-aeblack-600 mt-4">An entity of the UAE Federal Government, delivering services across the country.</p>
    <div class="flex gap-3 mt-5">
      <a href="https://facebook.com/example" aria-label="Facebook" class="inline-flex items-center justify-center text-aeblack-700 hover:text-primary-800">
        <svg aria-hidden="true" width="20" height="20" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"><rect width="256" height="256" fill="none"/><circle cx="128" cy="128" r="96" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/><path d="M168,88H152a24,24,0,0,0-24,24V224" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/><line x1="96" y1="144" x2="160" y2="144" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/></svg>
      </a>
      <a href="https://linkedin.com/company/example" aria-label="LinkedIn" class="inline-flex items-center justify-center text-aeblack-700 hover:text-primary-800">
        <svg aria-hidden="true" width="20" height="20" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"><rect width="256" height="256" fill="none"/><rect x="32" y="32" width="192" height="192" rx="8" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/><line x1="120" y1="112" x2="120" y2="176" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/><line x1="88" y1="112" x2="88" y2="176" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/><path d="M120,140a28,28,0,0,1,56,0v36" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="16"/><circle cx="88" cy="84" r="12" fill="currentColor"/></svg>
      </a>
    </div>
  </div>

  <div class="aegov-footer__group">
    <h2>About</h2>
    <ul role="list">
      <li><a href="/about">About the entity</a></li>
      <li><a href="/initiatives">Our initiatives</a></li>
      <li><a href="/careers">Careers</a></li>
    </ul>
  </div>
  <div class="aegov-footer__group">
    <h2>Media and data</h2>
    <ul role="list">
      <li><a href="/news">News</a></li>
      <li><a href="/open-data">Open data</a></li>
      <li><a href="/publications">Publications</a></li>
    </ul>
  </div>
  <div class="aegov-footer__group">
    <h2>Support</h2>
    <ul role="list">
      <li><a href="/faq">Frequently asked questions</a></li>
      <li><a href="/accessibility">Help and accessibility</a></li>
      <li><a href="/sitemap">Sitemap</a></li>
    </ul>
  </div>

  <p slot="copyright">
    © 2026. Example Federal Entity. All rights reserved.
    <a href="/updates">Last updated on 24/04/2026 at 15:45</a>
  </p>
  <div slot="legal">
    <a href="/privacy">Privacy policy</a>
    <a href="/accessibility-statement">Accessibility statement</a>
    <a href="/open-data-policy">Open data policy</a>
  </div>
</aegov-footer>

RTL support

The footer detects right-to-left mode from the closest dir ancestor or the html element — no extra property needed. The "Footer navigation" landmark label, the embedded highlights card's "Comments or complaints"/"Contact us"/"Toll free"/"Email" labels, and the "Download our app" block's title and store-name badges all switch to Arabic automatically. Layout mirrors through CSS grid and logical properties, so the highlights cards, the brand column, and disclosure chevrons all flip sides correctly with no extra markup.

<div dir="rtl">
  <aegov-footer entity-contact-number="800 8877" entity-email="info@example.gov.ae">
    <div class="aegov-footer__group">
      <h2>الوزارة</h2>
      <ul role="list"><li><a href="/about">عن الوزارة</a></li></ul>
    </div>
    <p slot="copyright">© 2026. جميع الحقوق محفوظة.</p>
  </aegov-footer>
</div>

Usage

Here is the recommended usage of a footer on any website or application. These are recommended usage guides, however the developer must use the best practices of web and application development to accurately use this component.

Use exactly one footer per page, at the very end of the document
It renders the page's only contentinfo landmark — place it after all other content, not nested inside main or any other landmark.

Give every icon-only social link in the brand slot an accessible name
This markup is entirely author-owned, so the component cannot add a label for you — use aria-label, visible text, or an alt'd image. A dev-mode console warning flags any link that's missing one.

Do not try to hide, restyle, or remove the fixed Tawasul "Comments or complaints" block
It is identical on every UAE government site by design — there is no prop or slot to change any part of it, including the logo. Only the entity's own contact number and email are site-specific.

Do not add your own button or disclosure markup around a link column's title
The component synthesizes and removes a toggle button automatically based on breakpoint and nav-variant. Author only a plain title element followed by the column's content — adding your own control creates a duplicate, conflicting one.

API reference

The following are the properties and references of a footer

aegov-footer properties

AttributeDescriptionTypeDefault

nav-variant

Controls how footer link columns behave below the sm breakpoint (640px) — independent of the grid's own 2-to-4-column switch at lg. collapsible toggles each column below sm; flat is always expanded.

collapsible | flat

collapsible

entity-contact-number

Forwarded to the embedded aegov-footer-highlights. The entity's own contact number, shown in the fixed highlights card.

string

undefined

entity-contact-number-label

Forwarded to the embedded aegov-footer-highlights. Overrides the label before the contact number (defaults to the bilingual "Toll free" text).

string

undefined

entity-email

Forwarded to the embedded aegov-footer-highlights. The entity's own contact email, shown below the contact number.

string

undefined

entity-email-label

Forwarded to the embedded aegov-footer-highlights. Overrides the label before the email (defaults to "Email").

string

undefined

entity-contact-href

Forwarded to the embedded aegov-footer-highlights. Destination for the fixed "Contact us" link. Nothing renders unless this is set.

string

undefined

app-store-href

Link to the entity's app on Apple's App Store. Renders a "Download our app" badge block in the brand column when set (alone or with google-play-href).

string

undefined

google-play-href

Link to the entity's app on Google Play, shown alongside app-store-href in the same badge block.

string

undefined

aegov-footer slots

SlotDescription

highlights

Forwarded to the embedded aegov-footer-highlights's own default slot (its start-side card content).

brand

Logo, description, and social links for the first item in the brand-and-nav-columns grid. When app-store-href/google-play-href are set, the "Download our app" badge block renders below this content, in the same column.

(default)

Footer link columns. Each column: a plain .aegov-footer__group wrapper div with a title element as its first child, followed by the rest of the column's content.

copyright

Copyright / last-updated text, shown at the start of the bottom bar.

legal

Legal links, shown at the end of the bottom bar. One wrapper div with plain a tags inside, no li needed — the component wraps each link in a real list itself.

aegov-footer-highlights properties (embedded sub-component)

AttributeDescriptionTypeDefault

entity-contact-number

The entity's own contact number, shown in the fixed card next to "Toll free" (or your override label). Nothing renders unless it's provided.

string

undefined

entity-contact-number-label

Overrides the label before entity-contact-number (defaults to the bilingual "Toll free" text).

string

undefined

entity-email

The entity's own contact email, shown below the contact number. Nothing renders unless it's provided.

string

undefined

entity-email-label

Overrides the label before entity-email (defaults to "Email").

string

undefined

entity-contact-href

Destination for the fixed "Contact us" link at the end of the card. The link text itself is fixed — only the destination is site-specific — so nothing renders unless this is provided.

string

undefined

aegov-footer-highlights slots (embedded sub-component)

SlotDescription

(default)

The start-side card's content, fully author-owned — wrap it in your own div carrying whatever background, shadow, border, radius, and padding classes you want (a newsletter form, app-download links, or anything else you want to promote); nothing is applied for you. The end-side card — the fixed "Comments or complaints" Tawasul block — has no prop or slot to change any part of it, including the logo.

Pass-through attributes

Attribute groupNotes

aria-*, data-*

Not specially forwarded on aegov-footer itself — apply directly to it, since it renders in the light DOM (no shadow root) and the host element is what assistive technology and selectors see.

class, style, id

Applied to the host element as usual.

Notes

The following notes are applicable of this component.

Built-in accessibility

  • Renders a single top-level footer element, giving the page its contentinfo landmark.
  • All link columns are wrapped in one navigation region labelled "Footer navigation" (bilingual), rather than a separate navigation landmark per column, avoiding landmark proliferation.
  • Column titles are plain, untouched elements whenever they aren't genuinely toggleable — no button exists in the DOM in that state at all, so assistive technology reads exactly what was authored (for example "heading level 2, The Ministry"), never a disclosure control's own role.
  • Below the sm breakpoint, nav-variant="collapsible" synthesizes a real button with live aria-expanded/aria-controls, toggling the panel's hidden attribute — fully keyboard-operable via native button activation (Enter/Space), with no custom keydown handling.
  • A dev-mode console warning flags a brand-slot link with no accessible name, since that markup is author-owned.
  • The "Download our app" badges are plain links with translated, human-readable text ("App Store", "Google Play") — nothing icon-only or unlabeled.
  • The dismiss/toggle focus ring on every interactive element matches aegov-button's own focus-visible treatment.

Developer responsibilities

  • Place aegov-footer at the end of the document, not nested inside main or another landmark — and use exactly one per page.
  • Author each link column as a plain title element (any tag) followed by its content — no extra markup needed for either nav-variant value.
  • Add role="list" to each column's list, since the component removes list markers via CSS, which strips implicit list semantics in some browsers.
  • Give every icon-only brand-slot link an accessible name (aria-label, or a visually-hidden sr-only span).
  • Do not attempt to hide, restyle, or remove the fixed Tawasul contact block — there is no supported way to do so, and it must stay identical across UAE government sites.

Keyboard support

Key Action
Tab Move focus to the next focusable element (a link, or a synthesized trigger below sm).
Enter, Space Toggle the focused column's panel, when nav-variant="collapsible" and below sm.