Confirmed users
1,396
edits
Accessibility/ARIAConflictsWithNativeMarkup: Difference between revisions
Jump to navigation
Jump to search
Accessibility/ARIAConflictsWithNativeMarkup (view source)
Revision as of 09:46, 1 September 2009
, 1 September 2009→Compatible roles
| Line 8: | Line 8: | ||
ARIA usage within native markup can be result of two conflict types. This is either ARIA overwhelms mapping rules of native markup or ARIA is mapped upon native markup. It depends on compatibility of ARIA role and role from native markup. Thus if roles are consistent or no ARIA role was used then ARIA is mapped upon native markup. Otherwise ARIA suppress any rules coming from native markup. | ARIA usage within native markup can be result of two conflict types. This is either ARIA overwhelms mapping rules of native markup or ARIA is mapped upon native markup. It depends on compatibility of ARIA role and role from native markup. Thus if roles are consistent or no ARIA role was used then ARIA is mapped upon native markup. Otherwise ARIA suppress any rules coming from native markup. | ||
== | ==ARIA applied on top of native markup== | ||
In the case of compatible roles or if ARIA role is not presented then user agent creates accessible for native markup element as usually with one exception. If ARIA markup and native markup are mapped to the same accessibility API properties then ARIA wins. Otherwise implementation coming from native markup accessible takes a place. For example, | In the case of compatible roles or if ARIA role is not presented then user agent creates accessible for native markup element as usually with one exception. If ARIA markup and native markup are mapped to the same accessibility API properties then ARIA wins. Otherwise implementation coming from native markup accessible takes a place. For example, | ||