Andrea Fercia

Related: https://github.com/Yoast/wordpress-seo/pull/10891 I'm afraid in the Edit view we'll have to keep the `` or use a ``.

The heading font used by Gutenberg depends on the active theme.

I might understand a 16 pixels font size for normal text, though inconsistent with core. Ideally, these changes should be evaluated holistically. I'd tend to think having some admin pages...

FWIW: I'd agree the WordPress default font size is too small with today's screens 🙂 However, the point is Health Check should just look like a WordPress admin page.

Maybe the OOA example that uses `aria-autocomplete=“inline”` would be more interesting for your needs: http://oaa-accessibility.org/examplep/combobox2/

Please also notice both examples use a container with `role="application"` and the options list uses `role="listbox"` and `role="option"` for the items, that's also what Mr. Zehe suggests to do for...

Hi okonomiyaki :) This is what a treeview is intended to be: http://www.w3.org/TR/wai-aria-practices/#TreeView So it's really about items that can be expanded or collapsed. Working example: http://accessibleculture.org/research-files/aria-tree-views/treeviewD.html Tested with Firefox...

Getting different results here, can still reproduce on Firefox, see screenshot below (Firefox 44, NVDA 2015.4). Worth noting testing with Chrome + NVDA is a bit pointless, since it's not...

@kevin-brown hello. I've recently spent some time investigating on this and I think there's probably more than one reason why the options are not announced by screen readers. I _think_...

Just submitted a PR as a first attempt to improve things :) There are best practices and examples to follow to build a "combobox widget", and also the suggested W3C...