Version: 48.0.2564.116 m OS: win10 Currently in Chrome, <header> and <footer> are exposed as banner/contentinfo landmark roles unless contained with <section> or <article> elements, we think this is too broad and these roles should only exposed if not a child of any sectioning content or main elements the acc API mappings for the elements reflect this stricter definition: API mapping for header and footer http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-header http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-footer related API spec issue https://github.com/w3c/aria/issues/277
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8a0d208a1fff647a2e9861f82462f60c4368efa5 commit 8a0d208a1fff647a2e9861f82462f60c4368efa5 Author: je_julie.kim <je_julie.kim@chromium.org> Date: Fri Feb 03 11:03:04 2017 Updated descendant condition for header/footer AX role mapping. This patch doesn't assign header and footer roles for descendants of main or other sectioning content or sectioning root element. BUG= 591328 Review-Url: https://codereview.chromium.org/2649953004 Cr-Commit-Position: refs/heads/master@{#447974} [modify] https://crrev.com/8a0d208a1fff647a2e9861f82462f60c4368efa5/content/test/data/accessibility/html/landmark-expected-android.txt [modify] https://crrev.com/8a0d208a1fff647a2e9861f82462f60c4368efa5/content/test/data/accessibility/html/landmark-expected-mac.txt [modify] https://crrev.com/8a0d208a1fff647a2e9861f82462f60c4368efa5/content/test/data/accessibility/html/landmark-expected-win.txt [modify] https://crrev.com/8a0d208a1fff647a2e9861f82462f60c4368efa5/content/test/data/accessibility/html/landmark.html [modify] https://crrev.com/8a0d208a1fff647a2e9861f82462f60c4368efa5/third_party/WebKit/Source/modules/accessibility/AXNodeObject.cpp [modify] https://crrev.com/8a0d208a1fff647a2e9861f82462f60c4368efa5/third_party/WebKit/Source/modules/accessibility/AXNodeObject.h
Comment 1 by je_julie...@samsung.com
, May 27 2016Status: Assigned (was: Untriaged)