Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML-AAM: UIA mapping for <legend> #172

Closed
cyns opened this issue Jan 12, 2016 · 8 comments
Closed

HTML-AAM: UIA mapping for <legend> #172

cyns opened this issue Jan 12, 2016 · 8 comments
Assignees

Comments

@cyns
Copy link
Contributor

cyns commented Jan 12, 2016

text
LabeledBy of parent fieldset points to this element

@cyns cyns added the AAM label Jan 12, 2016
@cyns cyns self-assigned this Jan 12, 2016
@cyns
Copy link
Contributor Author

cyns commented Feb 26, 2016

add participates in name calculation

@jasonkiss
Copy link
Contributor

There is an explicit entry for fieldset and legend in the acc name and description section of the document. Is it necessary to include a note about legend participating in the name calculation? I don't think so, but if it is, wouldn't we want to be consistent and include such note for the other APIs, and for similar elements, e.g summary, caption?

@asurkov
Copy link
Contributor

asurkov commented Mar 23, 2016

I think I'd rather had name computation and relations under each element.

@jasonkiss
Copy link
Contributor

@cyns, @asurkov

We don't document that many relations, so I'm happy with those being included on an element by element basis. But so many elements participate in their name calculation that I think it would get very repetitive to mention that for each element.

@asurkov Do you have particular concerns with the name computations being in their own section and separate from the individual element mappings?

jasonkiss added a commit that referenced this issue Jun 8, 2016
Proposing using the “Notes” preface to the role mapping table to
address issues #177, #159, and possibly #172.
@asurkov
Copy link
Contributor

asurkov commented Jun 8, 2016

@jasonkiss I think I'd rather had the element oriented structure as it's supposedly easier for implementers. That would require drastic the spec structure changes though. I can live with the current structure, if the majority find it optimal, but I might missed your question.

@jasonkiss
Copy link
Contributor

@asurkov You answered my question, thanks. Yes, integrating the name computation with each element's other mappings is a big change and I don't see it happening any time soon, given the increasing number of AAM specs using the current common structure.

@cyns @asurkov I'm going to propose that instead of adding "participates in name calculation" or similar to every element that participates in its own or another element's name calculation, we include a note in the "Notes" section preceding the mapping table. This note just reminds implementers to check the Accessible Name and Description Calculation section for how elements' names and descriptions are calculated, where applicable. See http://rawgit.com/w3c/aria/notes-to-html-role-mappings/html-aam/html-aam.html#html-element-role-mappings.

@asurkov
Copy link
Contributor

asurkov commented Aug 10, 2016

this sounds good

@jasonkiss
Copy link
Contributor

Addressed as described above in merged PR #424. Closing.

pkra pushed a commit to pkra/aria that referenced this issue May 20, 2024
pkra pushed a commit that referenced this issue May 20, 2024
fix: missing opening code element
pkra pushed a commit that referenced this issue May 20, 2024
Add current UIA mappings for meter

thank you @melanierichards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants