closes issue#325

This update allows authors to specify thelink orbutton roles on anarea with nohref attribute.

Any more complex widget, particularly any that would need to convey a visual state or updated styling, would be far more practical for authors to create another accessible control instead. As these elements do not allow nested content (and even CSS pseudo element content appears in a different location than where thearea's coordinates place it, no container-type role would make sense here either.

Ideally, authors would be using atabindex on these elements when specifying a role.... but as there could be situations where a role needs to be conveyed, but it is not necessary to make the particular element keyboard accessible (alternate mechanism available), the requirement for including atabindex was left off this PR. Additionally, we make no such requirements for other widget roles, so on second thought it seemed out of place to require one for this role.

Need at least two checkers to accept this change before we can merge.

• html validator
• ibm equal access accessibility checker
• axe-core
• arc toolkit (PR filed)

Preview |Diff