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

allow doc-* link roles on area with href #101

Closed
rdeltour opened this issue Mar 14, 2018 · 4 comments
Closed

allow doc-* link roles on area with href #101

rdeltour opened this issue Mar 14, 2018 · 4 comments
Labels

Comments

@rdeltour
Copy link
Member

consider allowing the following roles on area with href:

@scottaohara
Copy link
Member

@rdeltour it looks like this was already merged into the spec, but in reviewing it again today I have a question about doc-noteref.

Should that role be allowed on a <a href> or is it meant to not act as a link? The example in the ARIA DPub spec uses it on an <a> without an href, which either seems like an oversight with the example in the DPub spec, or I need to allow it on <a> and not <a href> here.

Thanks

@rdeltour
Copy link
Member Author

rdeltour commented Feb 4, 2020

Should that role be allowed on a <a href> or is it meant to not act as a link?

As far as I'm were it's clearly meant to be used as links (and it subclasses the link role), so yes I think it's an oversight in DPUB ARIA’s example 30.
Typically the noteref would be used both as a link to the actual note, plus also as an anchor for a backlink, but I don't think I've ever seen it used as an anchor only.

Pinging @mattgarrish (who's the DPUB ARIA editor and master of all EPUB/DPUB specs 😊) for confirmation.

@mattgarrish
Copy link
Member

so yes I think it's an oversight in DPUB ARIA’s example 30.

Yes, that's definitely a mistake in the example. An inactive note reference is somewhat useless; it's not something I'd expect to see done in the wild. I've opened an issue in the dpub aria tracker.

@scottaohara
Copy link
Member

thanks @mattgarrish

Then looks like this issue is good to close, because all those roles are in the Spec now.

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

No branches or pull requests

3 participants