Re: Request from APA-WG re ARIA in HTML Spec

>I don't recommend entering CR until these issues are addressed, because
there are currently many roles that are missing from the >accepted role
usage column, and if they are omitted then HTML validators will start
flagging valid constructs with false reports as >being invalid usages of
ARIA.

as I stated on the bug Bryan filed
<https://github.com/w3c/html-aria/issues/102#issuecomment-373287694>


   - The default implicit column mappings are defined in the HTML AAM
   <https://w3c.github.io/html-aam/>, if you have issue with these you will
   need to file issues there.
   - it is not simply enough to state that "the accepted
   roles/states/properties column is missing". As a host language HTML can and
   does limit the allowed roles on elements with meaningful default semantics.
   If it is requested that a particular role be allowed, then a case needs to
   be made for why.

Furthermore,

and if they are omitted then HTML validators will start flagging valid
> constructs with false reports as being invalid usages of ARIA.


What is in the current ARIA in HTML spec is what is implemented in the HTML
validator. The rules have been implemented in the HTML validator in some
form or other since 2010 as they were defined in HTML5.
<https://www.w3.org/TR/2014/REC-html5-20141028/dom.html#sec-strong-native-semantics>
If you review those rules it will be evident that in most cases they are
less stringent now than they were when initially defined. The relaxation of
the rules has been, in general on a case by case basis, based on use cases.



--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>

On 15 March 2018 at 07:35, Bryan Garaventa <bryan.garaventa@levelaccess.com>
wrote:

> Hi,
> I've completed my initial review of the spec document as I was asked to do
> last week, and have filed the issues I discovered here
> https://github.com/w3c/html-aria/issues/102
>
> I don't recommend entering CR until these issues are addressed, because
> there are currently many roles that are missing from the accepted role
> usage column, and if they are omitted then HTML validators will start
> flagging valid constructs with false reports as being invalid usages of
> ARIA.
>
> The changes are relatively simple though by adding the missing roles, so
> an update likely wouldn't take long.
>
> There are some areas where the mappings seem unclear to me, or where I've
> added suggestions regarding default role mappings. Areas beginning with FYI
> are simply informative in case the info is helpful.
>
> All of the other content appears clear to me though, and I found no issues
> while scanning the remainder of the document.
>
> Bryan Garaventa
> Accessibility Fellow
> Level Access, Inc.
> Bryan.Garaventa@LevelAccess.com
> 415.624.2709 (o)
> www.LevelAccess.com
>
> -----Original Message-----
> From: Janina Sajka <janina@rednote.net>
> Sent: Thursday, March 08, 2018 6:38 AM
> To: W3C WAI ARIA <public-aria@w3.org>; Joanmarie Diggs <jdiggs@igalia.com>
> Subject: Request from APA-WG re ARIA in HTML Spec
>
> Hello ARIA:
>
> Wearing my hat as APA Chair, I'd like to ask you to consider whether an
> ARIA review of the Web Platforms WG specification ARIA in HTML is needed.
> The Web Platforms WG has requested to take this specification to Candidate
> Recommendation (CR):
>
> http://w3c.github.io/html-aria/publish/index-CR-20180215.html
>
> There's considerable history behind this document which I won't attempt to
> summarize in this email. However, it would be very helpful for the ARIA-WG
> to take at least a quick look to determine whether there are any problems
> in this specification that should be cleared up before the document moves
> further.
>
> Janina
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:       http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa
>
>
>
>