News Releases - Choice Properties

Developments - Choice Properties

Presentations - Choice Properties

Contact - Choice Properties

Choice Properties - Canada's Preeminent REIT

Governance - Choice Properties

Accessibility - Choice Properties

Lots of Play - Choice Properties

Overview - Choice Properties

Choice Customer Connection - Choice Properties

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

September 2025

August 2025

Choice Properties Real Estate Investment Trust

	Title / URL	Issues
	News Releases - Choice Propertieswww.choicereit.ca/news-releases/	3
	Developments - Choice Propertieswww.choicereit.ca/developments/	3
	Presentations - Choice Propertieswww.choicereit.ca/presentations/	2
	Contact - Choice Propertieswww.choicereit.ca/contact/	2
	Choice Properties - Canada's Preeminent REITwww.choicereit.ca/	2
	Governance - Choice Propertieswww.choicereit.ca/governance/	2
	Accessibility - Choice Propertieswww.choicereit.ca/accessibility/	2
	Lots of Play - Choice Propertieswww.choicereit.ca/lots-of-play/	2
	Overview - Choice Propertieswww.choicereit.ca/about-overview/	2
	Choice Customer Connection - Choice Propertieswww.choicereit.ca/c3/	2

Add a submit button to all forms

Choice Properties Real Estate Investment Trust

Where this issue has occurred