Menu Card

Design System - Menu Card component

The Menu Card component serves as a navigational tile, guiding users through various modules, processes, or tasks. Built with accessibility, responsiveness, and clarity in mind, this molecule uses strong visual hierarchy with clear icons, descriptions, and optional labels. It supports interaction cues such as hover states and is optimised for multiple device sizes.

Component React

// Sample code

<MenuCard
  description="Use this checklist to supervise the team formation for Registration & Distribution"
  icon="Article"
  menuName="Menu"
  onClick={()=>{}}
  styles={{}}
/>

Component Flutter

Component Design

Anatomy

Variants

---

	Menu 1 A basic card with an icon and a short descriptive text for task or module access.
	Menu 2 Extends Menu 1 by including a Label next to the icon to add context or categorisation.

Properties

Icon - Menu 1 & 2 Clearly conveys the function or context of the menu item.
Description - Menu 1 & 2 A short line of text to inform the user about the menu’s purpose, to indicate that the button is not active.
Label - Menu 2 Appears above the description and helps name or categorise grouped items.

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
icon	text	-
menuName	text	-
description	yes/no	no
className	yes/no	no
styles	number	-
onClick	yes/no	-

Flutter

Usage Guide

---

	Maintain clarity Use concise, descriptive labels and explanations for each card. Overload the card with long sentences or technical jargon..

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.