E-mail List Archives
Re: 4.1.1 Parsing > nested elements
From: Jonathan Avila
Date: Mar 31, 2018 6:18PM
- Next message: Jonathan Avila: "Re: Experience with MS Teams"
- Previous message: JP Jamous: "Re: 4.1.1 Parsing > nested elements"
- Next message in Thread: Steve Faulkner: "Re: 4.1.1 Parsing > nested elements"
- Previous message in Thread: JP Jamous: "Re: 4.1.1 Parsing > nested elements"
- View all messages in this Thread
> Use of role=navigation on <ul> is a conformance error
Hi Steve, yes, agreed -- bad choice of example on my part. My question/statement was that when an allowed role is applied to an HTML element or one of it's children then that applied allowed role alters the allowed parent/child elements and allowed roles. Thus the use of the role can break the nesting structure role/implied role and in such cases even if ARIA is applied to only the parent or the child a 4.1.1 violation can occur. That is the nesting structure requirements for 4.1.1 should be based on the calculated role not the element's tag name.
Jonathan
Jonathan Avila
Chief Accessibility Officer
Level Access
<EMAIL REMOVED>
703.637.8957 office
Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog
See you at CSUN in March!
- Next message: Jonathan Avila: "Re: Experience with MS Teams"
- Previous message: JP Jamous: "Re: 4.1.1 Parsing > nested elements"
- Next message in Thread: Steve Faulkner: "Re: 4.1.1 Parsing > nested elements"
- Previous message in Thread: JP Jamous: "Re: 4.1.1 Parsing > nested elements"
- View all messages in this Thread