-
Notifications
You must be signed in to change notification settings - Fork 27
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
Remaining elements to revise mapping #373
Comments
Proposed Deep Dive for June 30 |
From today's deep dive: area no href - generic bdi/bdo - generic create a new issue to merge caption, legend, and label as they all do the same thing at a high level - identify content that names another element while |
Other no corresponding role elements, such as iframe, audio, video, etc. likely need some sort of role for implementors, but not for authors, if not one for both. but those would also need their own issues (which may already exist in ARIA). This is specifically for accName purposes to help determine what elements can be named. To help, HTML AAM could also indicate on a per-element basis which elements are namable vs not in the mapping tables. This goes along with other updates that need to be done to the accName section to simplify/clarify that section of the spec. |
Per discussion `<address>` in #373, WG had no objections to mapping the element to the `group` role.
related to #373 i, u, b, small map to generic. Comments referring to the elements being exposed by their platform specific text styles remain in comments. bdi/bdo map to generic. Reference writing-mode properties in comments for ia2/atk `data` and `a no href` map to generic as decided. also: simplifies br element mapping table
related to #373 i, u, b, small map to generic. Comments referring to the elements being exposed by their platform specific text styles remain in comments. bdi/bdo map to generic. Reference writing-mode properties in comments for ia2/atk `data` and `a no href` map to generic as decided. also: simplifies br element mapping table
* Revise address element to map to role=group * update changelog to ref date merged. Per discussion `<address>` in #373, WG had no objections to mapping the element to the `group` role.
Update pre element to generic role according to the HTML-AAM spec[1] and the discussion[2]. Therefore, the pre role was deprecated because it is no longer used. [1]: https://w3c.github.io/html-aam/#html-element-role-mappings [2]: w3c/html-aam#373 Low-Coverage-Reason: Renaming changes only. Bug: None Change-Id: I7eaca4a966de762614751850787e1bcd154c8798 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4776721 Reviewed-by: Camille Lamy <[email protected]> Commit-Queue: Hunseop Jeong <[email protected]> Reviewed-by: David Tseng <[email protected]> Reviewed-by: Aaron Leventhal <[email protected]> Cr-Commit-Position: refs/heads/main@{#1194019}
Closing #229, #183 and #346 in favor of this new issue to simplify.
The following elements should map to
generic
, but we will either need a call out here, or in CORE AAM how AT should treat an 'inline' vs a 'block'/other display typegeneric
(if not doing something with w3c/aria#996).area
nohref
b
i
data
samp
kbd
pre
q
s
small
u
var
(or maybe this is alsorole=code
? )the following need to be changed to 'no corresponding role' until their mappings can be finalized - covered in #376
dd
dt
questions on the following
bdi
/bdo
(change togeneric
or leave as a 'no corresponding role'?)cite
(change togeneric
or leave as a 'no corresponding role'?)abbr
(change togeneric
or leave as a 'no corresponding role'?)address
(change togeneric
or map togroup
?)figcaption
still map tocaption
even though it won't provide thefigure
a name anymore? (i think it might be ok, but want others opinions)label
, this stay as no corresponding role? We aren't moving forward with alabel
role, are we? Could this actually be another instance ofcaption
? is this ageneric
if not?legend
same as above?The text was updated successfully, but these errors were encountered: