NVDA does not read error messages referenced with aria-errormessage and aria-invalid #8318

Wildebrew · 2018-05-21T19:27:11Z

Steps to reproduce:

In any browser (Firefox/Chrome):

Head on over to my aria-errormessage code pen
Enter a number that is 12 or less and click the "Test it" button.
(optionally) you can move focus away from and back to the input field.

In the code aria-invalid gets set to true on the input and the error message is displayed (it is already connected using aria-errormessage).

Expected behavior:

When aria-invalid is set to true on a form field the screen reader should read any error message id referenced from the input field using aria-errormessage.

NVDA would read the error message after the label and value of the form field (similar to how it would be if it were referenced with aria-describedby), possibly adding a word like "error message" or "error".

Actual behavior:

NVDA does not read the error message when the invalid input is focused.

System configuration:

NVDA version: 2018.1
(with IE11, Chrome 65 and Firefox 52-ESR), was not able to test on latest Firefox build.

NVDA Installed or portable:
Installed

Other information:

Windows version:

Windows 7 and 8 tested.

Name and version of other software in use when reproducing the issue:

Tested with the major browsers on Windows (see above).

Other questions:

N/A.

PratikP1 · 2018-05-21T20:40:31Z

When a number <= 12 is typed and and “test it” button is activated, focus returns to the field and “invalid entry” is announced along with the number that was input. What exact behavior would you want to see here?

Wildebrew · 2018-05-21T20:53:01Z

NVDA should also read the error message that is displayed below the field "the number you typed is not greater than 12". The invalid announcement comes from use of aria-invalid, but I don't see the aria-errormessage attribute being communicated. The error message referenced with aria-errormessage could be read automatically or there should be a shortcut key to read the error message on demand with focus on the input field.

…

On 5/21/18, PratikP1 ***@***.***> wrote: When a number <= 12 is typed and and “test it” button is activated, focus returns to the field and “invalid entry” is announced along with the number that was input. What exact behavior would you want to see here? -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #8318 (comment)

-- Work hard. Have fun. Make history.

PratikP1 · 2018-05-21T20:57:37Z

Perhaps @michaelDCurran can respond here. Does NVDA support aria-errormessage yet? I don’t recall that it does.

aosheter · 2018-05-29T12:01:23Z

Possible duplicate of #7768, but I think this one is better, as it gave @PratikP1 a working example, and is more in depth.

DavidMacDonald · 2018-07-17T15:12:55Z

Seems we have a circle here: #7768 references #8318, and #8318, reference 7768. They both say it's better handled in the other.

Wildebrew · 2018-07-18T11:24:48Z

I don't really care about the issue number, but I do care that we settle on a solution and hope the good people at NVDA can find time to implement it (I know it takes time and I totally respect that). We want to use aria-errormessage so that we can hardcode the error association in the template and then activate it by setting aria-invalid to true on the field when it is in error. This can't be done with aria-describedby because the contents of its target are read regardless of visibility (in other words, a hidden error message referenced with aria-described by is always announced). But until aria-errormessage has better support we can't implement this solution.

…

On 7/17/18, David MacDonald ***@***.***> wrote: Seems we have a circle here: #7768 references #8318, and #8318, reference 7768. They both say it's better handled in the other. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #8318 (comment)

-- Work hard. Have fun. Make history.

Adriani90 · 2019-05-08T14:04:02Z

I can still reproduce this issue in NVDA 2019.1.1 on Firefox 66.0.4 and Chrome 74.
cc: @feerrenrut

Adriani90 · 2020-05-09T10:07:26Z

Still reproducible in Firefox 76.0.1 and Chrome 81. cc: @jcsteh, @aleventhal maybe you have some suggestions here, I think many authors implement aria-errormessage like this but I am not sure if this violates the Aria spec.

jcsteh · 2020-05-11T00:11:24Z

Firefox correctly exposes aria-errormessage using IA2_RELATION_ERROR. NVDA just doesn't support this yet.

Anubarak · 2021-04-23T14:16:56Z

I faced this issue today too and I tought it was due to my wrong code.
Can someone suggest a reader that supports it so I can test my HTML?
@Wildebrew Thanks for your example

woody-li · 2021-08-10T09:25:53Z

Looking forward for this feature.

Miguelklappes · 2021-09-01T18:51:06Z

Hope it gets implemented.

aleventhal · 2021-09-01T18:55:01Z

Similar to what James Teh mentioned, I don't believe this requires anything on the Chrome side. Chrome implements aria-errormessage and aria-invalid via the CORE-AAM spec, e.g. relations IA2_RELATION_ERROR and IA2_RELATION_ERROR_FOR.

james-hill-kc · 2022-05-23T16:02:38Z

This still appears to be an issue as of May 23rd 2022, is a fix expected any time soon?

timveld · 2022-10-20T10:59:52Z

+1 for prioritizing this. JAWS supports aria-errormessage and reads it very nicely, NVDA doesn't. Even though NVDA is the primary screen reader for which we optimize our application, that doesn't mean we can ignore the aria specification (which for good reasons recommends the use of aria-errormessage rather than aria-describedby in this situation).

feerrenrut · 2022-10-21T03:37:43Z

Technical notes to aide anyone willing to take this on:

Look at other fetched relations:

Expose the value from the virtual buffer (nvdaHelper C++ code) look at usages of getRelationId.
- In this case, the relations to look for are IA2_RELATION_ERROR, IA2_RELATION_ERROR_FOR
Other examples to follow: IA2_RELATION_DETAILS / IA2_RELATION_LABELLED_BY
- On the python side, look at def hasDetails, def _get_detailsSummary work / are used.

In this case, it is probably most user friendly to report the error automatically. However, it should be noted that when the error is displayed and exposed to AT there is the risk of reporting the error twice. To remedy these situations, look at how "labelledByContent" works.

onzag · 2022-11-13T15:45:19Z

Is this not yet fixed?... I am currently using orca for development reasons and I did not expect that the same issue was to be found in NVDA, can I use described-by instead?...

Wildebrew · 2023-08-18T03:15:15Z

This is still not fixed (tested with NVDA 2023.1 on latest versions of both Chrome and Firefox.
Does the team have any update?

Adriani90 · 2024-01-31T21:10:48Z

@seanbudd, @gerald-hartig it seems the demand for this from several web developers is quite high even though there is also a discussion on deprecating this role. I think it makes sense to implement support for this in NVDA given this role has already been used in the design of several websites or applications.
At the same time, there are also several bugs in NvDA with regards to aria role alert which is also used to announce error messages.
So to give the user the highest level of accessibility, both alert and errormessage roles should be fully supported in NVDA.

Can you estimate how much effort it would mean to solve this issue at least?

gerald-hartig · 2024-01-31T21:31:35Z

@Adriani90 we've recently started a push to improve our ARIA compatibility. This issue is right at the top of our list to resolve, and we have a specific release in mind for resolution of this one, but I'd like to hold off a bit before making any firm statements around timing. Are there any ARIA issues apart from this one you think we need to tackle as an immediate priority?

Closes #8318 Summary of the issue: Currently, NVDA does not read error messages referenced with aria-errormessage and aria-invalid (or platform native invalid). Description of user facing changes Error messages referenced by aria-errormessage are reported in speech and Braille on nodes marked as invalid. Description of development approach NVDAObjects have a new property, errorMessage, which is retrieved via the error IA2 relation. For virtual buffers, this is done in the virtual buffer backend and stored in the virtual buffer node. For focus mode, this is done at call-time.

ehollig mentioned this issue Jun 3, 2018

NVDA does not support attribute aria-errormessage #7768

Closed

feerrenrut added the ARIA label May 8, 2019

Adriani90 mentioned this issue May 8, 2019

NVDA ignores reading aria-error message with id reference #8605

Closed

This was referenced Dec 20, 2019

aria-errormessage is not output #10642

Closed

In Google Chrome, NVDA does not read an error message when an incorrect value is entered #8657

Closed

feerrenrut added the feature label May 11, 2020

jobara mentioned this issue Aug 23, 2021

feat: form layout improvements (resolves #75) fluid-project/looseleaf#76

Merged

seanbudd added this to the 2022.1 milestone Sep 2, 2021

feerrenrut added the GoogleWork label Nov 5, 2021

seanbudd removed this from the 2022.1 milestone Jan 31, 2022

seanbudd added triaged Has been triaged, issue is waiting for implementation. p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority labels May 24, 2022

damyanpetev mentioned this issue Sep 1, 2022

Grid Validation Implementation IgniteUI/igniteui-angular#11923

Merged

16 tasks

ynotdraw mentioned this issue Feb 14, 2023

feat: Added form field component CrowdStrike/ember-toucan-core#27

Merged

sivakusayan mentioned this issue Oct 2, 2023

Consider deprecating aria-errormessage due to existence of aria-describedby w3c/aria#2048

Open

SaschaCowley self-assigned this Feb 21, 2024

garyb1 mentioned this issue Mar 2, 2024

[material-ui][TextField] Attach aria-errormessage attribute mui/material-ui#38929

Open

2 tasks

SaschaCowley mentioned this issue Apr 17, 2024

Support aria-errormessage #16411

Merged

5 tasks

hansgrimm mentioned this issue Apr 22, 2024

Form: Fix error messages dso-toolkit/dso-toolkit#2141

Open

seanbudd closed this as completed in #16411 May 8, 2024

nvaccessAuto added this to the 2024.3 milestone May 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NVDA does not read error messages referenced with aria-errormessage and aria-invalid #8318

NVDA does not read error messages referenced with aria-errormessage and aria-invalid #8318

Wildebrew commented May 21, 2018

PratikP1 commented May 21, 2018 via email

Wildebrew commented May 21, 2018 via email

PratikP1 commented May 21, 2018 via email

aosheter commented May 29, 2018

DavidMacDonald commented Jul 17, 2018

Wildebrew commented Jul 18, 2018 via email

Adriani90 commented May 8, 2019

Adriani90 commented May 9, 2020

jcsteh commented May 11, 2020

Anubarak commented Apr 23, 2021

woody-li commented Aug 10, 2021

Miguelklappes commented Sep 1, 2021

aleventhal commented Sep 1, 2021

james-hill-kc commented May 23, 2022

timveld commented Oct 20, 2022

feerrenrut commented Oct 21, 2022

onzag commented Nov 13, 2022

Wildebrew commented Aug 18, 2023

Adriani90 commented Jan 31, 2024

gerald-hartig commented Jan 31, 2024 •

edited

NVDA does not read error messages referenced with aria-errormessage and aria-invalid #8318

NVDA does not read error messages referenced with aria-errormessage and aria-invalid #8318

Comments

Wildebrew commented May 21, 2018

Steps to reproduce:

Expected behavior:

Actual behavior:

System configuration:

Other questions:

PratikP1 commented May 21, 2018 via email

Wildebrew commented May 21, 2018 via email

PratikP1 commented May 21, 2018 via email

aosheter commented May 29, 2018

DavidMacDonald commented Jul 17, 2018

Wildebrew commented Jul 18, 2018 via email

Adriani90 commented May 8, 2019

Adriani90 commented May 9, 2020

jcsteh commented May 11, 2020

Anubarak commented Apr 23, 2021

woody-li commented Aug 10, 2021

Miguelklappes commented Sep 1, 2021

aleventhal commented Sep 1, 2021

james-hill-kc commented May 23, 2022

timveld commented Oct 20, 2022

feerrenrut commented Oct 21, 2022

onzag commented Nov 13, 2022

Wildebrew commented Aug 18, 2023

Adriani90 commented Jan 31, 2024

gerald-hartig commented Jan 31, 2024 • edited

gerald-hartig commented Jan 31, 2024 •

edited