Re: Enabling the ARIA 1.2 IDL Interface in browsers

To add one more bit of context: what's implemented right now is ARIA
reflection - making it possible to set and retrieve ARIA from JavaScript. A
later phase of AOM will expose getting the computed role and other computed
properties from a node, and then you'd expect to get the implied ARIA role
from an element like an <h1>.

On Wed, Apr 1, 2020 at 9:40 AM Gunderson, Jon R <jongund@illinois.edu>
wrote:

> Alice,
>
>
>
> Thank you for the clarifications, that helps.
>
>
>
> Jon
>
>
>
>
>
> *From:* Alice Boxhall <aboxhall@google.com>
> *Sent:* Monday, March 30, 2020 7:07 PM
> *To:* Gunderson, Jon R <jongund@illinois.edu>
> *Cc:* Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>; nurthen@adobe.com;
> public-aria@w3.org
> *Subject:* Re: Enabling the ARIA 1.2 IDL Interface in browsers
>
>
>
>
>
>
>
> On Tue, Mar 31, 2020 at 12:36 AM Gunderson, Jon R <jongund@illinois.edu>
> wrote:
>
> Alice,
>
>
>
> Thank you for the response and you work on the AOM, I have a few questions.
>
>
>
> I created a test page to do some testing on my own and I enabled
> experimental  features as described by Carolyn using Chrome Version
> 83.0.4099.0 (Official Build) canary (64-bit):
>
> https://raw.githack.com/illinois-dres-aitg/aom-testing/master/index.html
>
>
>
> I don’t seem to be getting the default role for the H1 element or the
> level, but do for headings created with divs.
>
>
>
> We don't expose any computed properties - so no default roles, only
> explicitly set ARIA roles.
>
>
>
> I am also curious about the ariaLabel interface, should it be giving the
> computed accessible name
>
>
>
> Similarly, we're not exposing computed labels - only explicitly set ARIA
> labels.
>
>
>
> For example:
>
>
>
> <button aria-label="I am an ARIA label" id="button1">I am text
> content</button>
>
>
>
> console.log(button1.ariaLabel);  // logs "I am an ARIA label"
>
>
>
> <button id="button1">I am text content</button>
>
>
>
> console.log(button2.ariaLabel);  // logs null - no aria-label set, does
> not compute label from text content
>
>
>
>
>
> Jon
>
>
>
>
>
>
>
> *From:* Alice Boxhall <aboxhall@google.com>
> *Sent:* Sunday, March 29, 2020 10:25 PM
> *To:* Gunderson, Jon R <jongund@illinois.edu>
> *Cc:* Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>; nurthen@adobe.com;
> public-aria@w3.org
> *Subject:* Re: Enabling the ARIA 1.2 IDL Interface in browsers
>
>
>
> Once Chrome 81 is promoted to stable (estimated April 2
> <https://chromiumdash.appspot.com/schedule>), the flag will no longer be
> necessary to access ARIA IDL properties (other than IDREF/IDREFS
> properties) in Chrome.
>
>
>
> On Mon, Mar 30, 2020 at 12:58 PM Gunderson, Jon R <jongund@illinois.edu>
> wrote:
>
> Thanks Carolyn,
>
>
>
> I was able to enable the AOM on Chrome.
>
>
>
> I am curious if default roles and values of HTML elements are suppose to
> be reflected in the AOM, or only roles and properties that have been
> explicitly set.
>
>
>
> No, no computed properties (including "default" roles) are exposed. This
> is straightforward IDL reflection.
>
>
>
> Jon
>
>
>
> *From:* Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
> *Sent:* Friday, March 27, 2020 10:31 PM
> *To:* nurthen@adobe.com
> *Cc:* Gunderson, Jon R <jongund@illinois.edu>; public-aria@w3.org
> *Subject:* RE: Enabling the ARIA 1.2 IDL Interface in browsers
>
>
>
> Hi, Jon.
>
>
>
> In case it's helpful, there's an IDL Button example in the APG
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_aria-2Dpractices_examples_button_button-5Fidl.html&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=9I76s_DQeMyePDM1NLeRmzQO75RtgjJ9Clf1LQyt7-I&m=CUEWT1G9KSuIIW29QTAcAf4nJccO4uGowZoCQfd1yZY&s=D03aQlTpUZt7FMZXFQPYA0oUXc9DjRhO-2PjQ2plJsg&e=>
> .
>
> Here's what I had to do to enable browsers so I could test
> *attribute reflection*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_aria-2Dpractices_pull_1161-23issuecomment-2D527296049&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=9I76s_DQeMyePDM1NLeRmzQO75RtgjJ9Clf1LQyt7-I&m=CUEWT1G9KSuIIW29QTAcAf4nJccO4uGowZoCQfd1yZY&s=xwEN9x1Bwnf5-iZNe8Sp9nRgcpUNcoT41JCaB51Ad1A&e=> for
> that example (info from Sept 2019).
>
> Also, this conversation with Mallory and Alice about *element reflection*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_aria-2Dpractices_pull_1045-23discussion-5Fr320948178&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=9I76s_DQeMyePDM1NLeRmzQO75RtgjJ9Clf1LQyt7-I&m=CUEWT1G9KSuIIW29QTAcAf4nJccO4uGowZoCQfd1yZY&s=6RlGkTZdwUn8vx9iouPBmHW7iVfVDwkjV97wtqIw9Pk&e=>
> may be helpful.
>
> I don't know if element reflection has been fully implemented in any
> browser yet, but maybe?
>
>
>
> Car
>
>
>
> ----- Original message -----
> From: James Nurthen <nurthen@adobe.com>
> To: "Gunderson, Jon R" <jongund@illinois.edu>, ARIA Working Group <
> public-aria@w3.org>
> Cc:
> Subject: [EXTERNAL] Re: Enabling the ARIA 1.2 IDL Interface in browsers
> Date: Thu, Mar 26, 2020 12:54 PM
>
>
>
> https://github.com/WICG/aom/blob/gh-pages/explainer.md#reflecting-aria-attributes
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_WICG_aom_blob_gh-2Dpages_explainer.md-23reflecting-2Daria-2Dattributes&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=9I76s_DQeMyePDM1NLeRmzQO75RtgjJ9Clf1LQyt7-I&m=CUEWT1G9KSuIIW29QTAcAf4nJccO4uGowZoCQfd1yZY&s=1T8abQ9rphHy3yPsQ3LflPQsKWwRzAnDZQRKN6TryZ0&e=>
> states
>
>
>
> This is shipping in Safari, and implemented behind a flag (
> enable-experimental-web-platform-features) in Chrome.
>
>
>
> Don’t know how up to date this is.
>
>
>
> *James Nurthen*  |  Accessibility Engineer  |  Adobe  |  p. 415.832.2734
> <(415)%20832-2734>  |  c. 415.987.1918 <(415)%20987-1918>  |
> nurthen@adobe.com
>
>
>
>
>
>
>
> *From: *Gunderson, Jon R <jongund@illinois.edu>
> *Date: *Thursday, March 26, 2020 at 9:51 AM
> *To: *ARIA Working Group <public-aria@w3.org>
> *Subject: *Enabling the ARIA 1.2 IDL Interface in browsers
>
> Can someone point me to where you can learn how to enable browsers to turn
> on their implementation of the ARIA 1.2 IDL interface:
>
> https://w3c.github.io/aria/#idl-interface
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_aria_-23idl-2Dinterface&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=9I76s_DQeMyePDM1NLeRmzQO75RtgjJ9Clf1LQyt7-I&m=CUEWT1G9KSuIIW29QTAcAf4nJccO4uGowZoCQfd1yZY&s=G2tD32IaUazu5oTX4KomoZydj-UhJVopHYDniPDbawA&e=>
>
>
>
> Jon
>
>
>
>
>
> Jon Gunderson, Ph.D., CPWA
>
> Coordinator of Accessible IT Group
>
> University of Illinois at Urbana/Champaign
>
> 1207 S. Oak Street
>
> Champaign, IL 61820
>
>
>
> www: https://go.illinois.edu/jongund
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__go.illinois.edu_jongund&d=DwMFaQ&c=OCIEmEwdEq_aNlsP4fF3gFqSN-E3mlr2t9JcDdfOZag&r=9I76s_DQeMyePDM1NLeRmzQO75RtgjJ9Clf1LQyt7-I&m=CUEWT1G9KSuIIW29QTAcAf4nJccO4uGowZoCQfd1yZY&s=7dVn6pNyYULiUxToXbLrGe-vnJ86AQt435TVo--4MZw&e=>
>
>
>
>
>
>
>
>