- From: Aaron Leventhal <aleventhal@google.com>
- Date: Tue, 22 May 2018 22:10:59 -0400
- To: Matt King <a11ythinker@gmail.com>
- Cc: public-aria-practices@w3.org
Received on Wednesday, 23 May 2018 02:11:35 UTC
Hi Matt, Chrome tries to enforce rules around activedescendant usage, even though the core aam doesn't require it. Firefox does not try to do this. These restrictions got in the way this time by expecting an aria role that supports activedescendant. The code should have allowed the textfield role to come from the native input element, and buy require an aria role. Here's the bug: https://bugs.chromium.org/p/chromium/issues/detail?id=845651 Aaron On Tue, May 22, 2018, 9:02 PM Matt King <a11ythinker@gmail.com> wrote: > Aaron, thanks! Can you point to the bug? > > > > Was it a change related to activedescendant? > > > > Matt > > > > *From:* Aaron Leventhal [mailto:aleventhal@google.com] > *Sent:* Tuesday, May 22, 2018 6:01 PM > *To:* public-aria-practices@w3.org > *Subject:* ARIA 1.1 combobox examples fix in Chrome > > > > Hi all, I just landed a change that should show up in tomorrow's Canary. > > > > It fixes the ARIA 1.1 combobox examples in Chrome. The dropdown list items > were not being read by screen readers as the user arrowed through them. > > > > Thanks, > > Aaron > > >
Received on Wednesday, 23 May 2018 02:11:35 UTC