Not sure if you are suggesting to disable a11y completely. I don't think we want to do that since it is in pretty good shape.
What we can do is disable or not land specific a11y features that wont make it on time to be fully localized. S. On Tue, Jul 7, 2015 at 6:30 PM, Axel Hecht <[email protected]> wrote: > Any strings should be frozen, including a11y. > > If that's not the case, that's bad. > > The resolution to that is either to get a timeline for a11y in the v1 > release, or to remove it from the v1 release. > > Note, I'm not sure that a mixed language a11y story is a good user > experience, so if we can't get a localized a11y UX into v1, we'd need to > find a way to disable it. > > Axel > > On 7/7/15 10:34 PM, Brian Nicholson wrote: > >> Can someone summarize where we are now with the string freeze, and >> what the freeze covers? >> >> Namely, are a11y strings included in the freeze? If so, I think our >> a11y strings are far from complete -- we continue to get PRs from >> dusek (our awesome a11y contributor) that contain NSLocalizedString >> additions. Also, I expect that we'll be adding/updating a11y labels as >> we continue to refine our UI tests since KIF and a11y strings are >> tightly coupled. >> >> On Thu, Jul 2, 2015 at 1:47 PM, Stef <[email protected]> wrote: >> >>> Wiadomość napisana przez Stefan Arentz <[email protected]> w dniu 2 >>>> lip 2015, o godz. 21:52: >>>> >>>> I think we are pretty close. I don't think we have any outstanding >>>> strings >>>> at this point. >>>> >>>> I have looked at many l10n bugs and resolved almost all of them. >>>> >>> >>> Nice! >>> >>> Fixes 1175887 - Not all string tables are properly converted to .stri… >>>> < >>>> https://github.com/mozilla/firefox-ios/commit/6e7d3ee3567ad3b3fbcf29e07c267ec48ef54731 >>>> > >>>> >>>> >>>> The last one is worth mentioning: a number of strings were not actually >>>> included in the build. I'm surprised nobody really noticed. I think that >>>> shows that we need to figure out a way to do more automated testing. For >>>> example with screenshots taken of every possible piece of UI that we >>>> have. >>>> >>> >>> Screenshots of every possible UI state (in language other then English, >>> pseudolocale maybe?) would be great but that could be quite hard and I >>> think improving l10n story could yield better results. >>> >>> Most of the strings should be localized in pl¹ but import/export and >>> ignoring valid strings especially sucks and irregular test builds suck too >>> - how many unlocalizable unreported strings can be spotted in last >>> TestFlight build (22? from ~2 weeks ago?)? >>> >>> >>> 1. Thanks to https://github.com/splewako/firefox-ios-l10n-en >>> _______________________________________________ >>> mobile-firefox-dev mailing list >>> [email protected] >>> https://mail.mozilla.org/listinfo/mobile-firefox-dev >>> >> > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
