Open chiaradm95 opened 1 year ago
The relevant spec is html-aria which defines which roles are allowed on HTML elements. For the specifics for the aside element see https://w3c.github.io/html-aria/#el-aside.
There's currently an open issue to review the aside element, see https://github.com/w3c/html-aria/issues/411
Thank you very much, I wasn't aware of this spec. I will look at it in detail.
Chiara De Martin
[Logo di Fondazione LIA]
Corso di Porta Romana 108, 20122 Milano
www.fondazionelia.orghttp://www.fondazionelia.org/ - www.libriitalianiaccessibili.orghttp://www.libriitalianiaccessibili.org/
[Loghi dei social Facebook, Twitter, Instagram e Twitter] Segui @fondazionelia
Da: Peter Krautzberger @.> Inviato: martedì 28 marzo 2023 17:16 A: w3c/dpub-aria @.> Cc: Chiara De Martin @.>; Author @.> Oggetto: Re: [w3c/dpub-aria] Can we have doc-glossary on
The relevant spec is html-ariahttps://github.com/w3c/html-aria/ which defines which roles are allowed on HTML elements. For he specifics for the aside element see https://w3c.github.io/html-aria/#el-aside.
There's currently an open issue to review the aside element, see w3c/html-aria#411https://github.com/w3c/html-aria/issues/411
— Reply to this email directly, view it on GitHubhttps://github.com/w3c/dpub-aria/issues/53#issuecomment-1487088466, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZLGJI3Z5XCJFPXX6BDCS5TW6L6GDANCNFSM6AAAAAAWKWXZQQ. You are receiving this because you authored the thread.Message ID: @.***>
Network Confidentiality Notice
Il presente messaggio, e ogni eventuale documento a questo allegato, potrebbe contenere informazioni da considerarsi strettamente riservate ad esclusivo utilizzo del destinatario in indirizzo. Chiunque ricevesse questo messaggio per errore o comunque lo leggesse senza esserne legittimato è avvertito che trattenerlo, copiarlo, divulgarlo, distribuirlo a persone diverse dal destinatario è severamente proibito ed è pregato di darne notizia immediatamente al mittente oltre che cancellare il messaggio e i suoi eventuali allegati dal proprio sistema. Ai sensi del Regolamento UE 2016/679, il Titolare del trattamento garantisce la massima riservatezza ed il pieno rispetto degli obblighi previsti dalla normativa nazionale e comunitaria in merito alla protezione dei dati personali.
This message, and any attached file transmitted with it, contains information that may be confidential or privileged for the sole use of the intended recipient. If you are not the intended recipient of this e-mail or read it without entitlement be advised that keeping, copying, disseminating or distributing this message to persons other than the intended recipient is strictly forbidden. You are to notify immediately to the sender and to delete this message and any file attached from your system. In accordance with EU Reg. 2016/679 (GDPR), the Data Controller guarantees the maximum level of confidentiality and full respect of all obligations provided for by the national and the EU legislation currently in force with regard to protection of personal data..
This shows one of the problems of publishing structures being both primary and subordinate. The role was modelled on a glossary being a primary section in the back matter. If you put it on an aside
for a glossary embedded within a section then it's no longer going to be complementary. That's probably not critical since embedded glossaries usually precede the section content, but there's no real advantage to using aside
over section
in terms of how it will be exposed to AT.
That said, if an aside
not scoped to the body or main is going to be generic, anyway, then it doesn't seem harmful to allow doc-glossary on it.
The KB page is not authoritative, as @pkra has already mentioned. There's a link to ARIA in HTML at the bottom, but I'll go back to those element lists and make it clearer to refer to that doc for the most up-to-date list of elements or in case of conflicts.
FWIW, the PR https://github.com/w3c/html-aria/pull/455 is proposing to allow the role on aside elements.
Hi everyone,
as the title suggests, I'm here because I'd need to use
role="doc-glossary"
on the<aside>
tag. However, both EPUBCheck and ACE report errors. ACE reports that "ARIA role doc-glossary is not allowed for given element". As far as I understand,<aside>
has the implicit role "complementary", which is a subclass role of "landmark", which in turn is the superclass indicated for doc-glossary.Also, looking at the Accessible Publishing Knowledge Base by DAISY,
<aside>
is listed among the possible elements doc-glossary is allowed on (http://kb.daisy.org/publishing/docs/html/dpub-aria/doc-glossary.html).As for the content of the
<aside>
, the error occurs both if we have a definition list (<dl>
with<dt>
and<dd>
, possibly withrole="term"
on<dt>
), or if we have a<p>
with<dfn>
to identify the term.In the specific use case, I have an EPUB with boxes (
<aside>
) that contain definitions of words and therefore represent small glossaries, so using doc-glossary would give more semantics.Can anyone help me understand the problem?