The team was tasked with using the CMS component library to create engaging experiences like surveys and forms. However, the CMS’s limitations made it challenging to build these features in a way that would be intuitive and user-friendly.
Since we were working with a new CMS, I initiated training sessions to bring the team up to speed, ensuring they understood its capabilities and limitations. This preparation allowed us to design engaging user experiences within the system’s constraints.
The project was recently launched, and there is currently no performance data available yet. The website is live.
As the Sr. UX Architect, I led the UX design, overseeing a Jr. UX Designer while collaborating with copywriters, product designers, and dev team.
In the discovery phase, I conducted interviews with key stakeholders to gain a deep understanding of their goals and expectations for the responsive design project.
In the Define stage, I facilitated a co-op session with subject matter experts to collaboratively outline the content and define the website’s information architecture.
Wireframes for both mobile and desktop were created to map out navigation and functionality, leveraging the CMS component library while working within its limitations to ensure a consistent design across all devices. The focus was on designing interactive experiences, such as the sign-up form and survey.
With a focus on user engagement, the wireframes include a detailed example of the two-step sign-up form, showcasing all states: blank, filled, error, success, and opt-out screens.
Due to the limitations of the CMS platform, the survey experience was integrated into a chatbot modal, making it accessible from any page on the website. Wireframes were created for both mobile and desktop, displaying the functionality across different devices.
To ensure the website was accessible to all users, I conducted a thorough accessibility audit of the layout, focusing on compliance with WCAG 2.2 AA standards.
The accessibility audit focused on ensuring the website adhered to WCAG 2.2 AA standards, identifying and addressing key accessibility issues within the layout. The following areas were prioritized:
Typically, a second audit would be performed on the live website to address backend accessibility issues. However, since we were working within a CMS platform, a backend audit was considered unnecessary, as the platform itself is designed to meet accessibility standards.
In the Deliver stage, the focus shifts to preparing the layout, style guide, and functional specifications document for development. The final product was fully aligned with the CMS platform requirements, built using the component library, and verified for accessibility compliance.
Here are some key takeaways from the project: