Project List

Popeyes Accessibility Rebuild

An accessible, WordPress-managed, fully responsive rebuild of Popeyes’ dot-com and corporate sites

Popeyes.com website pages displayed on desktop, tablet, and phone devices demonstrating responsiveness.

Implementation

  • CMS:

    WordPress

  • Frameworks:

    • Bootstrap
    • jQuery

  • Languages:

    • PHP
    • JavaScript
    • Less/CSS
    • HTML

  • WCAG 2.0:

    AA

  • APIs:

    • Brandify Locations
    • YouTube

  • Template Engine:

    Twig

  • Task Manager:

    Grunt

  • Design:

    Responsive

  • Source Control:

    GIT

  • Methodology:

    Agile

About the Project

When I was presented the project, the Popeyes.com website had already been in existence for a few years and had been previously built and maintained by another agency. The immediate problems facing the client were:

  • The challenges of navigating the website as an accessibility user.
  • Two separately maintained sites: a mobile site that only worked on phones, and a fixed-width desktop site with little consideration for tablet users.
  • A static site being hosted in WordPress with none of the content actually being managed by the CMS.
  • Several third-party content providers hosting their own versions of the wrapper with no control over wrapper updates.

The task: Resolve all the challenges, relaunch the website, and perform ongoing maintenance.

The Solution

Most of this project was straight forward. With the fear of impending litigation, I formed the business plan for the minimum viable product required if the legal team ordered the site to be relaunched mid-stream, and then defined biweekly sprints through project completion.

  • The website was rebuilt from the ground up to be WCAG 2.0 AA compliant.
  • I designed and developed a fully responsive single site experience to replace the device-specific sites.
  • While it wasn’t in the budget to make the content completely manageable by the CMS, significant improvements were made so that WordPress was being used more properly, and a majority of the content could be maintained by editors rather than developers. In addition, biweekly menu updates were set up to be scheduled processes rather than manual midnight launches.
  • Moustache-style templates served through the WordPress system were provided to all third-parties in order to maintain a single unified site wrapper.