ARIA in HTML (w3c/html-aria#372) is tightening the rule on use of aria-checked, particularly due to w3c/aria#1622 and the fact that aria-checked=mixed should never be able to be exposed by browsers that correctly follow the ARIA spec.

we would request that this at the very least this be called out as an author error if using aria-checked=mixed on a checkbox.

There is a bug in chromium now where aria-checked incorrectly takes precedent over the native checked / dirty checked state of an element, which can cause inaccurate information to be exposed if the checked state and the aria-checked attribute are out of alignment: https://bugs.chromium.org/p/chromium/issues/detail?id=1260371

@MHoov Where can I find the "general rule description (SME & Dev)" and testcases that were written as of June 1? I don't know where to look.

Notes from Triage Meeting:

If aria tag "overrides" the native elements state in an AT then this should be a violation.

According to a quick chrome test the aria tag overrides the native behavior. So we are expecting this to be a Violation.

Hey team! Please add your planning poker estimate with ZenHub @aliunwala @mbgower @shunguoy @tombrunet @philljenkins @drjoho

this might be expanded to a more generic case when a user explicitly specifies a role that is the same or conflicts with the implicit role.

this will be covered in #721, close as fixed.