View Single Post
Old 06-07-2025, 10:29 AM   #9
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 9,070
Karma: 6361556
Join Date: Nov 2009
Device: many
The aria spec is truly horribly written, Its main focus seems to to make web user interfaces, forms, and user input controls interpretable. But outside of that why define innate roles for almost every tag but then say do not use them. The rules for applying those roles are just too arcane to be useful. And why define an innate role for a table or table row, etc at all. A typical spec designed and written by a committee without any thought for practical use.

So given all of that, and given an epub is not a web user interface in itself and is instead a publishing mechanism, I think Doitsu is rght here and we should collect a much shorter list of the most frequently used aria roles.

What I think is very strange given the "do not overspecify or duplicate" guidance all throughout the aria spec, is why there is a huge overlap between epub:type and aria digital publishing roles. Seems quite strange. Are both needed? If so that breaks the do not duplicate guidance in the aria spec.

So for those reading this, a shorter list of the aria-roles you actually use would prove to be useful.

Please attach a list in a response in this thread and I will collect and collate them to aid the design of the clips ui.
KevinH is offline   Reply With Quote