Community
Participate
Working Groups
The ARIA "role" attribute is special in that it can change the semantics of an HTML tag for accessibility purposes. So specifying a "role" on a tag filters the remaining "aria-*" attributes that can also be set on the tag. It would be really cool and useful if this relationship was encoded in the HTML content assist. For example, if a <div role="tree"> then the <div> can also support aria-activedescendant, aria-expanded, aria-multiselectable, and aria-required. There's one more part to this relationship that would be really useful to encode: some ARIA roles require that certain other attributes are included, for example role="checkbox" requires aria-checked. Consider implementing this also.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html
This is even more relevant now that authoring tools are being called out in section 508: http://www-03.ibm.com/able/guidelines/ci162/accessibility_checklist.html#authoring
This is similar to Bug 516619 and can probably use the same code with different data.
See also bug 484255 (similar, but not the same).
