E-mail List Archives
Re: Accessible Mega Menu and Safari
From: Bryan Garaventa
Date: Mar 31, 2016 4:15PM
- Next message: Gijs Veyfeyken: "Re: Accessible and Responsive Navigation"
- Previous message: Robert Fentress: "Re: Accessible Mega Menu and Safari"
- Next message in Thread: Brooks newton: "Re: Accessible Mega Menu and Safari"
- Previous message in Thread: Robert Fentress: "Re: Accessible Mega Menu and Safari"
- View all messages in this Thread
Not premature, the more bugs that are filed with different steps to reproduce, the better.
This also effects iOS, where VO isn't tracking focus movement properly.
E.G
http://whatsock.com/tsg/Coding%20Arena/Modals/Modal%20(Internal%20Content)/demo.htm
It appears that when element.focus() is used to set focus to an element, VO in iOS will do so when the element is onscreen, however when setting focus to an offscreen element such as in the modal above in order to set focus to the beginning of the modal content, VO will not be moved.
As a result, when swiping from left to right or right to left using one finger, focus appears to be stuck on the Login button even though this is already hidden using aria-hidden="true" at this point.
This is an iOS bug, because it is still possible to read such offscreen content such as hidden headings and the like when swiping from left to right in this manner on iOS, so there should be no reason why focus can't be set to this location as well. This is often how focus is handled for dynamic content regions that are opened when there is no otherwise logical place to set focus other than by using an offscreen element at the beginning of the content region.
Another issue is that, at least on iOS using VO, dynamic elements or content that is dynamically updated within a heading is not being recognized by VoiceOver. Such as when a heading is also a live region using aria-live="polite", and when an interactive role state changes, such as when toggling a button within a heading that includes aria-pressed="true" or aria-pressed="false", where the state change is not being recognized.
- Next message: Gijs Veyfeyken: "Re: Accessible and Responsive Navigation"
- Previous message: Robert Fentress: "Re: Accessible Mega Menu and Safari"
- Next message in Thread: Brooks newton: "Re: Accessible Mega Menu and Safari"
- Previous message in Thread: Robert Fentress: "Re: Accessible Mega Menu and Safari"
- View all messages in this Thread