|Bug #||Title||Description||Steps to Reproduce||Expected Results||Actual Results||Screenshot||Platform||User Agent||Assistive Technology||Impact||Status||URL to Bug Report||Bug Report ID#||Bug Reported By||Additional Notes||Bug Tracker||URL||Details/Bug Reporting Guidelines||Bug Type|
|1.01||VoiceOver iOS does not read or focus on <fieldset> <legend> elements||The user cannot set focus to the <legend> using explore by touch or linear, swipe navigation. <fieldset><legend> elements are skipped over completely.||1. Open http://pauljadam.com/demos/mobileforma11y.html in Mobile Safari on iOS 8.3.|
2. Turn VoiceOver on.
3. Set focus to a <fieldset> <legend>.
4. Swipe through all elements on the form.
|VoiceOver speaks the <legend> element text on entering each <fieldset> and when user places focus on <legend>||VoiceOver skips over each <legend> element and will not allow explore by touch focus.||iOS 8.3||Mobile Safari||VoiceOver||Critical||Not Fixed||https://bugreport.apple.com/||18412597||Paul J. Adam||This bug is not fixed but not as broken as before. <legend> is focusable but is not spoken again for each input inside the group like on OS X 10.11.||Apple Bug Reporter||http://bugreport.apple.com||Screen Reader|
Native iOS/OS X
|1.02||VoiceOver OS X does not indicate presense of Help Text or Hints to the user when they set focus to a control with title or aria-describedby attribute values.||The user may tab to a control with a title attribute or aria-describedby value present but the text is not spoken until a 7 second delay and there is no audio or text indication that a Hint or Help Text is even present on the control. This can lead users to not hear form input instructions that are associated with the input because they will not wait for the delayed announcement.||1. Open http://pauljadam.com/demos/aria-describedby-validation.html in Safari on OS X|
2. Turn VoiceOver on
3. Set focus to the Password * input which has instruction text associated via aria-describedby ID reference.
|VoiceOver speaks "Password *, required, edit text, 8 digits, 1 upper case, 1 number, 1 special character".|
VoiceOver speaks "Password *, required, edit text, (ding-earcon-unique-for-help-text)" User invokes help text command to hear hint.
VoiceOver speaks "Password *, required, edit text, hint present" User invokes help text command to hear hint.
|VoiceOver speaks "Password *, required, edit text" User tabs away without hearing the hint after a 7 second delay.||OS X 10.10.3||Safari 8.0.6||VoiceOver||Critical||Fixed||https://bugreport.apple.com/problem/viewproblem||21029190||Paul J. Adam||This was originally not the standard behavior. Apple did not document when they made this change. On OS X 10.11 this bug is no longer present because apple changed the help text/hint delay to be almost instant.||Open Radar||http://www.openradar.me||Open radar is a way make your bug reports with Apple public as their tracker is not searchable. This does require you to file both with apple and with open radar (to let the world know).||Screen Reader|
Native iOS/OS X
|1.03||Google reCAPTCHA api2 not accessible to VoiceOver iOS users.||After activating the I'm not a robot checkbox the verification challenge opens but the iOS VO focus is still on the checkbox and they do not get focus shifted to the actual challenge widget. Even though there is an announcement "Opening verification challenge" when the VO user swipes to the next elements their focus never goes into the challenge window. If a user were to get lucky with expore by touch navigation and open the audio challenge then they would find that the text input to enter the challenge answer has no accessible name. The image based challenges for finding pictures of cake or other items are not accessible to the screen reader due to lack of alt text. The audio challenge is difficult to impossible to complete in the allotted amount of time due to short challenge expiration window. The garbled audio challenges that sound like paranormal activity are basically impossible to complete.||1. Open https://www.google.com/recaptcha/api2/demo in Mobile Safari on iOS|
2. Turn on VoiceOver
3. Activate I'm not a robot checkbox
|Focus shifts into the challenge widget as expected. User can then swipe to the audio challenge button. User is able to type the audio challenge into the answer text box which has an accessible name before their time expires.||Focus remains on the I'm not a robot checkbox. User cannot swipe into the challenge widget. User cannot activate audio challenge button. Audio challenge answer text input has no accessible name. User cannot type audio challenge answer in time before it expires and they have to start over again.||iOS 8.3||Mobile Safari||VoiceOver||Critical||Not Fixed||http://www.google.com/accessibility/get-in-touch.html||N/A||Paul J. Adam||Filed under Google's get in touch accessibility contact form not sure where to file this?|
reCAPTCHA api2 Accessibility Docs:
|Chromium bug tracker||https://code.google.com/p/chromium/issues/list||http://www.chromium.org/for-testers/bug-reporting-guidlines-for-the-mac-linux-builds||Browser|
|1.04||VoiceOver for iOS does not read <iframe> elements during linear (swipe) navigation.||VO will skip directly over an iframe and user will not know it is there on the page. Explore by touch is the only method to find the iframe but user would have to guess if one was there.||1. Open https://www.google.com/recaptcha/api2/demo in Mobile Safari on iOS|
2. Turn on VoiceOver
3. Swipe through all elements on the screen
|VoiceOver reads all elements on the screen including setting focus inside the I'm not a robot checkbox <iframe> element during normal linear swipe navigation.||VoiceOver skips right over the <iframe> element never reading the "I'm not a robot checkbox" because it is inside an iframe.||iOS 8.3||Mobile Safari||VoiceOver||Critical||Fixed||https://bugreport.apple.com/problem/viewproblem||21051187||Paul J. Adam||This was a very important bug to get fixed as <iframe>s are so popular in modern web development.||Internet Explorer Feedback||https://connect.microsoft.com/ie/||https://connect.microsoft.com/IE/content/content.aspx?ContentID=29582||Browser|
|1.05||Siri image search not accessible to VoiceOver screen reader users on the Apple Watch. No alt text even on the bing logo||VO only speaks TH image for each image result.||1. Turn On VoiceOver on Apple Watch|
2. Ask Siri to show you a picture of an "orangatang"
3. Swipe through image results with VoiceOver
4. Swipe to Bing logo
|VoiceOver speaks a uniqe and useful accessible name for each image result. VoiceOver speaks an accessible name for the bing logo.||VoiceOver speaks "TH image" TH image" for each result. VoiceOver speaks nothing for the bing logo.||https://instagram.com/p/265fw3kO3j/?taken-by=pauljadam||Apple Watch OS 1.0.1||VoiceOver||Critical||Not Fixed||https://bugreport.apple.com/problem/viewproblem||21064389||Paul J. Adam||See screenshot for instagram video of bug.||Bugzilla@Mozilla||https://bugzilla.mozilla.org||https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines||Browser|
|1.06||HTML title attribute text not accessible to keyboard users in all browsers.||NVDA Issues||http://community.nvda-project.org/wiki/Issues||Screen Reader|
|1.07||HTML Headings not navigable with a keyboard in all browsers.||Webkit bugzilla||https://bugs.webkit.org/||https://bugs.webkit.org/page.cgi?id=bug-writing.html||Browser|
|1.08||GNOME (Orca) Bugzilla||https://bugzilla.gnome.org/enter_bug.cgi?product=orca||Screen Reader|
|1.09||feedback about Android accessibility||http://www.google.com/accessibility/get-in-touch.html||Screen Reader|
|1.10||bug on iOS VoiceOver where you lose focus to top of DOM after selecting a popup button picker item||http://pauljadam.com/demos/mobileforma11y.html||Steve Faulkner's filing bugs tutorial||http://www.paciellogroup.com/blog/2014/06/filing-bugs/|
|1.11||Google Hangouts A11y Problems?|
|1.12||Adobe Connect Not Accessible on iOS OS X with VoiceOver||Nothing is focusable or readable in the Adobe Connect iOS app with VoiceOver. It's not possible to login to a webinar.|
|1.13||Adobe Connect Chat Not Accessible|
|1.14||JAWS/IE does not speak role=alert text automatically. Only aria-live=assertive works.|
|1.15||NO <ins> and <del> <sub> and <sup>|
|1.16||Apple's iCloud.com Online iWork office suite not accessible.|
|1.17||aria-required not working in Chrome 42||Looks like there was a regression error introduced recently. aria-required was working in Chrome but now no longer works.|
0. Go to: http://jsbin.com/tuhupi/1/
1. Start up VoiceOver on MacOS
2. Click/tab to the input field in the above example
3. Listen for "required" to be spoken
|aria-required="true" added to an input should cause that input to be spoken as a "required edit text" in VoiceOver. This used to work in previous versions of Chrome.|
"required" message/state is not communicated by VoiceOver. The HTML5 required attribute works(e.g. communicates "required"), but the aria-required attribute doesn't.
|n/a||Win7, MacOS - others not tested||Chrome 42||VO, NVDA, JAWS||Assigned||https://code.google.com/p/chromium/issues/detail?id=487401||487401||Patrick Fox||Filed last week , actually. Looks like they're working on it now!|
|1.18||ARIA menu not announced correctly in IE||See bug report URL||https://connect.microsoft.com/IE/feedbackdetail/view/1356649/ie-exposes-aria-menu-incorrectly||Dylan Barrell|
|1.19||aria-hidden specification misleading||See bug report URL||https://www.w3.org/Bugs/Public/show_bug.cgi?id=28677|
|1.21||Please Add More Bugs folks! :)|
|1.25||Bug Tracker details start in Column R to the right ->|