Progressive enhancement confusion

[rkdefra]

There seems to be some confusion around the term "progressive enhancement", which could lead to unnecessarily constraining technology choices. The kind of "zero enhancement" strategy described below is very different, and far more restrictive.
The goal of progressive enhancement is not to constrain the use of web technologies, merely to ensure the best possible behaviour across client scenarios.
The wider Gov.UK standards better describe approaches to progressive enhancement, and do not prohibit the use of javascript based technologies for frontend UIs.

software-development-standards/docs/standards/javascript_standards.md

Lines 15 to 17 in 18ffd4d

	- Frameworks such as React, Angular, Vue etc go against [progressive enhancement](https://www.gov.uk/service-manual/technology/using-progressive-enhancement)
	- Even frameworks that provide server-side rendering encourage and enable accidental use of client-side approaches, which violate the progressive enhancement principle
	- The [GOV.UK Design System](https://design-system.service.gov.uk/) already provides a set of accessible components that support progressive enhancement

There also seems to be no distinction between standards for public facing content and systems designed exclusively for the use of civil servants (or other internal users).

[steve-dickinson]

"The goal of progressive enhancement is not to constrain the use of web technologies, merely to ensure the best possible behaviour across client scenarios."

Although I agree with this statement, the use of heavy frameworks and libraries, such as React, Angular, or Vue, can lead to unnecessary complexity. While these frameworks can enable feature rich interactivity, they often introduce a larger footprint, which can be counterproductive when trying to ensure a lightweight and maintainable service. Overuse of such technologies can also make services harder to maintain over time, especially if different teams or developers are working with different technologies across the estate.

We should be aiming for consistency across all digital services which are built. When services are developed using varied frameworks, it can create a maintenance overhead due to the different skill sets required for each framework. This leads to more complexity and technical debt, which can slow down development and increase the likelihood of issues/bugs.

When it comes to user experience, there should be no distinction between external and internal users. Every user, whether they are a member of the public or a civil servant, deserves the same level of quality and accessibility. We need to make sure that all services, regardless of their intended audience, follow the same high standards of usability and accessibility.