Hello, I've taken ownership as a shepherd for the submission status notified rule. the current phrasing likely could be improved to help clarify the scope, timing, location, etc.
Current Text:
"Data entry interfaces notify users of submission status at the time of submission."
Issues:
- Narrow Scope: The term "Data entry interfaces" makes this seem as though it only applies to forms.
- "at the time of submission" implies that the notification would only be able to be "Sent" if it happens, which I don't think is the intention of the rule.
- Unclear Location: There is no indication of where the notification should occur (e.g., email, txt message, etc.)
- Status Type is Ambiguous: There is no indication of the types of status covered. It is unclear if this is limited strictly to "submission statuses" or if it includes success/failure/etc.
Proposed Text:
"Interfaces provide timely contextual notifications of submission progress and submission outcome."
Finally, "Confirmation of Action," is typically used at Microsoft(and potentially outside of Microsoft) to describe a status message(in WCAG 2.2 terms) that follows an action... for example the new ARIA Notification JS API was originally discussed under the name "Confirmation of Action API" (see this blink-dev thread). If you want this supplemental requirement to focus just on indicating the status that it was submitted(without pass/fail) then adoption of a common term like confirmation of action might be helpful.
@hidde for visibility.
Hello, I've taken ownership as a shepherd for the submission status notified rule. the current phrasing likely could be improved to help clarify the scope, timing, location, etc.
Current Text:
"Data entry interfaces notify users of submission status at the time of submission."
Issues:
Proposed Text:
"Interfaces provide timely contextual notifications of submission progress and submission outcome."
Finally, "Confirmation of Action," is typically used at Microsoft(and potentially outside of Microsoft) to describe a status message(in WCAG 2.2 terms) that follows an action... for example the new ARIA Notification JS API was originally discussed under the name "Confirmation of Action API" (see this blink-dev thread). If you want this supplemental requirement to focus just on indicating the status that it was submitted(without pass/fail) then adoption of a common term like confirmation of action might be helpful.
@hidde for visibility.