Hi Alex,
 
Correct, aria-details requires no special role. However, the use case is for the digital publishing industry. They want to be able to take a piece of content and go to the alternative content that provides detailed information which could be alternative content as we discussed previously. The user may or may not wish to go back to the content the details is being provided for.
 
The need for a reverse relationship for the error message is more critical.
 
So, do we agree on a reverse relationship for error message and not details?
 


Rich Schwerdtfeger
 
 
----- Original message -----
From: Alexander Surkov <surkov.alexan...@gmail.com>
To: Brett Lewis <ble...@vfo-group.com>
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, "ja...@nvaccess.org" <ja...@nvaccess.org>, "jdi...@igalia.com" <jdi...@igalia.com>, "accessibility-...@lists.linux-foundation.org" <accessibility-...@lists.linux-foundation.org>
Subject: Re: Reverse relationships
Date: Wed, Sep 7, 2016 10:34 AM
 
You're right. An element referred by aria-errormessage can be an alert of live region and thus should be announced by a screen reader, when it pops up. In this case, it seems the screen reader may need to find a context element, and if this is true, then the reverse relation is needed.
 
aria-details are different, since they are more like labels and descriptions, and I guess thus they should be skipped when navigating the virtual buffer. That suggests that aria-details either needs a role (or xml-roles object attribute) or a reverse relation.
 
On Wed, Sep 7, 2016 at 11:11 AM, Brett Lewis <ble...@vfo-group.com> wrote:

Hi,

Is that documented somewhere?

I read through the information on error and I don’t see anything about AT skipping error messages if encountering them while reading through the virtual buffer.

Have I misunderstood something?

Thanks,

Brett

 

Brett Lewis

VFO | Software Engineer

11800 31st Court North, St. Petersburg, FL 33716

T 727-299-6270

blewis@vfo-group.com

www.vfo-group.com

 

 

From: Alexander Surkov [mailto:surkov.alexander@gmail.com]
Sent: Wednesday, September 07, 2016 8:02 AM
To: Brett Lewis <ble...@vfo-group.com>
Cc: Richard Schwerdtfeger <sch...@us.ibm.com>; ja...@nvaccess.org; jdi...@igalia.com; Accessibility-ia2@lists.linux-foundation.org
Subject: Re: Reverse relationships

 

Hi, Brett.

Can you please elaborate your use case? My understanding is AT skips error/details, if the user encounters them, but announce them, when the user navigates to an element related with error/details. Why would AT need to find a related element by error/details?

Thanks.

Alex.

 

On Wed, Sep 7, 2016 at 9:42 AM, Brett Lewis <ble...@vfo-group.com> wrote:

Hi Rich,

I think we do need the reverse relationships.

Web authors can place the error/details anywhere on the page and there doesn’t seem to be any simple way for the user to determine what element the error message or details applies to without such a reverse relation.

Brett

 

 

Brett Lewis

VFO | Software Engineer

11800 31st Court North, St. Petersburg, FL 33716

T 727-299-6270

blewis@vfo-group.com

www.vfo-group.com

 

 

From: Richard Schwerdtfeger [mailto:sch...@us.ibm.com]
Sent: Tuesday, September 06, 2016 12:57 PM
To: ja...@nvaccess.org; surkov.alexan...@gmail.com; Brett Lewis <ble...@vfo-group.com>; jdi...@igalia.com
Cc: Accessibility-ia2@lists.linux-foundation.org
Subject: Reverse relationships

 

We need agreement:

 

Should the error message and details relationships have reverse mappings?

 

Rich

 



Rich Schwerdtfeger

 

 

 

_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2

Reply via email to