On Fri, Dec 1, 2017 at 11:49 AM, Jonathan Kingston <j...@mozilla.com> wrote: > If roles are mapped 1:1 to HTML features we basically: > - Promote the use of bad markup and the expectation that bad markup will > use good ARIA.
It's pretty clear that <input> and <select> et al have limitations that are not acceptable for certain UIs on the web. At that point you need to implement those controls yourself. If we don't offer the same APIs that the browser uses to implement <input> and <select> et al, we're basically saying that only high-level approaches can be accessible. That's not acceptable. We should strive to remove the limitations of the high-level approaches so they become more appealing and more widely adopted, but we should not withhold low-level APIs. > - The need to reimplement all of HTML into ARIA becomes greater. It's not a reimplementation. It's effectively exposing the signal the browser sends to assistive technology for a particular element so custom controls can send the same signal indicating they behave in a roughly equivalent way. -- https://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
