Open
Bug 1164236
Opened 9 years ago
Updated 2 years ago
Intro View Accessibility
Categories
(Firefox for iOS :: General, defect)
Tracking
()
NEW
People
(Reporter: dusek, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(1 file)
- "Back"/"Forward" should be labeled as "Previous"/"Next" - After pressing the arrow, VoiceOver cursor should move to the text of the item (not stay on the arrow).
Reporter | ||
Comment 1•9 years ago
|
||
The intro wizard has changed significantly so the previous assessment of its accessibility is no longer valid. Right now, there are these accessibility issues: - no way to go to the next/previous screen - there are no longer the Next/Previous buttons, scrolling gestures do not work; only by a workaround - double-press-and-hold, then flick right/left - scrolls accordingly - the adjustable page indicator cannot be adjusted - images are not conveyed to accessibility (no descriptions) - e.g. the first image contains a hint where the tabs button is with respect to other UI elements, and that it contains a number of tabs. This is a useful "101"-type information that should be conveyed to a VoiceOver user too - "Start Browsing" should be invokable by accessibility escape gesture
Reporter | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 2•9 years ago
|
||
The bug will not be fixed after integrating this first PR. (That will only happen after integrating a second PR which I anticipate in 1-2 weeks.) So please do not close this bug after merging this first PR.
Attachment #8632323 -
Flags: review?(bnicholson)
Comment 3•9 years ago
|
||
It's usually a good idea to open a separate bug per pull request; I would have suggested creating a separate bug specifically for landing the early strings (this helps reduce clutter and avoid confusion). No big deal though. Thanks! https://github.com/mozilla/firefox-ios/commit/13770619e9b9aae4da604eff56f360c23aeee44a
Updated•9 years ago
|
Attachment #8632323 -
Flags: review?(bnicholson) → review+
Comment 4•9 years ago
|
||
What prevents this from landing?
Reporter | ||
Comment 5•9 years ago
|
||
I haven't finished it yet (though I have some intermediate state in my git on my laptop). The original pull request was just for translatable strings, with actual work to follow in another pull request.
Comment 6•9 years ago
|
||
Hey Boris, I noticed that there are a couple of new strings added in this patch: https://github.com/mozilla/firefox-ios/commit/13770619e9b9aae4da604eff56f360c23aeee44a Do you know if these made it onto master? We're currently string frozen for 1.0 so any additional strings will unfortunately need to be added to the 1.1 release.
Reporter | ||
Comment 7•9 years ago
|
||
Hello Stephan, yes, the strings luckily made it, the only thing left now is to finish the actual code :-)
Comment 8•9 years ago
|
||
Awesome :) Thanks for all the hard work on the accessibility stuff btw!
Reporter | ||
Comment 9•9 years ago
|
||
(In reply to Stephan Leroux [:sleroux] from comment #8) > Thanks for all the hard work on the accessibility stuff btw! Thanks :-)
Comment 10•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:jeevans, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: dusek → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(jeevans)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•