242112 - (calendar-kbd-access) [meta] make calendar keyboard accessible

Status: NEW

(Calendar :: General, defect)

Description

[Mostafa Hosseini]

<aaronlev> But I think a main thing is to allows the user to arrow around and
select items in the calendar grid
<aaronlev> and get context menus with shift+f10

Comment 1

[Aaron Leventhal]

Please see:
http://www.mozilla.org/projects/ui/accessibility/accessible-xul-authoring.html

I can help advise on multiple discontiguous selection with the keyboard when
someone starts working on this bug.

Comment 2

[Matthew (lilmatt) Willis]

Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove

Comment 3

[Omar Bajraszewski]

(In reply to comment #0)
> <aaronlev> But I think a main thing is to allows the user to arrow around and
> select items in the calendar grid
> <aaronlev> and get context menus with shift+f10

Is it still valid? Can it be closed?

Comment 4

[Michiel van Leeuwen (email: mvl+moz@)]

No, it can not be closed. It is still very valid.

Comment 5

[Philipp Kewisch [:Fallen][📱📆]]

I think this would make a nice student project, description may follow soon. If this hasn't happened by the time you are interested, please contact me.

Comment 6

[Philipp Kewisch [:Fallen][📱📆]]

Bug 472448 would probably also make a nice candidate

Comment 7

[Philipp Kewisch [:Fallen][📱📆]]

A group of three students from Brazil in a course about open source is going to be working on this bug as a student-project. Looking forward to your patch(es), thanks Eduardo!

Comment 8

[Philipp Kewisch [:Fallen][📱📆]]

Taking this off the beta list, there are enough accessibility bugs on the 1.0 blocking list, its unlikely we can achieve full accessibility in that timeframe.

Comment 9

[Veeraya Pupatwibul]

I don't quite get this bug. Does "Make calendar keyboard accessible" mean keyboard short-cut? Could someone please elaborate more? I'm interested in this bug. Thanks!:)

Comment 10

[Abhishek Bhattacharya [:babhishek21]]

Anybody working on it yet? (looks like this has been here for a long time)
If not, I might be interested.

If possible, I'd prefer to work this out under GSOC 2015. Is it ok to put it up for GSOC 2015? 
Some things to consider:
1. Project wide enough for the summer. Has to be handled by a single student.
2. A Mentor is required. Mentor gets USD 500 from Google.

If it is suitable for GSOC and a mentor is found, I'll be willing to put it up on the Brainstorming[1] wiki.

Mentors/QA Contacts/anybody else in charge, reply please.

[1] https://wiki.mozilla.org/Community:SummerOfCode15:Brainstorming

Comment 11

[Abhishek Bhattacharya [:babhishek21]]

EDIT to comment #10,

Mentoring Organisation (in this case Mozilla) gets USD 500 from Google.

Comment 12

[Philipp Kewisch [:Fallen][📱📆]]

Hey Abhishek, I'm pretty sure this is a good idea for a project, I'll have to take a look at the current state though to double check. You can go ahead and put it up on the brainstorming page and set me as a mentor, I will hash out the actual mentorship once the deadline approaches. We are two mentors for Calendar right now, so any two of the three projects will be chosen given we get the slots. I may be able to find a third mentor if we surpisingly get three slots.

If you want to contact me on IRC, my nickname is Fallen. I'll leave the needinfo field set so I don't forget, but feel free to nag me any time or ask questions when I am around.

Comment 13

[Abhishek Bhattacharya [:babhishek21]]

(In reply to Philipp Kewisch [:Fallen] from comment #12)
> Hey Abhishek, I'm pretty sure this is a good idea for a project, I'll have
> to take a look at the current state though to double check. You can go ahead
> and put it up on the brainstorming page and set me as a mentor, I will hash
> out the actual mentorship once the deadline approaches. We are two mentors
> for Calendar right now, so any two of the three projects will be chosen
> given we get the slots. I may be able to find a third mentor if we
> surpisingly get three slots.
> 
> If you want to contact me on IRC, my nickname is Fallen. I'll leave the
> needinfo field set so I don't forget, but feel free to nag me any time or
> ask questions when I am around.

Thanks for the fast reply. I just applied for Editorship on Mozilla Wiki (so it will take some time) If possible, can you put it up yourself. I'd be highly grateful. If you are busy, then I'll try and put it up as soon as I can, or get someone else to put it up! Thanks again.

Another thing, when can I catch you on IRC? (time zone, your free hours, etc.)

Comment 14

[Philipp Kewisch [:Fallen][📱📆]]

I don't remember what we last discussed here, but as you know Mozilla is not part of GSoC. Would you still be interested in working on it?

Comment 15

[Abhishek Bhattacharya [:babhishek21]]

(In reply to Philipp Kewisch [:Fallen] from comment #14)
> I don't remember what we last discussed here, but as you know Mozilla is not
> part of GSoC. Would you still be interested in working on it?

Yes sure. Would you like me to start now? If it is better done over a continuous time frame of ~2 months, then my summer vacations (from June first week) would be perfect. If you want to start now, that would be a bit tight though.

Comment 16

[Philipp Kewisch [:Fallen][📱📆]]

There is no bound on when you should complete this, since its not a Summer of Code project anymore, just a simple voluntary contribution. You can get started right away as it fits into your schedule, there is no deadline on when it should be done.

First I'd suggest going through the list of dependent bugs. Some of them might be fairly easy and can be done when you have a free hour or two in the evenings, for example bug 260121. That also has the advantage that you don't have a pressure to learn everything about the Lightning codebase at once but can gradually get started.

Comment 17

[Wayne Mery (:wsmwk)]

full list http://mzl.la/1XISplL

Comment 18

[Utkarsh Malviya]

I am new to open source!
I know HTML, CSS, JavaScript and Jquery!
Can you please help me to solve this bug.
Thankyou!

Comment 19

[Wayne Mery (:wsmwk)]

(In reply to Utkarsh Malviya from comment #18)
> I am new to open source!
> I know HTML, CSS, JavaScript and Jquery!
> Can you please help me to solve this bug.
> Thankyou!

You probably know this, but this is a just a meta bug, the bugs to be fixed should be marked blocking this bug. I think the only one in the blocking list or http://mzl.la/1XISplL ** marked as "good first bug" is bug 736071. But perhaps fallen or someone he nominates can point you to other good starter bugs. There may even be ones with draft patches

** And there may be other accessibility candidates in https://mzl.la/2d005PO - which lists bugs that have the string "accesssibility".  Any which are valid accessibilty issues should get the access keyword and marked blocking this bug.

Comment 20

[Philipp Kewisch [:Fallen][📱📆]]

Yes, please email me if you need help getting started. Working on accessibility bugs requires some understanding of the ARIA standard and willingness to learn about XUL and XBL. I can help you get started there, but some self-learning will be required.

Comment 21

[Utkarsh Malviya]

Hey Philipp, I emailed but you didn't reply!
Can you fuide me for GSoC. I want to contribute in mozilla and I think GSoC will be a good starting point.

Comment 22

[rahul.shivaprasad]

Hi,
I would like to work on this project if no one is working on it.

Comment 23

[chrizilla]

(In reply to Wayne Mery (:wsmwk) from comment #19)

[…] http://mzl.la/1XISplL […]
And there may be other accessibility candidates in https://mzl.la/2d005PO - which lists bugs that have the string "accesssibility".
Any which are valid accessibilty issues should get the access keyword and marked blocking this bug.

I didn't have time for https://mzl.la/2d005PO but I went through http://mzl.la/1XISplL and https://mzl.la/4crOMNN and am adding all accessibility issues here as requested + will add access for each bug.