- From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
- Date: Tue, 15 Aug 2017 20:45:33 +0000
- To: Steve Faulkner <faulkner.steve@gmail.com>
- CC: ARIA Working Group <public-aria@w3.org>
- Message-ID: <BN6PR03MB2785640A86E449444D5EDC6CF28D0@BN6PR03MB2785.namprd03.prod.outlook.com>
Sorry about that, I meant to but missed it. http://www.w3.org/TR/html-aria/#docconformance Bryan Garaventa Accessibility Fellow Level Access, Inc. Bryan.Garaventa@LevelAccess.com 415.624.2709 (o) www.LevelAccess.com From: Steve Faulkner [mailto:faulkner.steve@gmail.com] Sent: Tuesday, August 15, 2017 4:07 AM To: Bryan Garaventa <bryan.garaventa@levelaccess.com> Cc: ARIA Working Group <public-aria@w3.org> Subject: Re: ARIA and HTML document question about implicit headings Bryan wrote: "I noticed recently that according to the ARIA and HTML mapping tables, the use of aria-level is said to not be allowed on H1 through H6 elements, even though these implicitly map to role="heading"." It would be really helpful to provide a reference to a source when making such statements. On Monday, 14 August 2017, Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>> wrote: Hi, I noticed recently that according to the ARIA and HTML mapping tables, the use of aria-level is said to not be allowed on H1 through H6 elements, even though these implicitly map to role="heading". Since supporting attributes like aria-pressed and aria-haspopup are accepted on other implicit elements like role="button", amongst other implicit role and attribute combinations, why is this one different? Bryan Garaventa Accessibility Fellow Level Access, Inc. Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com> 415.624.2709 (o) www.LevelAccess.com<http://www.LevelAccess.com> -- -- Regards SteveF Current Standards Work @W3C<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
Received on Tuesday, 15 August 2017 20:46:01 UTC