From 2cb5811c413bd1f4cd40f828976cdb40d95cd9e8 Mon Sep 17 00:00:00 2001 From: KateMacdonald Date: Wed, 6 Nov 2024 16:41:27 +1100 Subject: [PATCH 1/2] Update src/content/design-system/components/compacta --- .../components/compacta/design/user-experience/content.mdoc | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/apps/site/src/content/design-system/components/compacta/design/user-experience/content.mdoc b/apps/site/src/content/design-system/components/compacta/design/user-experience/content.mdoc index 195274ae2..226a81452 100644 --- a/apps/site/src/content/design-system/components/compacta/design/user-experience/content.mdoc +++ b/apps/site/src/content/design-system/components/compacta/design/user-experience/content.mdoc @@ -1,8 +1,6 @@ The Compacta was designed to meet the need of capturing multiple instances of detailed information without overwhelming users, particularly on mobile devices. An example use case may be multiple questions about a customers’ assets. -It is always editable, with the drawer state an easy and familiar show/hide interaction. The remove button is located at the top of an open Compacta for consistency, recall, and to keep all functions in one place. - -The numbering of each Compacta is an accessibility consideration for low vision/zoom and screen reader users to help navigate and identify groupings of content. +The drawer has an easy and familiar show/hide interaction. The 'Add another' and 'Remove' buttons are left-aligned and positioned at the bottom of an open Compacta. This placement, along with the numbering of each Compacta are both accessibility considerations for users who rely on zoom functionality, ensuring they can easily locate these controls without needing to search across the screen. ### States and behaviours @@ -29,5 +27,3 @@ An example may be: ### Pre-populated content Pre-populating fields with content brings complexity for data management, technology, data quality, risk and compliance, and users’ cognitive load. However, if done well with good quality data it can expedite form progress. - -If pre-populating Compactas, use an alert above the first instance to highlight the need for the user to open and review their information as all pre-populated Compactas should be closed by default. By having all pre-populated Compactas open for review would be potentially overwhelming. From cecbb0b779affdf697fde355f92e5671f6bfd11b Mon Sep 17 00:00:00 2001 From: KateMacdonald Date: Wed, 6 Nov 2024 16:52:16 +1100 Subject: [PATCH 2/2] Update src/content/design-system/components/compacta --- .../compacta/accessibility/accessibility-notes/content.mdoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/apps/site/src/content/design-system/components/compacta/accessibility/accessibility-notes/content.mdoc b/apps/site/src/content/design-system/components/compacta/accessibility/accessibility-notes/content.mdoc index 063054e61..894f1fa11 100644 --- a/apps/site/src/content/design-system/components/compacta/accessibility/accessibility-notes/content.mdoc +++ b/apps/site/src/content/design-system/components/compacta/accessibility/accessibility-notes/content.mdoc @@ -5,3 +5,5 @@ All components comply with WCAG 2.1 AA guidelines and Success Criteria. These fa In order to assist screen reader users in determine which ‘compacta’ they are viewing an associated number is required. This is kept at the UI level for those who may use a combination of magnifier and screen reader. Compactas are accessible components and must have numerical signifiers to aid screen reader users navigate and contextualise as well as those who use zoom tools or a combination of both. + +The left-aligned placement of the 'Add another' and 'Remove' buttons is also an accessibility consideration for users who rely on zoom functionality, ensuring they can easily locate these controls without needing to search across the screen.