Closed Bug 1527381 Opened 8 months ago Closed 6 months ago

Please replace sec508 keyword with access keyword for all bugs with sec508 keyword

Categories

(bugzilla.mozilla.org :: Bulk Bug Edit Requests, task)

Production
task
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: asa, Assigned: emceeaich)

Details

The Accessibility Team has concluded that the value of a distinct "sec508" keyword is very low today and we should replace it with the more commonly used and understood "access" keyword. We would like to do this for all bugs with the sec508 keyword and to do it without sending bugmail.

The query for bugs with the sec508 keyword is this: https://bugzilla.mozilla.org/buglist.cgi?keywords=sec508&limit=0

Once the change has been made, we would like to see the sec508 keyword removed from the keywords list.

Do we also want to rename access keyword to a11y? (The same thing applies to the ue keyword, which can be renamed to ux, though it’s a separate bug.)

(In reply to Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat) from comment #1)

Do we also want to rename access keyword to a11y? (The same thing applies to the ue keyword, which can be renamed to ux, though it’s a separate bug.)

Just my opinion, but "access" is more accessible than "a11y". I would rather we didn't change access to a11y.

(In reply to Asa Dotzler [:asa] from comment #2)

Just my opinion, but "access" is more accessible than "a11y".

I know the ironic accessibility issue 😉 For me, access sounds vague, because it can refer to a general internet access/connection issue or whatever.

IMO, we shouldn't change the access keyword. I agree it's a bit confusing, but there are probably a lot of queries (and habits!) that will break if we do this. (In contrast, sec508 is much less used, particularly these days.)

FWIW, if we were going to change it, I think a11y would be fine. Weird as it sounds to speech users, it is a common "term" in the a11y community, so we're used to it.

I'm going to ask twitter and in a couple of places to get feedback on this, because I understand a11y to be widely understood as the term. See '#a11ychat' tag, etc.

We are using the access keyword probably because a11y was not a common term before and the original initiative was called Access Mozilla. As I mentioned, user experience is now also abbreviated as ux, not ue.

Keywords can be altered whenever needed. We recently changed footprint, mlk and topmlk to memory-footprint, memory-leak and top-memory-leak respectively, and no one has complained about it. These are all legacy.

This has been sitting stalled, so can we switch to a11y or access?

We discussed this in a team meeting this week. Consensus was to do comment 0 (sec508 -> access) but leave access alone (no rename of "access").

Order of operations

  1. Add access keyword to all bugs with sec508 keyword
  2. Remove sec508 keyword from bugs with that keyword
  3. Disable sec508 keyword
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.