Accessibility/ARIAConflictsWithNativeMarkup: Difference between revisions

Jump to navigation Jump to search
Line 28: Line 28:
Here there is conflict since input isn't disabled and therefore its native accessible object shouldn't have disabled state. But since aria-disabled is used then result accessible object should expose disabled state.
Here there is conflict since input isn't disabled and therefore its native accessible object shouldn't have disabled state. But since aria-disabled is used then result accessible object should expose disabled state.


==Incompatible roles==
==ARIA suppresses native markup==


When ARIA role is incompatible with role coming from native markup then user agent should create generic accessible object. However the accesible object should reflect any general rules peculiar to all elements from native markup. For example,
When ARIA role is incompatible with role coming from native markup then user agent should create generic accessible object. However the accesible object should reflect any general rules peculiar to all elements from native markup. For example,
Confirmed users
1,396

edits

Navigation menu