- From: Aaron Leventhal <aleventhal@google.com>
- Date: Mon, 15 May 2017 20:25:10 +0000
- To: ARIA Working Group <public-aria@w3.org>
- Message-ID: <CA+1LECT=NWbWwbTBVwsk0aC0zS6bFD20nL+cxPQFt5EcKQ46SA@mail.gmail.com>
Alert https://rawgit.com/w3c/aria-practices/master/examples/alert/index.html Comments: - Probably worth having an alternate example that uses aria-hidden to trigger CSS display:none becoming display:block. This should also be a legal way of doing alert, and it’s a pretty common way of making content suddenly visible. Button https://rawgit.com/w3c/aria-practices/master/examples/menu-button/menu-button-links.html# Comments: - Tabbing to button, entire button does not scroll into view (only top half does) - Pressing Space or Enter on button, document scrolls to top and button + links are scrolled out-of-view Disclosure https://rawgit.com/w3c/aria-practices/master/examples/disclosure/disclosure-faq.html Comments: - Minor comment: is it worth putting the disclosed text in a live region so that it is read automatically upon expansion? We do this in the tab example. Grid https://rawgit.com/w3c/aria-practices/master/examples/grid/dataGrids.html Comments: - Steals Alt+left/alt+right, and probably other modified arrow keys. In all examples, the keyboard handler should be very careful about rejecting keys with modifier combinations that are not used. Also, the keys that are used should be consumed. The treegrid example is very careful about this. Listbox https://rawgit.com/w3c/aria-practices/master/examples/listbox/listbox.html Comments: - Not sure why, but NVDA reads “not selected” for items but never reads “selected” in both Chrome and Firefox. The experience doesn’t seem right, reading “checked” for selected items but “unselected” for the opposite. Also, the author should not need to include “checked” in the name since that should be read automatically, that’s what the semantics are for. - NVDA does not read that the list is multiselectable upon entry into the list. This should be reported to the NVDA team. - Chrome should be exposing the SELECTED state for the focused item in single selection lists when aria-selected is not "false" Menubutton Comments: - Get 404 errors for links to the two examples from https://rawgit.com/w3c/aria-practices/master/examples/ Radiobutton https://rawgit.com/w3c/aria-practices/master/examples/radio/radio-1/radio-1.html Comments: - Steals alt+left, alt+right as other examples do. We need to fix all the example to be exact with the modifier logic, so I won’t list this problem for each example. Slider https://rawgit.com/w3c/aria-practices/master/examples/slider/slider-1.html Comments: - Does not work with Chrome. I’ve filed a bug in Chrome for this. - There are 3 valuechange events for each slider movement, which does not seem like the normal case, and makes it harder to use for debugging. However, this is not a deal-breaker or anything like that. Progressbar - Example not present, but I suggest it should be as it’s widely useful, and very similar to writing a slider Tree https://rawgit.com/w3c/aria-practices/master/examples/treeview/treeview-2/treeview-2b.html Comments: - The automatic posinset/setsize is not reported in Chrome. I’ve filed an issue for this.
Received on Monday, 15 May 2017 20:25:58 UTC