Agriculture Design System
Elevating the accessibility of a government design system through strategic information architecture and comprehensive documentation.

Elevating the accessibility of a government design system through strategic information architecture and comprehensive documentation.
The Agriculture Design System (AgDS) team operates within the Australian Government's Department of Agriculture, Fisheries and Forestry (DAFF). We ensure that digital products and services created by teams within DAFF can be used by everyone, regardless of ability or situation.
How do you make accessibility guidance actionable for designers and developers using a design system? They often aren't going into the design system to look for general accessibility information. They are often going in to find out how to correctly implement a component.
The challenge was determining how much information to provide and at what point in their workflow, while ensuring comprehensive coverage without overwhelming users.
As a designer on a large-scale government design system, I:
With a Professional Certificate in Web Accessibility (PCWA) and previous accessibility experience, I also:
Review existing accessibility information across the design system to identify gaps and opportunities.
Define the information architecture approach, including content placement rules and structure.
Applied user-focused writing approach that adheres to the Australian Government Style Manual to create accessibility documentation using the framework established at the information architecture phase.
Collaborate with another accessibility specialist to ensure techincal accuracy and conformance. Follow with stakeholder review working with design system leadership to align strategically with system goals.
Launch comprehensive accessibility documentation across the design system. This includes the foundational accessibility section, as well as contextual component level accessibility guidance.
The discoverability problem was solved by creating a clear structural hierarchy that distinguished between two distinct types of accessibility information:
Component-level guidance within accessibility tabs: Information about accessibility considerations specific to individual components, actionable during design or development. These cover aspects that, if implemented incorrectly, would render components inaccessible.
Foundational knowledge within a global accessibility section: Essential accessibility principles and broader topics that apply across multiple components or situations.
For component accessibility tabs, I organised content around specific accessibility topics prioritising immediate implementation needs. Each topic follows a consistent three-part structure:
Requirements: Direct, actionable guidance on what users must do to implement accessibly.
Benefits: Explanation of why this consideration matters and how it impacts users with disabilities.
WCAG references: Direct links to relevant Web Content Accessibility Guidelines for compliance context.
Related guidance: Direct links to other guidelines, such as the ARIA Authoring Practices Guide.
For the foundational section, I created comprehensive content using a four-part structure that builds understanding whilst maintaining consistency:
Topic introduction within AgDS context: Explains how AgDS specifically addresses each area, providing confidence and context about the system's approach.
Requirements, benefits, WCAG references, related guidance: Using the same four-part structure as component tabs creates consistency across all accessibility documentation, reducing cognitive load and helping users quickly locate information.
This approach ensures users encounter relevant guidance in context whilst having access to comprehensive foundational knowledge when needed.
Created a sustainable model for accessibility documentation that scales as new components are added to the system. This provides clear guidance for where new accessibility content should live and enables teams to find relevant information in context of their work.
Delivered 44 pages of accessibility guidance covering existing design system components, foundational accessibility topics, and conformance considerations.
Presented the accessibility documentation to the department and at design guild, generating significant engagement, especially from both designers and developers. Feedback highlighted that the information was "practical, concise and actionable," validating the content strategy approach. Teams began actively reading and referencing the documentation, with increased accessibility-related inquiries demonstrating real usage and organisational need.
Established the design system as a reliable source of accessibility guidance, enabling teams across the organisation to create more inclusive digital experiences whilst maintaining consistency with established patterns and principles.
The Agriculture Design System accessibility documentation now serves as a comprehensive resource that empowers teams across DAFF to build inclusive digital experiences while maintaining design consistency and regulatory compliance.
Empowering marketing managers to access critical pharmaceutical performance data
View case study