- From: Ms J <ms.jflz.woop@gmail.com>
- Date: Fri, 8 Apr 2022 10:21:44 +0000
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <PAXPR04MB9469A6FC31AE674EA008BA8BAEE99@PAXPR04MB9469.eurprd04.prod.outlook.com>
Hello, Please can you provide some clarity on what counts as an ‘accessible name’. The definition says The accessible name is the name of a ‘user interface element’. https://www.w3.org/TR/accname-1.1/#glossary But then the name computation mentions the name of ‘accessible objects’ and tasks about headings having accessible names: https://www.w3.org/TR/wai-aria-1.1/#namecomputation I mainly just want to make sure I’m using terminology correctly. I appreciate there are other widgets and roles that are not ‘user interface components’ that do support or require an accessible name, such as regions or tabpanels. However, there are some that don’t require them such as a rule of ‘list’ - this isn’t on the list of roles supporting name from content, but wouldn’t generally require an aria-label or anything explicitly defining the accessible name. I associate accessible names with anything I would use the aria-label attribute on. I would not usually refer to an empty heading as having no ‘accessible name’ and would not tend to use an aria-label on one. Some clarity would be greatly appreciated! Thank you Sarah
Received on Friday, 8 April 2022 10:22:00 UTC