- From: bryan rasmussen <rasmussen.bryan@gmail.com>
- Date: Fri, 25 Oct 2024 21:21:27 +0200
- To: Taliesin Smith <talilief@gmail.com>
- Cc: WAI IG <w3c-wai-ig@w3.org>
- Message-ID: <CAHKsR69yuk7rCzT0mwLKH3EXmBmka6gQ3jz=mQvLuxcm4_qf6g@mail.gmail.com>
according to the rules for Providing accessible names and descriptions https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/#naming_role_guidance heading is Required *Only If* Content Insufficient and listitem do not name, however you may name a list. Cheers, Bryan Rasmussen On Fri, Oct 25, 2024 at 8:37 PM Taliesin Smith <talilief@gmail.com> wrote: > Dear Interest Group Members, > > I have always thought of an "accessible name" as required content for an > interactive thing like a button or a checkbox or slider, etc. > > Do text elements like paragraphs, headings, list items have accessible > names, that is if there is no added aria-label attribute. > > Developers on our team are abstracting / simplifying our current API that > builds accessibility into our interactive simulations. The plan is to make > the API very simple, like everything gets an accessible name. This seemed a > little odd to me, as I have never thought of a paragraph as having an > accessible name. > > Do text nodes have accessible names by default? > > Taliesin > > > ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~ > Taliesin L. Smith > talilief@gmail.com > taliesin.smith@colorado.edu > > Inclusive Design Research Specialist > PhET Interactive Simulations > http://phet.colorado.edu/ > Department of Physics > University of Colorado, Boulder > > > > > > >
Received on Friday, 25 October 2024 19:21:42 UTC