Project

General

Profile

Actions

Feature #8901

open

Theme analysis for accessibility

Added by Matt Gold almost 5 years ago. Updated 5 months ago.

Status:
Assigned
Priority name:
Normal
Assignee:
Category name:
Accessibility
Target version:
Start date:
2017-11-10
Due date:
% Done:

0%

Estimated time:

Description

review top themes for accessibility

Actions #1

Updated by Matt Gold almost 5 years ago

  • Target version set to 1.13
Actions #2

Updated by Matt Gold almost 5 years ago

  • Tracker changed from Bug to Feature
Actions #3

Updated by Boone Gorges over 4 years ago

This is an important task, but doesn't need to be tied to a milestone.

Could we have a discussion of this during a team meeting? Perhaps a member of the community team could take the lead on the review. I could provide a list of most popular themes, along with a brief primer on how to do a simple accessibility scan.

Actions #4

Updated by Boone Gorges over 4 years ago

  • Target version changed from 1.13 to 1.14
Actions #5

Updated by Boone Gorges almost 4 years ago

Steve, adding you as a watcher. Perhaps we could talk during our next dev chat about how we might structure this kind of review.

Actions #6

Updated by Boone Gorges almost 4 years ago

  • Target version changed from 1.14 to 1.15
Actions #7

Updated by Boone Gorges over 3 years ago

Adding some watchers to this ticket. Luke or Laurie (I think?) mentioned this project during our last meeting. I wonder if we could come up with the sketch of a plan, and think about how work might be divided up. Maybe a Summer 2019 task? For now, leaving in the milestone for visibility.

Actions #8

Updated by Raymond Hoh over 3 years ago

Just wanted to quickly note while working on the GCDI site that the make theme doesn't use a <label> element for the search form because they override the form with a search template file. Until they fix this, we can use the 'get_search_form' filter to add back the <label> element dynamically.

Actions #9

Updated by Boone Gorges over 3 years ago

  • Target version changed from 1.15 to 1.16

Had a chat recently with Krysia and Laurie about this ticket. They've got a plan and will be starting on the review, but it's not tied to the 1.15 release.

Actions #10

Updated by Laurie Hurson almost 3 years ago

Hi All,

As discussed on the dev call earlier this week I have written up a summary of our Accessibility review here: https://docs.google.com/document/d/1mmHq1XLULv1YkmKgQExjtjKjuwlGq3fnvMuoxGoGuJk/edit?usp=sharing

Actions #11

Updated by Boone Gorges almost 3 years ago

I wanted to say thanks for the update, Laurie - I'm going to take time in the first few days of next week to look it over in detail and determine next steps.

Actions #12

Updated by Boone Gorges almost 3 years ago

  • Target version changed from 1.16 to 1.17.0
Actions #13

Updated by Boone Gorges about 2 years ago

  • Target version changed from 1.17.0 to 1.18.0
Actions #14

Updated by Boone Gorges almost 2 years ago

  • Target version changed from 1.18.0 to 1.19.0
Actions #15

Updated by Boone Gorges 10 months ago

  • Target version changed from 1.19.0 to 2.0.0
Actions #16

Updated by Boone Gorges 5 months ago

  • Target version changed from 2.0.0 to Future release
Actions

Also available in: Atom PDF