Corporate governance | Our Business | Diageo

Buchanan’s | Discover Buchanan's whisky | Our brands | Diageo

How We Build Brands | Our Business | Diageo

Board Of Directors | Representatives | Our Business | Diageo

Crown Royal whisky | Discover Crown Royal | Diageo

History of Diageo | Our Business | Diageo

Europe | Where we operate | Diageo

Baileys | Brand Profile | Diageo

CÎROC | Brand Profile | Diageo

The Archive | History | Our Business | Diageo

Forms should always contain a submit button, otherwise some people using
accessible technologies may not be able to submit the form.

Submit buttons are `<input>` elements with a type attribute of `submit` or
`image`, or `<button>` elements with type `submit`.

## Rationale 

Many users expect to be able to press enter in a form to submit it. However,
this is not always possible.

Users of some assistive technologies may (depending on the technology) only
be able to press a button to submit the form. In the absence of a submit
button, the user may not be able to submit the form.

In addition, the absence of a submit button suggests that the form may 
provide an automatic 'change of context', i.e. major change to the user 
interface without the user choosing to do so. This can be highly disorientating
to some users.

## Methodology

* All `<form>` elements on the page are tested separately.
* Check whether the <form> contains any of the following elements, and that the elements are visible
  when the page first loads:
  * `<input>`
  * `<textarea>`
  * `<checkbox>`
  * `<select>`
  * `<button>`
* If the form contains any of the above elements, then it is considered to
  need a submit button. If a submit button is missing, then a failure is reported.

### Field visibility check

The check for field visibility (above) is designed to ignore forms which perform functions not normally
associated with user interaction, such as tracking code, or ASPX forms which wrap every page 
but which don't contain any interactive elements. These are common potential false positives.

A trade-off here is that some forms may be invisible when a page loads, and later revealed to
a user following some interaction. If these are missing a submit button, Silktide will not detect them.
In practice, this false negative is far less likely than the false positive this prevents. 

## Further reading

* [WCAG 3.2.2 - On Input](https://www.w3.org/WAI/WCAG22/Understanding/on-input.html)
* [Technique H32](https://www.w3.org/TR/WCAG20-TECHS/H32.html)

form-submit-required

October 2025

September 2025

Diageo

	Title / URL	Issues
	Corporate governance \| Our Business \| Diageowww.diageo.com/en/our-business/corporate-governance	1
	Buchanan’s \| Discover Buchanan's whisky \| Our brands \| Diageowww.diageo.com/en/our-brands/brand-explorer/buchanans	1
	How We Build Brands \| Our Business \| Diageowww.diageo.com/en/our-business/building-world-class-brands	1
	Board Of Directors \| Representatives \| Our Business \| Diageowww.diageo.com/en/our-business/board-of-directors	1
	Crown Royal whisky \| Discover Crown Royal \| Diageowww.diageo.com/en/our-brands/brand-explorer/crown-royal	1
	History of Diageo \| Our Business \| Diageowww.diageo.com/en/our-business/our-history	1
	Europe \| Where we operate \| Diageowww.diageo.com/en/our-business/where-we-operate/europe	1
	Baileys \| Brand Profile \| Diageowww.diageo.com/en/our-brands/brand-explorer/baileys	1
	CÎROC \| Brand Profile \| Diageowww.diageo.com/en/our-brands/brand-explorer/ciroc	1
	The Archive \| History \| Our Business \| Diageowww.diageo.com/en/our-business/our-history/the-archive	1

Add a submit button to all forms

Diageo

Where this issue has occurred