Not mapped only means that the element is not mapped. Hidden should apply to the element and its subtree unless a descendant is overridden by the element. So, I think a better solution would be to not to expose the role at all and allow it to default to the native host language semantics. In this case it does not matter whether it has focus or not. In fact, I think it would be best to state that in the mapping spec. that defines what it means to not be mapped. We should say that it defaults to the native host language semantics and the ARIA role is not exposed. Would this not be a better approach? Rich Schwerdtfeger > On Oct 27, 2016, at 9:24 AM, Alexander Surkov <asurkov@mozilla.com> wrote: > > Thinking more, aria-hidden='true' might be not that bad, even with its > ambiguity of the usage and implementations in the browsers. If you say > 'not mapped', then I think you should say if this is applied to > elements from its subtree, also you may need to clarify the edge > cases, for example, what happens, if the focus goes into 'pullquote' > element. > > Having said I would probably prefer if that was the author's > responsibility to hide the element from AT, either by moving it > offscreen or putting aria-hidden='true' on it. > > Also I don't quire understand why would we need to have 'pullquote' > role in the first place. If pullquote doesn't have semantics, then it > doesn't seem worthwhile to have ARIA role for it. > > Thanks. > Alexander. > > On Thu, Oct 27, 2016 at 9:34 AM, Rich Schwerdtfeger > <richschwer@gmail.com> wrote: >> Based on this discussion: >> >> https://lists.w3.org/Archives/Public/public-dpub-aria/2016Oct/0029.html >> >> I want to change the dpub-aam mapping to not mapped for all platforms. That >> includes (not xml-roles values for linux and Windows IA2 mappings). It means >> that the Mac mapping would go form group to not mapped. >> >> Any disagreement? >> >> Regards, >> Rich >> >> Rich Schwerdtfeger >> >> >> >>
Received on Thursday, 27 October 2016 16:06:13 UTC