[Spike] Page tools: accessibility requirements for Page Tools
Closed, ResolvedPublic1 Estimated Story PointsOct 10 2022
Actions

Assigned To

Authored By

	ovasileva
	Sep 27 2022, 10:58 AM

Description

Background

We're beginning the work for page tools and would like to define the accessibility requirements for the feature

Acceptance criteria

Review feature proposal and identify accessibility requirements and changes necessary
Add above requirements to the ticket in which the work will need to be considered

Details

Due Date: Oct 10 2022, 7:00 AM

Related Objects
Search...

Status	Subtype	Assigned	Task
Resolved		ovasileva	T317884 [EPIC] Vector 2022 post-deployment work
Resolved		ovasileva	T302073 [GOAL] Page Tools available on all wikis
Resolved	Oct 10 2022	Jdrewniak	T318690 [Spike] Page tools: accessibility requirements for Page Tools

Event Timeline

ovasileva created this task.Sep 27 2022, 10:58 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 27 2022, 10:58 AM

ovasileva triaged this task as Medium priority.Sep 27 2022, 10:58 AM

ovasileva added a parent task: T302073: [GOAL] Page Tools available on all wikis.

Jdlrobson edited projects, added Web-Team-Backlog-Archived (Kanbanana-2022-23-Q2); removed Vector 2022, Web-Team-Backlog-Archived (Kanbanana-2022-23-Q1).Sep 29 2022, 5:17 PM

Jdlrobson set the point value for this task to 1.Sep 29 2022, 5:30 PM

Jdlrobson assigned this task to bwang.Oct 3 2022, 5:47 PM

@ovasileva What exactly is needed for analysis of spike tickets? Should this just be moved to ready to dev?

In T318690#8287924, @bwang wrote:

@ovasileva What exactly is needed for analysis of spike tickets? Should this just be moved to ready to dev?

Yeah, that makes a lot of sense actually

bwang moved this task from Ready for Development to Doing on the Web-Team-Backlog-Archived (Kanbanana-2022-23-Q2) board.Oct 6 2022, 9:00 PM

After reviewing the tasks in this epic I came up with these ACs

Landmark regions are preserved and accessible by screenreaders when a menu is pinned and unpinned (Accounted for the article tools in T317897, and for the main menu in T317899 and T317900)
Contents of pinned menu are immediately follows the menu toggle in the DOM so the contents are accessible to keyboard/screenreader users (Accounted for the article tools in T317897, and for the main menu in T317899)
Ensure brackets in pinnable toggle buttons aren't read out to screenreaders. (Accounted for in T317897)
Ensure collapsible sections of the article tools dropdown follow ARIA authoring guidelines for the disclosure widget (Accounted for in T318168)
Existing "More options" landmark name is renamed, now that the "More" menu is repurposed into the "Tools" article tools menu. (Accounted for in T318434)

bwang moved this task from Doing to Ready for Signoff on the Web-Team-Backlog-Archived (Kanbanana-2022-23-Q2) board.Oct 19 2022, 4:40 PM

bwang removed bwang as the assignee of this task.Oct 20 2022, 5:09 PM

bwang subscribed.

LGoto assigned this task to Jdrewniak.Oct 20 2022, 5:10 PM

Jdlrobson set Due Date to Oct 10 2022, 7:00 AM.Oct 21 2022, 10:59 PM

Jdlrobson changed the subtype of this task from "Task" to "Deadline".

• alexhollender_WMF renamed this task from [Spike] Article tools: accessibility requirements for Article Tools to [Spike] Page tools: accessibility requirements for Page Tools .Oct 25 2022, 7:21 PM

• alexhollender_WMF updated the task description. (Show Details)

Jdrewniak closed this task as Resolved.Oct 27 2022, 5:05 PM

bwang added projects: Accessibility, Vector 2022.Nov 7 2022, 6:35 PM

bwang mentioned this in T323634: Track AFB accessibility testing results in phab.Dec 12 2022, 10:26 PM

[Spike] Page tools: accessibility requirements for Page Tools Closed, ResolvedPublic1 Estimated Story PointsOct 10 2022Actions