ASP Digital Design System

Definition of done

The Definition of Done (DoD) is a set of criteria that must be met for a user story or task to be considered complete and ready for deployment. It ensures that the team has met the required quality standards and that the product is in a releasable state. This document outlines the Definition of Done, including cross-browser testing and accessibility requirements to WCAG 2.1 AA standard.

General Criteria:

  1. All user stories, tasks, and acceptance criteria are implemented.
  2. Code is written following the team’s coding standards and best practices. 🚧 WIP (to be defined) 🚧
  3. Code has been reviewed by at least one other team member and necessary improvements have been made.
  4. All automated tests pass successfully, including unit tests, integration tests, and any other applicable tests.
  5. All manual tests have been executed and passed.
  6. Documentation has been updated to reflect any changes made to the system. 🚧 WIP (to be structured) 🚧
  7. All known bugs have been fixed or logged as separate issues in DevOps.

Cross-Browser Testing:

  1. The application has been tested on all supported browsers and versions, including but not limited to Chrome, Firefox, Safari, and Edge. 🚧 WIP (clear list to be defined and browerlistrc file created) 🚧
  2. The core functionality and user experience are consistent across different browsers.
  3. All interactive elements, such as buttons, links, and forms, are working as expected on all supported browsers.
  4. Visual design and layout are consistent across different browsers and devices.
  5. Cross-browser compatibility issues have been identified and resolved, or a suitable fallback solution has been implemented.

Accessibility (WCAG 2.1 AA Standard):

  1. The application complies with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards.
  2. All content and functionality are perceivable to users with disabilities.
  3. Text alternatives are provided for non-text content, including images, videos, and audio.
  4. Keyboard accessibility is ensured, allowing users to navigate and interact with the application using only the keyboard.
  5. Color contrast is sufficient to ensure readability for users with visual impairments.
  6. All forms and input fields have appropriate labels and instructions for screen reader users.
  7. The application is compatible with assistive technologies, such as screen readers and magnifiers.
  8. Focus states are clearly visible to assist users navigating through interactive elements.
  9. ARIA (Accessible Rich Internet Applications) attributes are used appropriately to enhance accessibility.

Deployment:

  1. The code has been successfully merged with the master branch of the application’s repository.
  2. Continuous Integration (CI) pipelines have been triggered and completed without errors.
  3. The application has been deployed to the designated environments, such as staging or production, depending on the release process.
  4. Smoke tests or other post-deployment verification tests have been conducted to ensure the application is running correctly in the target environment.
  5. All necessary configurations and environment-specific settings have been applied.

Review and Approval:

  1. The completed user story or task has been reviewed by the product owner or the designated stakeholders.
  2. The product owner or stakeholders have approved the user story or task as meeting the acceptance criteria and quality standards.

By adhering to this Definition of Done, the team ensures that the product has been thoroughly tested, meets the accessibility requirements, and is ready for deployment.

Published 18 January 2024
Last updated 23 January 2024