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

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] Bitmask for rare accessibility attributes

I'd say the bitmask idea is covered by states concept, for example, see STATE_SYSTEM_HASPOPUP [1]. I guess we can add more IA2 states if needed. [1] https://msdn.microsoft.com/en-us/library/windows/desktop/dd373609(v=vs.85).aspx On Tue, Sep 6, 2016 at 8:39 PM, James Teh

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

Hi Rich, I think you nicely articulated our concerns w/r/t the concatenation of error/description information. In particular, it is really hard to separate out error information from a description if the user wants it for some reason while concatenating the information is not too difficult.

Re: [Accessibility-ia2] Form role mapping

Hi Rich, I think this is fine. This seems like a reasonable way to move forward. Brett Brett Lewis VFO | Software Engineer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6270 ble...@vfo-group.com www.vfo-group.com From: Richard

Re: [Accessibility-ia2] Reverse relationships

I'd say we need have the reverse relations in both of specs (IA2 and UAIG) and implemented in the browsers, iff there's a valid use case for them, and intentions from screen readers to implement them. On Wed, Sep 7, 2016 at 8:44 AM, Richard Schwerdtfeger wrote: > To be clear,

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] Form role mapping

There's a point in discussing, the spec can be changed, if there's solid ground for that. My concerns are: * Both IA2 and ATK have a better role match for both role='form' and HTML form, which is ATK_ROLE_FORM and IA2_ROLE_FORM. Thus if there's no strong reason why we have to use a 'weaker'

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

To clarify, I'm concerned about aria-errormessage here. For aria-details, we wouldn't be trying to report the information as one chunk. Instead, the user would perform a command to navigate to the details, at which point they would browse it like they browse any other content. For

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

Yes it may provide alternative content as well.   Rich Schwerdtfeger     - Original message -From: Alexander Surkov To: James Teh Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, IAccessible2 mailing list

Re: [Accessibility-ia2] Form role mapping

>*AT and browsers support those roles, if Firefox Nightly starts to expose IA2_ROLE_LANDMARK instead IA2_ROLE_FORM, then it >breaks all existing screen reader versions. In case of commercial screen readers this is painful for the users, since they have to buy a >new version of their screen reader.