Re: [Accessibility-ia2] aria-details and aria-errormessage mapping [Issue-1044]

Alex, Jamie,   We discussed this concatenation and Microsoft (Cynthia Shelly) and also Matt King and the more we look at concatenation the worse it looks. This impact more than IA2. It would effect the UIA Mapping for Edge and it creates problems for internationalization whereby we can't put a

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

> > > I have included Joseph on CC so that he is aware of the name and > > description issue. > > > > Rich Schwerdtfeger > > > > > > > > - Original message - > > From: Richard Schwerdtfege

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

  Sent by: accessibility-ia2-boun...@lists.linuxfoundation.org>     To: jdi...@igalia.com>     Cc: accessibility-ia2@lists.linuxfoundation.org>     Subject: Re: [Accessibility-ia2] aria-details and aria-errormessage>     mapping>     Date: Wed, Aug 24, 2016 10:01 AM>      >  

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

These were the original relation names for error message and details   IA2_RELATION_DETAILS IA2_RELATION_ERROR_MESSAGE   I also have these relationships for ATK/ATSPI: RELATION_DETAILS RELATION_ERROR_MESSAGE   They are listed in this branch I am working on:

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

ok.   So, Alex, please provide me the name of the two IA2 relationships fore details and error message? I will work with joseph and amelia to look at concatenation of error messages in the description.   Also, Joanie expressed a desire to have reverse relationships for details and error message. I

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Hey Rich. On matters where I have no strong opinion, but Jamie does, I defer to Jamie. Mapping of aria-details and aria-errormessage for my platform falls into this category, at least currently. Let's suck it and see. --joanie On 08/24/2016 10:39 AM, Richard Schwerdtfeger wrote: > Alright. I am

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

I'm not yet certain if we agreed upon how to expose aria-details, because longdesc is exposed as an action, which pops up a window with the longdesc, when invoked. My understanding is it is a web author responsibility to implement aria-details UI, and thus action mechanism perhaps is not suitable

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Hi Rich, If it's not being stringified, IMO, it doesn't make sense to use describedBy because describedBy should all be stringified in description. My question is why it can't be stringified. You say it can't be stringified because: 1. "the content must be visible": That's not a reason not

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Hi James,   If you wanted to reuse the existing description relationships (with a separate description relationship instance) and place an object attribute on the error message target to indicate that it is an error message I think that makes perfect sense. It just can't be stringified. However,

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Hi Rich, Thanks for the clear explanations; I really do appreciate it. Part of the confusion here is that I've unintentionally conflated aria-details with aria-errormessage. Regarding aria-details, what you say absolutely makes sense. Given that, reading the details automatically as a

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

>I've already stated my view on this and asked several questions, but it seems key decisions have already been made, despite a lack of clarification around the concerns I've raised. >Given that this has basically become a circular time sink of an argument, I'll provide a final summary of my

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

We *cannot* map aria-errormessage or aria-details to a string description. That is absolutely prohibited in the aria specification. It is not to be stringified. Neither is aria-details. Also, in the aria spec. if aria-details and aria-describedby cannot be mapped separately aria-details takes

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

I'd love to hear Jamie on this honestly, but his wording was: " To me, it sounds like errormessage just makes the rules slightly simply to make life simpler for authors; errormessage isn't presented unless invalid is true, errormessage must be visible to be presented, etc. That might be fair

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

The reason one might wish to have the reverse relationship is if the error messages could be encountered independently. Consider the following scenario: 1. User fills out form 2. User presses submit 3. New page loads displaying the errors at the top with the form fields reproduced below the

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Note, Jamie has been objecting against new relation for aria-errormessage [1]. [1] https://lists.linuxfoundation.org/pipermail/accessibility-ia2/2016-April/002046.html On Wed, Aug 10, 2016 at 8:33 AM, Alexander Surkov < surkov.alexan...@gmail.com> wrote: > All reverse relations go at

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Those would be great. What would you have for reverse relationships?   Rich Schwerdtfeger     - Original message -From: Alexander Surkov To: "accessibility-ia2@lists.linuxfoundation.org" , James Teh

Re: [Accessibility-ia2] aria-details and aria-errormessage mapping

Hey Alex, all. On both of these, we were waiting on the IA2 mapping because I was/am pretty sure that I'd be okay with your mappings and would duplicate them in ATK and AT-SPI2. I'm fine with what you propose below, but do we also want a reciprocal relation type? --joanie On 08/09/2016 03:12