Where is accessible name and descriptions defined? about accname HOT 9 CLOSED

I probably need more coffee, but I'm not sure what the question is. Are you saying there is something wrong with the redirects? Or is your question about the mappings? In the meantime....

The AccName spec defines the platform-independent name and description calculation. To me, that is the answer to "Where is accessible name and descriptions defined?"

What is "documented in the Core Accessibility API Mappings specification" are the "accessibility API mappings." (emphasis added)

In other words, once you calculate the platform-independent name and description as per the AccName spec, you need to know how to expose ("map") the results via platform accessibility APIs such at ATK, IAccessible2, UIAutomation, or nsAccessibility (aka AXAPI). Core AAM tells you how to do that platform-specific exposure.

Please let me know what information or changes you seek. Sorry for being dense and thanks for the report!

from accname.

OK now I found this

https://w3c.github.io/accname/#mapping_additional_nd_name

User agents MUST compute an accessible name using the rules outlined below in the section titled Text Alternative Computation.

so the algorithm is the one at

https://w3c.github.io/accname/#mapping_additional_nd_te

I filed this because I simply couldn't find what I was looking for and instead ended up going in circles.

from accname.

So I think there are several things that could be improved.

• The links should be updated so they point to the new locations.
• The links could go to a specific section.
• The section title shouldn't be "Text Alternative Computation" if it's also used for accessible name computation; maybe "Text Alternative and Accessible Name Computation" (or something)
• The paragraphs that link to the other spec could clarify what the reader is expected to find in the spec they are currently reading vs what's in the other spec.

from accname.

@zcorpan agreed re the language confusion. If the section title were "Name and Description Computation" rather than "Text Alternative Computation," would that be more clear to you?

from accname.

Yes.

from accname.

or "Accessible Name and Description Computation"

from accname.

So I think there are several things that could be improved.

• The links should be updated so they point to the new locations.

Should be done (in the non-TR copies).

• The links could go to a specific section.

In AccName, the text already has links to the specific sections: "See the mapping table entries for aria-label, aria-labelledby, and aria-describedby." Unfortunately, those links are broken due to a tooling issue. See w3c/core-aam#5. When that tooling issue is fixed the links in the paragraph will take you to the specific mappings.

• The section title shouldn't be "Text Alternative Computation" if it's also used for accessible name computation; maybe "Text Alternative and Accessible Name Computation" (or something)

Done. Also updated references to it in ARIA and Core AAM (again the non-TR copies). I still need to update some ARIA links to not point to TR (where the name isn't updated). But that's not an AccName spec issue.

• The paragraphs that link to the other spec could clarify what the reader is expected to find in the spec they are currently reading vs what's in the other spec.

Perhaps you could propose an alternative wording?

Thanks again, and please let me know if I missed something else regarding your issue.

from accname.

Thank you! I think those fixes are enough to close this issue.

from accname.

Thank you! I think those fixes are enough to close this issue.

Awesome. Thanks again for the report. Please re-open if you find something else related to this which we need to fix.

from accname.