GAAD A11y Bug Bash
Comments
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Still loading...
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAF
1
Bug #TitleDescriptionSteps to ReproduceExpected ResultsActual ResultsScreenshotPlatform User AgentAssistive TechnologyImpactStatusURL to Bug ReportBug Report ID#Bug Reported ByAdditional NotesBug TrackerURLDetails/Bug Reporting GuidelinesBug Type
2
1.01VoiceOver 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.3Mobile SafariVoiceOverCriticalNot Fixedhttps://bugreport.apple.com/
18412597Paul J. AdamThis 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 Reporterhttp://bugreport.apple.com Screen Reader
Assistive Technology
Native iOS/OS X
3
1.02VoiceOver 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".
OR
VoiceOver speaks "Password *, required, edit text, (ding-earcon-unique-for-help-text)" User invokes help text command to hear hint.
OR
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.3Safari 8.0.6VoiceOverCriticalFixedhttps://bugreport.apple.com/problem/viewproblem21029190Paul J. AdamThis 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 Radarhttp://www.openradar.meOpen 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
Assistive Technology
Native iOS/OS X
4
1.03Google 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.3Mobile SafariVoiceOverCriticalNot Fixedhttp://www.google.com/accessibility/get-in-touch.htmlN/APaul J. AdamFiled under Google's get in touch accessibility contact form not sure where to file this?

reCAPTCHA api2 Accessibility Docs:
https://support.google.com/recaptcha/#6175971
Chromium bug trackerhttps://code.google.com/p/chromium/issues/listhttp://www.chromium.org/for-testers/bug-reporting-guidlines-for-the-mac-linux-buildsBrowser
5
1.04VoiceOver 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.3Mobile SafariVoiceOverCriticalFixedhttps://bugreport.apple.com/problem/viewproblem21051187Paul J. AdamThis was a very important bug to get fixed as <iframe>s are so popular in modern web development.Internet Explorer Feedbackhttps://connect.microsoft.com/ie/https://connect.microsoft.com/IE/content/content.aspx?ContentID=29582Browser
6
1.05Siri image search not accessible to VoiceOver screen reader users on the Apple Watch. No alt text even on the bing logoVO 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=pauljadamApple Watch OS 1.0.1VoiceOverCriticalNot Fixedhttps://bugreport.apple.com/problem/viewproblem21064389Paul J. AdamSee screenshot for instagram video of bug.Bugzilla@Mozillahttps://bugzilla.mozilla.orghttps://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelinesBrowser
7
1.06HTML title attribute text not accessible to keyboard users in all browsers.NVDA Issueshttp://community.nvda-project.org/wiki/IssuesScreen Reader
8
1.07HTML Headings not navigable with a keyboard in all browsers.Webkit bugzillahttps://bugs.webkit.org/https://bugs.webkit.org/page.cgi?id=bug-writing.htmlBrowser
9
1.08GNOME (Orca) Bugzillahttps://bugzilla.gnome.org/enter_bug.cgi?product=orcaScreen Reader
10
1.09feedback about Android accessibilityhttp://www.google.com/accessibility/get-in-touch.htmlScreen Reader
Assistive Technology
11
1.10bug on iOS VoiceOver where you lose focus to top of DOM after selecting a popup button picker itemhttp://pauljadam.com/demos/mobileforma11y.htmlSteve Faulkner's filing bugs tutorialhttp://www.paciellogroup.com/blog/2014/06/filing-bugs/
12
1.11Google Hangouts A11y Problems?
13
1.12Adobe Connect Not Accessible on iOS OS X with VoiceOverNothing is focusable or readable in the Adobe Connect iOS app with VoiceOver. It's not possible to login to a webinar.
14
1.13Adobe Connect Chat Not Accessible
15
1.14JAWS/IE does not speak role=alert text automatically. Only aria-live=assertive works.
16
1.15NO <ins> and <del> <sub> and <sup>
17
1.16Apple's iCloud.com Online iWork office suite not accessible.
18
1.17aria-required not working in Chrome 42Looks 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/aWin7, MacOS - others not testedChrome 42VO, NVDA, JAWSAssignedhttps://code.google.com/p/chromium/issues/detail?id=487401487401Patrick FoxFiled last week , actually. Looks like they're working on it now!
19
1.18ARIA menu not announced correctly in IESee bug report URLhttps://connect.microsoft.com/IE/feedbackdetail/view/1356649/ie-exposes-aria-menu-incorrectlyDylan Barrell
20
1.19aria-hidden specification misleadingSee bug report URLhttps://www.w3.org/Bugs/Public/show_bug.cgi?id=28677
21
1.20
22
1.21Please Add More Bugs folks! :)
23
1.22
24
1.23
25
1.24
26
1.25Bug Tracker details start in Column R to the right ->
27
1.26
28
1.27
29
1.28
30
1.29
31
1.30
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
BugList