From efa2a68f935b3ae9555e80c0dd5ce4626a7ca771 Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 14:42:56 +0200 Subject: [PATCH 1/7] Update error-identification.html --- understanding/20/error-identification.html | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index 538effccc4..cb2a80cc13 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -47,7 +47,25 @@

Intent of Error Identification

  • the user enters alphabetic characters or parentheses into their phone number field that only accepts numbers;
  • the user enters a bid that is below the previous bid or the minimum bid increment.
    • - +

    Note on using HTML form validation

    +

    With HTML form validation, the use of the required attribute on a field has the consequence that + when trying to submit the form with this field empty, the user agent will display a generic text message that a value + in the field is required, and set the focus to the first field missing required input. + It will also scroll the page to this field is in the viewport.

    +

    In most common user agent and screen reader combinations, the screen reader will read the error message + and the programmatic name of the required field. + While this in principle meets the requirements of this Success Criterion, + it should be noted that there are several disadvantages related to this approach:

    +

    If a user enters a value that is too high or too low, and the coding on the page automatically changes that value to fall within the allowed range, the user's error would still From 3903365b9419f94fd5ee810de01c477063dbec2c Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 14:45:17 +0200 Subject: [PATCH 2/7] Update error-identification.html --- understanding/20/error-identification.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index cb2a80cc13..8c807f3492 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -51,7 +51,7 @@

    Note on using HTML form validation

    With HTML form validation, the use of the required attribute on a field has the consequence that when trying to submit the form with this field empty, the user agent will display a generic text message that a value in the field is required, and set the focus to the first field missing required input. - It will also scroll the page to this field is in the viewport.

    + It will generally also scroll the page so that this field and the generated error message will be visible in the viewport.

    In most common user agent and screen reader combinations, the screen reader will read the error message and the programmatic name of the required field. While this in principle meets the requirements of this Success Criterion, From 31d16ee11dd1ce74533302ef243a82fc2ff0712c Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 14:56:32 +0200 Subject: [PATCH 3/7] Update error-identification.html --- understanding/20/error-identification.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index 8c807f3492..62a09195c3 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -58,11 +58,11 @@

    Note on using HTML form validation

    it should be noted that there are several disadvantages related to this approach:

    From 1ba859b145be7f71c067ed6770dfd5f3883b052b Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 14:58:13 +0200 Subject: [PATCH 4/7] Update error-identification.html minor edit --- understanding/20/error-identification.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index 62a09195c3..d8b2da1528 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -60,7 +60,7 @@

    Note on using HTML form validation

  • Depending on the user agent, the message may be non-permanent, or fail to scroll with the page
  • Depending on the user agent, zoomed-in (magnified) content may display the error message unmagnified; the message may may be too small for users to read
    • -
  • HTML validation messages for fields with type=text will be unspecific +
  • HTML validation messages for fields with type="text" will be unspecific and will neglect to provide helpful suggestions where these may be needed
  • If several errors are present, only the first error is exposed. Once the user has provided an input that conforms to the type of field and resubmits the form, From f26f47511bebae96283eacb87359c8fa01666bed Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 15:16:38 +0200 Subject: [PATCH 5/7] Update error-identification.html minor edits --- understanding/20/error-identification.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index d8b2da1528..80e02ac50b 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -47,11 +47,11 @@

    Intent of Error Identification

  • the user enters alphabetic characters or parentheses into their phone number field that only accepts numbers;
  • the user enters a bid that is below the previous bid or the minimum bid increment.
    • -

    Note on using HTML form validation

    -

    With HTML form validation, the use of the required attribute on a field has the consequence that - when trying to submit the form with this field empty, the user agent will display a generic text message that a value +

    Note on using native HTML form validation

    +

    With native HTML form validation, the use of the required attribute on a field has the consequence that + when trying to submit the form with this field empty, the user agent will automatically display a generic text message that a value in the field is required, and set the focus to the first field missing required input. - It will generally also scroll the page so that this field and the generated error message will be visible in the viewport.

    + The user agent will generally also scroll the page so that the field in error and the generated error message will be visible in the viewport.

    In most common user agent and screen reader combinations, the screen reader will read the error message and the programmatic name of the required field. While this in principle meets the requirements of this Success Criterion, From c56388ef8ce97cd97e1e27ba88def5177539fbfa Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 15:17:44 +0200 Subject: [PATCH 6/7] Update error-identification.html minor edit --- understanding/20/error-identification.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index 80e02ac50b..3e18a1ef50 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -49,10 +49,10 @@

    Intent of Error Identification

    Note on using native HTML form validation

    With native HTML form validation, the use of the required attribute on a field has the consequence that - when trying to submit the form with this field empty, the user agent will automatically display a generic text message that a value + when trying to submit the form with this field empty, the user agent will automatically display a generic error message that a value in the field is required, and set the focus to the first field missing required input. The user agent will generally also scroll the page so that the field in error and the generated error message will be visible in the viewport.

    -

    In most common user agent and screen reader combinations, the screen reader will read the error message +

    In most common user agent and screen reader combinations, the screen reader will read the generic error message and the programmatic name of the required field. While this in principle meets the requirements of this Success Criterion, it should be noted that there are several disadvantages related to this approach:

    From 28b66de4e503bd171f8f093849c5dbda4a45937d Mon Sep 17 00:00:00 2001 From: Detlev Fischer Date: Thu, 5 Jun 2025 15:19:46 +0200 Subject: [PATCH 7/7] Update error-identification.html --- understanding/20/error-identification.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html index 3e18a1ef50..754f336ad4 100644 --- a/understanding/20/error-identification.html +++ b/understanding/20/error-identification.html @@ -60,8 +60,7 @@

    Note on using native HTML form validation

  • Depending on the user agent, the message may be non-permanent, or fail to scroll with the page
  • Depending on the user agent, zoomed-in (magnified) content may display the error message unmagnified; the message may may be too small for users to read
    • -
  • HTML validation messages for fields with type="text" will be unspecific - and will neglect to provide helpful suggestions where these may be needed
    • +
  • HTML validation messages for fields with type="text" will be unspecific, i.e. they will not provide helpful suggestions where these may be needed
  • If several errors are present, only the first error is exposed. Once the user has provided an input that conforms to the type of field and resubmits the form, the next error (if present) will be exposed. This means that repeated resubmissions and corrections may be required.