Current

In content implemented using markup languages, the conventional name of conventional form fields, conventional buttons or controls, or links can be programmatically determined.

Proposed

In content implemented using markup languages, the qualified purpose of conventional form fields[1], conventional buttons, controls, or links[2] can be programmatically determined.

Conventional buttons, controls, or links

Understanding

In the broadest of terms, the goal is to advise, programmatically, the intent of acting upon a trigger, whether that is a link, a button, or some other custom control. By splitting the method from the intent, we can narrow the number of terms under review. Taking the original list of proposed terms and definitions, I also attempted to group the triggers based upon categories: Navigation Actions, UI / Page Actions, Editing Actions, Email Actions, and Shopping Actions, as well as a list of common web pages.