Design to perform an accessibility pass for the feature.
Is the out-of-the-box implementation functional? Do modules need to be grouped alternatively, or do any accessibility labels need to renamed?
Identify any fixes and prioritize P0, P1, P2 in a punchlist
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T406183 [Epic] AB test Activity Tab V2 on iOS | |||
| Resolved | GOlson-WMF | T409766 [Design] Activity tab accessibility review for December release |
per @HNordeenWMF's comment on Slack, copying my comment over here: I noticed that when I have dynamic type set up, the "Time spent reading this week" in languages where the text is longer ends up left-aligning rather than staying centered. i'm not sure if this is another result of the reformatting of the screen due to the timeline of behavior. Noting here so we can prioritize all accessibility-related fixes later on.
@HNordeenWMF i don't think we're at the phase yet where this ticket can be signed off on since many requirements remain to be implemented per spec across the feature — should this ticket just hang out in my column until we're at that point?
Hey @SChekfa-WMF, we're releasing next week, so we want to do accessibility review covering what has been built so far before it goes out to users. Here are the user stories going out in the release:
hi @HNordeenWMF, do you mean that the feature is going out to beta not fully built? i haven't seen any editing modules in my lane, nor the customization modules. or will those arrive in my lane before we go out next week?
also, what do the crossed out tickets represent in the list you provided? @HNordeenWMF
@HNordeenWMF i've done a pass on the tickets above and noted all accessibility issues i found in a tab in our punchlist.
@SChekfa-WMF Cross-out tickets are simply ones that have been closed, because we released them behind a feature flag.
Pushing this back to "Did not pass design review". @Engineers please address the P0 items 4 and 5 in the punchlist