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

<featurecaption>'s Content model, Content attributes, and Contexts to be used #203

Closed
Malvoz opened this issue Aug 12, 2021 · 0 comments · Fixed by #207
Closed

<featurecaption>'s Content model, Content attributes, and Contexts to be used #203

Malvoz opened this issue Aug 12, 2021 · 0 comments · Fixed by #207
Assignees

Comments

@Malvoz
Copy link
Member

Malvoz commented Aug 12, 2021

I believe <featurecaption>'s Content model should be the same as HTML <title> (Text) and not <figcaption> (Flow content). This is mostly to align with the title element because I think we'll want featurecaptions to behave similar to title elements (see polyfill issue on native tooltips) so that we can have tooltips on hover (and focus, as some browsers are working on) which is important such that featurecaptions are accessible to visual users as well as non-visual users using ATs.

The Contexts in which this element can be used should be "As a child of a feature element containing no other featurecaption elements".

Content attributes may as well be Global attributes (same as for <title>).

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

Successfully merging a pull request may close this issue.

1 participant