Intro at http://www.w3.org/TR/accname-aam-1.1/#intro

Rephrased -

Intro at http://www.w3.org/TR/accname-aam-1.1/#intro is not clear in how
and from where Assistive Technology (AT) gets accessible name /
description. I think explaining the interaction (also differences) between
API, DOM, and Browser with AT will aid in understanding how the process
works for non-technical readers.

I run JAWS but I don’t always know where the information is coming from
when in virtual mode vs document mode. Is it the DOM or API that is passing
on bits and pieces to AT? Consider expanding and including the part [
http://www.w3.org/TR/wai-aria-1.1/#intro_ria_accessibility] across all a11y
specs -- “While it is possible for assistive technologies to access these
properties directly through the Document Object Model [DOM4], the preferred
mechanism is for the user agent to map the states and properties to the
accessibility API of the operating system. See the Core Accessibility API
Mappings 1.1 [CORE-AAM] and the Accessible Name and Description:
Computation and API Mappings 1.1 [ACCNAME-AAM] for details” and the
subsequent image in the intro @ http://www.w3.org/TR/accname-aam-1.1/#intro
 …”


Thanks,

Devarshi