Footer

Design System - Footer component

The Footer component provides navigational actions or supplementary content at the bottom of pages. It serves as a closing control panel for tasks or flows, ensuring alignment with accessibility, responsiveness, and contextual clarity across applications.

Component React

// Sample code

<Footer
  actionFields={[
    <Button icon="ArrowBack" label="Back" onClick={()=>{}} type="button" variation="secondary"/>,
    <Button icon="ArrowForward" isSuffix label="Next" onClick={()=>{}} type="button"/>
  ]}
  className=""
  maxActionFieldsAllowed={5}
  sortActionFields
  style={{}}
/>

Component Flutter

Component Design

Anatomy

---

Variants

---

	Default A straightforward footer with clearly defined action buttons like "Back" and "Next," used in linear flows or form-based screens.
	Flex A more dynamic variant that allows flexible content like dropdown menus, dynamic button alignment, and custom text

Properties

Button Supports multiple button styles, including: Primary (e.g., “Next”) Secondary (e.g., “Back”) Tertiary (optional actions) Dropdown / Dropup menus (used to group multiple actions)
Extra Content Allows inclusion of helper or legal text beneath or between buttons, offering context or attribution.

Property Configuration Table

Each design component offers a range of configurable options. These options are intentionally platform-agnostic, allowing implementations to adapt and tailor them to align with the specific requirements of the chosen framework.

React

Property	Value	Default
className	text	-
style	text	-
actionFields	yes/no	no
maxActionFieldsAllowed	yes/no	no
sortActionFields	number	-
setactionFieldsToRight	yes/no	-
setactionFieldsToLeft	yes/no	no
children	yes/no	no

Flutter

Usage Guide

---

	Button Labeling Clearly label all buttons with actionable language like “Next,” “Submit,” or “Save”. Avoid using vague or unclear labels like “Click” or “Okay” that provide no guidance on the action.

Change log

---

Date	Number	Notes
Dec 15, 2024	v-0.0.2	This component is added to the website. This component is now individually versioned.

Design Checklist

---

	All interactive states - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
	Accessible use of colours - Colour is not used as the only visual means of conveying information (WCAG 2.1 1.4.1)
	Accessible contrast for text - Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).
	Accessible contrast for UI components - Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).
	Keyboard interactions - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
	Screen reader accessible - All content, including headings, labels, and descriptions, is meaningful, concise, contextual and accessible by screen readers.
	Responsive for all breakpoints - Responsiveness for 3 breakpoints - Mobile, Tablet and Desktop
	Usage guidelines - Includes a list of dos and don'ts that highlight best practices and common mistakes.
	Content guidelines - Content standards and usage guidelines for writing and formatting in-product content for the component.
	Defined variants and properties - Includes relevant variants and properties (style, size, orientation, optional iconography, decorative elements, selection states, error states, etc.)
	Defined behaviours - Guidelines for keyboard navigation and focus, layout management (including wrapping, truncation, and overflow), animations, and user interactions.
	Design Kit - Access to the design file for the component in Figma, multiple options, states, colour themes, and platform scales.