1501182 - Expose the landmark role on elements that have a WAI-ARIA landmark role

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect, P2)

Description

[Marco Zehe (:MarcoZ)]

The new WAI-ARIA 1.1 landmark role mapping should be applied to banner, complementary, contentinfo, form, main, navigation, region if the element also has an accessible name, and search.

Comment 1

[laura2342]

Currently, firefox assigns a "banner" role to <header> element regardless of whether it appears nested in another landmark. Per updated landmark role mapping: 

https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/landmarks/HTML5.html

header: banner when in context of the body element. The header element is not a banner landmark when it is a descendant of the following HTML5 sectioning elements:

    article
    aside
    main
    nav
    section

Comment 2

[Marco Zehe (:MarcoZ)]

(In reply to laura2342 from comment #1)
> Currently, firefox assigns a "banner" role to <header> element regardless of
> whether it appears nested in another landmark. Per updated landmark role
> mapping: 
> 
> https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/
> landmarks/HTML5.html
> 
> header: banner when in context of the body element. The header element is
> not a banner landmark when it is a descendant of the following HTML5
> sectioning elements:
> 
>     article
>     aside
>     main
>     nav
>     section

Thanks Laura, this is a separate issue, and I will file a bug for it shortly. One additional question, though, does this apply to footer, too? Right now, header and footer elements get the same treatment as for whether they should be treated as landmark elements or not. If footer is different, e. g. it *is* allowed inside such other landmarks, we'll need to separate them.

Comment 3

[laura2342]

Yes- same idea for the footer; if the footer is nested it shouldn't have contentinfo applies as a landmark.

Comment 6

[Marco Zehe (:MarcoZ)]

Attachment: Bug 1501182 - Expose WAI-ARIA landmarks as landmark roles through accessibility APIs, r=Jamie

Comment 7

[Marco Zehe (:MarcoZ)]

(In reply to laura2342 from comment #1)

Currently, firefox assigns a "banner" role to <header> element regardless of
whether it appears nested in another landmark. Per updated landmark role
mapping:

https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/
landmarks/HTML5.html

header: banner when in context of the body element. The header element is
not a banner landmark when it is a descendant of the following HTML5
sectioning elements:

article
aside
main
nav
section

For completeness, this was dealt with in bug 1573750.

Comment 8

[Marco Zehe (:MarcoZ)]

Treeherder results will appear here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=1f1ba5181ebbb2570be7df1f006e42f1454855b2

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3769178b9a30
Expose WAI-ARIA landmarks as landmark roles through accessibility APIs, r=Jamie

Comment 10

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/3769178b9a30