Re: [Accessibility-ia2] Reverse relationships

Hi Janina,    I believe you are still the a11y director at the LF? Can you see any reason why IA2 could not be moved to github?   Rich Rich Schwerdtfeger     - Original message -From: Alexander Surkov Sent by:

Re: [Accessibility-ia2] Reverse relationships

A dummy copy/paste apparently makes a bad job. Thanks for the catch. Here is the change [1]. I guess we could ask them to move the repo to GitHub, not sure if there are any reasons to keep it on the LF server. [1]

Re: [Accessibility-ia2] Reverse relationships

I think IA2 should be moved to github as well. Rich Schwerdtfeger     - Original message -From: James Teh Sent by: accessibility-ia2-boun...@lists.linuxfoundation.orgTo: Alexander Surkov Cc: IAccessible2 mailing list

Re: [Accessibility-ia2] Reverse relationships

On 8/09/2016 9:22 PM, Alexander Surkov wrote: Thank you, Jamie. I'm taking that screen readers may need to a context element, when error message pops up, as a use case for a reverse relation (if not, please correct me). I think we'd more likely use it if the user is reviewing a form (rather

Re: [Accessibility-ia2] Reverse relationships

On Wed, Sep 7, 2016 at 3:25 PM, Richard Schwerdtfeger wrote: > 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

Re: [Accessibility-ia2] Reverse relationships

Thank you, Jamie. I'm taking that screen readers may need to a context element, when error message pops up, as a use case for a reverse relation (if not, please correct me). Could you also comment my guess about aria-details? If a screen reader skips aria-details elements when navigating, then

Re: [Accessibility-ia2] Reverse relationships

Agreed. Happy to have a reverse relation for errormessage, since we seem to have a use case. We don't seem to have a compelling use case for a reverse relation for details, so let's leave it out for now. On 8/09/2016 5:25 AM, Richard Schwerdtfeger wrote: Hi Alex, Correct, aria-details

Re: [Accessibility-ia2] Reverse relationships

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

Re: [Accessibility-ia2] Reverse relationships

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

Re: [Accessibility-ia2] Reverse relationships

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.

Re: [Accessibility-ia2] Reverse relationships

- Original message - > From: James Teh <ja...@nvaccess.org> > To: Dominic Mazzoni <dmazz...@google.com>, Richard > Schwerdtfeger/Austin/IBM@IBMUS > Cc: accessibility-...@lists.linux-foundation.org > Subject: Re: [Accessibility-ia2] Reverse relationships

Re: [Accessibility-ia2] 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,

Re: [Accessibility-ia2] Reverse relationships

To be clear, we would not document them in the mapping specification if they are not implemented.   When I say add them later I am referring to the mapping spec. and browsers. However, doing that has ramifications for AT vendors. Rich Schwerdtfeger     - Original message -From: James Teh

Re: [Accessibility-ia2] Reverse relationships

That's fair. The only problem is that if they're documented in the mapping spec, browsers are technically non-compliant if they don't implement. On 7/09/2016 2:58 PM, Dominic Mazzoni wrote: Is there any reason we shouldn't *define* the reverse relationships now? Browsers can choose not to

Re: [Accessibility-ia2] Reverse relationships

Is there any reason we shouldn't *define* the reverse relationships now? Browsers can choose not to implement them now for performance reasons, and AT can choose to ignore them. On Tue, Sep 6, 2016 at 7:16 PM Richard Schwerdtfeger wrote: > Jamie, > > > Well you can add

Re: [Accessibility-ia2] Reverse relationships

Jamie,     Well you can add reverse relationships later if it becomes an issue. The only problem with adding it later is you will also then need to test if that reverse relation ship exists and what to do with older browsers that won't have the relationship.   Rich   Rich Schwerdtfeger     -

[Accessibility-ia2] 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