- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 11 Jan 2023 10:08:34 +0000
- To: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
- Message-ID: <PR3PR09MB534786586EA2A4A6970A8411B9FC9@PR3PR09MB5347.eurprd09.prod.outlook.com>
Hi everyone, I’ll try and keep the discussion thread separate from the CFC thread. Melanie wrote: > why modify "lists" with "bulleted or numbered"? If you are giving an exception to bulleted or numbered lists, removing the bullets doesn't change the impact on the user. Why not just "lists"? We could draw a circle in a Venn diagram of everything that could be a list (in HTML terms) including navigation, images of a product, cards, description lists, as well as simple ordered/unordered lists. That would be a large circle. Then a second, smaller circle of things which look like bulleted & numbered lists. The overlap would be the HTML ordered/unordered lists, and the non-overlap would be paragraphs (etc) presented with bullets/numbers. This exception is intended to cover things which are (or can be) re-flowing text because it is infeasible to include those. We are looking for something that at least correlates with main content area style lists. If we just say “lists”, that covers things we don’t intend to cover. > With exceptions for so many things … it might be easier to flip it all and say what IS in scope. It is getting long, but I think flipping it would be longer. E.g. * Button * Text input * File input * Checkbox * Radio button * Custom select drop-downs * Accordion controls * Slider thumbs (depending on whether you can tap the slider bar) * Spin buttons * Switches * Tabs Some of those we could group as ‘buttons’, but I’ve probably also missed some from a quick scan of HTML & ARIA controls. I think we’re better off saying “targets” with some known exceptions, rather than the other way around. Kind regards, -Alastair -- @alastc / www.nomensa.com<http://www.nomensa.com>
Received on Wednesday, 11 January 2023 10:09:13 UTC