E-mail List Archives
Re: Landmarks
From: Bossley, Peter A.
Date: Jan 14, 2020 7:30PM
- Next message: Barry Hill: "Screen reader and greyed-out submit button"
- Previous message: Bryan Garaventa: "Re: Wanted: Examples for drag-and-drop implementations with pointer alternatives"
- Next message in Thread: Swift, Daniel P.: "Re: multiple navigation landmarks"
- Previous message in Thread: glen walker: "Re: Landmarks"
- View all messages in this Thread
Adding a role to a native element that already inherits that role should not cause double reading. Where I see that double reading issue most often is where a container element nested inside the native role has the additional duplicated role assigned to it. I'm not sure the double specification is really necessary with modern browsers and AT, but if you want to make sure it wouldn't be an issue putting an example together and using an API inspector should be able to show you what the accessibility tree from the browser is actually exposing. I find this useful when I can't figure out, after code/DOM inspection, if a screen reader is misbehaving or if it is the browser.
- Next message: Barry Hill: "Screen reader and greyed-out submit button"
- Previous message: Bryan Garaventa: "Re: Wanted: Examples for drag-and-drop implementations with pointer alternatives"
- Next message in Thread: Swift, Daniel P.: "Re: multiple navigation landmarks"
- Previous message in Thread: glen walker: "Re: Landmarks"
- View all messages in this Thread