There are many elements that do/will map to generic per ARIA 1.2 / Core AAM / HTML AAM updates.
Rather than call out these rules multiple times throughout our table, we should create a section specifically for rules that should be taken into account, and then we can make reference to those in the table.
for instance, these elements must not be named (aria-label / aria-labelledby).
If set to role=none, they must not have a tabindex or onclick, other things that would make them interactive.
they must not have aria-roledescription.
The goal here should not be to repeat rules from ARIA, obviously, but we need to make sure that anything that squarely falls into our court is called out in this manner.
There are many elements that do/will map to
genericper ARIA 1.2 / Core AAM / HTML AAM updates.Rather than call out these rules multiple times throughout our table, we should create a section specifically for rules that should be taken into account, and then we can make reference to those in the table.
for instance, these elements must not be named (aria-label / aria-labelledby).
If set to role=none, they must not have a
tabindexoronclick, other things that would make them interactive.they must not have
aria-roledescription.The goal here should not be to repeat rules from ARIA, obviously, but we need to make sure that anything that squarely falls into our court is called out in this manner.