<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>27391</bug_id>
          
          <creation_ts>2014-11-21 14:22:30 +0000</creation_ts>
          <short_desc>Corrections for ATK</short_desc>
          <delta_ts>2018-05-03 21:19:35 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>ARIA</product>
          <component>HTML AAM</component>
          <version>1.1</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Joanmarie Diggs">jdiggs</reporter>
          <assigned_to name="steve faulkner">faulkner.steve</assigned_to>
          <cc>jason</cc>
    
    <cc>jdiggs</cc>
    
    <cc>surkov.alexander</cc>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>115291</commentid>
    <comment_count>0</comment_count>
    <who name="Joanmarie Diggs">jdiggs</who>
    <bug_when>2014-11-21 14:22:30 +0000</bug_when>
    <thetext>I&apos;m going to do these in multiple passes because some I need to give thought to. In the meantime, here are some easy ones:

* audio: ATK_ROLE_AUDIO
* blockquote: ATK_ROLE_BLOCK_QUOTE
* dd: ATK_ROLE_DESCRIPTION_VALUE
* dl: ATK_ROLE_DESCRIPTION_LIST
* dt: ATK_ROLE_DESCRIPTION_TERM
* pre: ATK_ROLE_SECTION
* tr: ATK_ROLE_TABLE_ROW
* video: ATK_ROLE_VIDEO

Some of the input types are going to need corrections (and possibly new API in ATK), but I&apos;m pretty sure about:
* input (file upload): ATK_ROLE_BUTTON &lt;-- probably for IA2 as well(?)

For one thing, it&apos;s normally a button, right? For another, as the new STATIC role docs say, &quot;ATK_ROLE_STATIC should not be applied to widgets which are traditionally interactive....&quot; So if it&apos;s not a button, it probably still isn&apos;t STATIC and we need to come up with something else.

Also, this might be worth a note:
* span - *almost always* not mapped. But if there is a need to expose it, e.g. &lt;span onclick=&quot;foo()&quot;&gt;clickable&lt;/span&gt;, then it should be ATK_ROLE_STATIC.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>115295</commentid>
    <comment_count>1</comment_count>
    <who name="steve faulkner">faulkner.steve</who>
    <bug_when>2014-11-21 14:59:51 +0000</bug_when>
    <thetext>Have updated

* audio: ATK_ROLE_AUDIO
* blockquote: ATK_ROLE_BLOCK_QUOTE
* dd: ATK_ROLE_DESCRIPTION_VALUE
* dl: ATK_ROLE_DESCRIPTION_LIST
* dt: ATK_ROLE_DESCRIPTION_TERM
* pre: ATK_ROLE_SECTION
* tr: ATK_ROLE_TABLE_ROW
* video: ATK_ROLE_VIDEO

commit https://github.com/w3c/aria/commit/73d820d9a590a884e09f5693462136658a1ee181

still need to review:

some of the input types are going to need corrections (and possibly new API in ATK), but I&apos;m pretty sure about:
* input (file upload): ATK_ROLE_BUTTON &lt;-- probably for IA2 as well(?)

For one thing, it&apos;s normally a button, right? For another, as the new STATIC role docs say, &quot;ATK_ROLE_STATIC should not be applied to widgets which are traditionally interactive....&quot; So if it&apos;s not a button, it probably still isn&apos;t STATIC and we need to come up with something else.

Also, this might be worth a note:
* span - *almost always* not mapped. But if there is a need to expose it, e.g. &lt;span onclick=&quot;foo()&quot;&gt;clickable&lt;/span&gt;, then it should be ATK_ROLE_STATIC.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>115358</commentid>
    <comment_count>2</comment_count>
    <who name="Joanmarie Diggs">jdiggs</who>
    <bug_when>2014-11-22 23:20:28 +0000</bug_when>
    <thetext>(In reply to Joanmarie Diggs from comment #0)

&gt; Some of the input types are going to need corrections (and possibly new API
&gt; in ATK), but I&apos;m pretty sure about:
&gt; * input (file upload): ATK_ROLE_BUTTON &lt;-- probably for IA2 as well(?)
&gt; 
&gt; For one thing, it&apos;s normally a button, right? For another, as the new STATIC
&gt; role docs say, &quot;ATK_ROLE_STATIC should not be applied to widgets which are
&gt; traditionally interactive....&quot; So if it&apos;s not a button, it probably still
&gt; isn&apos;t STATIC and we need to come up with something else.

Interesting: In Firefox, the widget is a button. In Chrome, the widget is a button. In Safari and Epiphany, however, the widget is a text input field. Bah.

I guess the spec text probably needs to say that the mapping is conditional based on the user agent&apos;s native support for that element.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>118570</commentid>
    <comment_count>3</comment_count>
    <who name="Joanmarie Diggs">jdiggs</who>
    <bug_when>2015-03-12 20:39:50 +0000</bug_when>
    <thetext>(In reply to Joanmarie Diggs from comment #2)
&gt; (In reply to Joanmarie Diggs from comment #0)
&gt; 
&gt; &gt; Some of the input types are going to need corrections (and possibly new API
&gt; &gt; in ATK), but I&apos;m pretty sure about:
&gt; &gt; * input (file upload): ATK_ROLE_BUTTON &lt;-- probably for IA2 as well(?)
&gt; &gt; 
&gt; &gt; For one thing, it&apos;s normally a button, right? For another, as the new STATIC
&gt; &gt; role docs say, &quot;ATK_ROLE_STATIC should not be applied to widgets which are
&gt; &gt; traditionally interactive....&quot; So if it&apos;s not a button, it probably still
&gt; &gt; isn&apos;t STATIC and we need to come up with something else.
&gt; 
&gt; Interesting: In Firefox, the widget is a button. In Chrome, the widget is a
&gt; button. In Safari and Epiphany, however, the widget is a text input field.
&gt; Bah.
&gt; 
&gt; I guess the spec text probably needs to say that the mapping is conditional
&gt; based on the user agent&apos;s native support for that element.

I stand by my above statement (conditional based on user agent&apos;s native support...). Having said that, it&apos;s now a button in WebKit!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>119890</commentid>
    <comment_count>4</comment_count>
    <who name="Joanmarie Diggs">jdiggs</who>
    <bug_when>2015-04-24 17:35:53 +0000</bug_when>
    <thetext>(In reply to Joanmarie Diggs from comment #0)

&gt; Also, this might be worth a note:
&gt; * span - *almost always* not mapped. But if there is a need to expose it,
&gt; e.g. &lt;span onclick=&quot;foo()&quot;&gt;clickable&lt;/span&gt;, then it should be
&gt; ATK_ROLE_STATIC.

Ping. The above is accurate, and not yet reflected here:
https://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-span

As for IA2, they are in a similar boat but I believe their mapping is for system text or text frame or whatever.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120278</commentid>
    <comment_count>5</comment_count>
    <who name="Joanmarie Diggs">jdiggs</who>
    <bug_when>2015-05-12 21:31:57 +0000</bug_when>
    <thetext>Alex Surkov just pointed out that address is mapped to ATK_ROLE_PARAGRAPH.

As a general rule, only paragraph elements should be mapped to ROLE_PARAGRAPH. Otherwise Orca&apos;s structural navigation by paragraph will jump to non-paragraphs, which is probably something Orca users are not expecting.

Mapping it to ATK_ROLE_SECTION seems like a better choice to me.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120962</commentid>
    <comment_count>6</comment_count>
    <who name="steve faulkner">faulkner.steve</who>
    <bug_when>2015-06-13 10:02:42 +0000</bug_when>
    <thetext>(In reply to Joanmarie Diggs from comment #4)
&gt; (In reply to Joanmarie Diggs from comment #0)
&gt; 
&gt; &gt; Also, this might be worth a note:
&gt; &gt; * span - *almost always* not mapped. But if there is a need to expose it,
&gt; &gt; e.g. &lt;span onclick=&quot;foo()&quot;&gt;clickable&lt;/span&gt;, then it should be
&gt; &gt; ATK_ROLE_STATIC.
&gt; 
&gt; Ping. The above is accurate, and not yet reflected here:
&gt; https://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-span
&gt; 
&gt; As for IA2, they are in a similar boat but I believe their mapping is for
&gt; system text or text frame or whatever.

ok, so if event handler attached to element = ATK_ROLE_STATIC?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>120999</commentid>
    <comment_count>7</comment_count>
    <who name="alexander surkov">surkov.alexander</who>
    <bug_when>2015-06-15 15:13:40 +0000</bug_when>
    <thetext>(In reply to Joanmarie Diggs from comment #5)
&gt; Alex Surkov just pointed out that address is mapped to ATK_ROLE_PARAGRAPH.
&gt; 
&gt; Mapping it to ATK_ROLE_SECTION seems like a better choice to me.

iirc we agreed to map it into ATK_ROLE_SECTION, and I tweaked Firefox implementation and the spec to fit it.

(In reply to steve faulkner from comment #6)

&gt; ok, so if event handler attached to element = ATK_ROLE_STATIC?

it depends on element display, if it&apos;s block then section, static for inlines</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>129196</commentid>
    <comment_count>8</comment_count>
    <who name="James Nurthen">w3cbugzilla</who>
    <bug_when>2018-05-03 21:19:35 +0000</bug_when>
    <thetext>HTML AAM is no longer an ARIA Deliverable. If you wish to pursue this issue please file at https://github.com/w3c/html-aam/issues</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>