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] Agreement on concatenation of aria-describedby and aria-errormessage relationships

Perhaps there should be an API to compute the full (recursive) text for any given node, so when you want to get the text from a relation or something else indirect without actually jumping to it, you could do that with one call rather than exploring it recursively. In any event, performance seems

Re: [Accessibility-ia2] Bitmask for rare accessibility attributes

On Tue, Sep 6, 2016 at 5:39 PM James Teh wrote: > What do you think about using an object attribute (or attributes) to do > this, rather than a separate bit mask? That way, it's much easier to add > new ones. Also, I'm guessing most AT (certainly screen readers) already >

Re: [Accessibility-ia2] Agreement on concatenation of aria-describedby and aria-errormessage relationships

That doesn't solve the need to walk the tree to gather the error message, which is the real problem. On 7/09/2016 12:21 PM, Richard Schwerdtfeger wrote: I think Dominic's suggestion on an interface tester with bit flags works well. Rich Rich Schwerdtfeger - Original message -

Re: [Accessibility-ia2] Form role mapping

Jamie,   I thought I addressed this before: The HTML AAM points to the ARIA core mapping specification now. They will implement what we have. One of the reasons ARIA in HTML is being held up is for us. The plan is for the host language platforms to use as much of the ARIA spec. as possible to

Re: [Accessibility-ia2] Agreement on concatenation of aria-describedby and aria-errormessage relationships

I think Dominic's suggestion on an interface tester with bit flags works well.   Rich   Rich Schwerdtfeger     - Original message -From: James Teh To: Richard Schwerdtfeger/Austin/IBM@IBMUS, surkov.alexan...@gmail.com, ble...@freedomscientific.com, jdi...@igalia.comCc:

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     -

Re: [Accessibility-ia2] Bitmask for rare accessibility attributes

That makes sense to me.  Rich Schwerdtfeger     - Original message -From: Dominic Mazzoni via Accessibility-ia2 Sent by: accessibility-ia2-boun...@lists.linuxfoundation.orgTo: accessibility-...@lists.linux-foundation.orgCc:Subject:

Re: [Accessibility-ia2] Bitmask for rare accessibility attributes

That's a very interesting idea. Note that for errormessage, we can first test for the invalid state, so this wouldn't help that. (The bigger problem there is walking the tree to get the message from the target.) What do you think about using an object attribute (or attributes) to do this,

Re: [Accessibility-ia2] Agreement on concatenation of aria-describedby and aria-errormessage relationships

Fair enough. Thanks for the clear reasoning. My one remaining concern is performance, but we will clearly need to find an alternative technical solution to this problem. In short, not concatenating means that for every focus event, we need to check for the invalid state plus an errormessage

Re: [Accessibility-ia2] Form role mapping

Hi Rich, I've already stated my view on this: I understand the reason for the use of the landmark role for role="form". However, I disagree with the HTML form element being mapped to the landmark role because semantics are lost. The fact that something is a form has more semantic value

[Accessibility-ia2] Bitmask for rare accessibility attributes

One of the objections Jamie brought up to making aria-errormessage an additional interface is that it increases the number of interfaces AT needs to call on every single accessible. I've also thought about this same issue, as the number of nodes in an average web page continues to grow along with

[Accessibility-ia2] Agreement on concatenation of aria-describedby and aria-errormessage relationships

  The ARIA working group is against concatenating the description and relationship strings. I will try to summarize:   Specifically, concatenation by browsers could:   Defeat the purposes of aria-errormessage. The aria-errormessage relationship is designed to ensure assistive technology

[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