Merge pull request #926 from WestpacGEL/content-compact-ally

Content compact ally
WestpacGEL · Nov 6, 2024 · f3d006d · f3d006d
2 parents 67d479a + cecbb0b
commit f3d006d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 5 deletions.
diff --git a/.../content/design-system/components/compacta/accessibility/accessibility-notes/content.mdoc b/.../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.
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
@@ -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.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -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.