[liblouis-liblouisxml] Re: Adding comments to issues

  • From: Michael Whapples <mwhapples@xxxxxxx>
  • To: liblouis-liblouisxml@xxxxxxxxxxxxx
  • Date: Tue, 15 Oct 2013 22:09:12 +0100

This is what I was thinking of.
I did not know about github allowing reply by email. Does it allow opening a issue by email and changing the status of the report by email?
While it would require hosting it I know that a system like roundup offers all that.
As John said though a simple web interface should be just as acceptable and I would imagine it would be easier to find a hosted solution with a simple web interface. However there does seem to be a trend for web developers to complicate the interface for no apparent reason, other than to show how much javascript/ajax/other web technology they can use. 

Michael Whapples
On 15/10/2013 21:08, Bert Frees wrote:
I'm not saying "move to Github", but maybe there is an issue tracker out there that has the same feature, in which case the accessiblity of the web interface is not so crucial. 

On 15 Oct 2013, at 22:06, Bert Frees wrote:
For what it's worth (and I haven't been following the discussion very closely, so maybe someone mentioned this before): the Github issue tracker has an "email reply support" feature[1], which basically means that you can follow and participate in conversations both with email and on the Github website. 

[1] https://github.com/blog/811-reply-to-comments-from-email

On 15 Oct 2013, at 20:32, John J. Boyer wrote:
Given the captcha problem, I now agree that we need to find a diffferent 
issue tracker. I tried adding a comment with IE, but couldn't get
anywhere. An issue tracker with a simple web form to fill out would be
no problem for me. It should also not use Javascript. I prefer elinks,
which is a text browser.

John

On Tue, Oct 15, 2013 at 05:14:02PM +0100, Michael Whapples wrote:

Hello,
I know I personally have dislikes for how Google do certain things, even 
in what they term as their accessible versions and feel that usability
could certainly be far better.

I never actually tried adding more than one comment to a bug so cannot
comment on whether a captcha is used. If that is true then in my mind it is totally unacceptable for this project as captcha's are accessibility 
problems (difficult enough for me with just sight problems, but the
audio alternative is next to useless to someone with good hearing so I
would guess is totally useless for someone in John Boyer's situation
with hearing issues as well).

Also there is the issue that I think John Boyer can have difficulties
with some web interfaces and would prefer to use email interfaces.
I know that some have resisted using something else for an issue tracker 
as they felt the alternatives are far more advanced than we need and
might require additional effort to maintain. However considering these
serious accessibility issues, it appears the GoogleCode issue tracker is not suitable and so while alternatives have been placed on the table and rejected, I feel we now need those who have rejected proposed solutions 
to suggest their own solution which could be deemed acceptable from an
accessibility view.

Michael Whapples


On 15/10/2013 16:34, Vic Beckley wrote:

Hello to those in power,

I have been testing out the accessibility of the issue tracker on the
Google
Code page for liblouisutdml. I was able to add my first comment just fine and it was sent to the list. However, every time I try adding a comment now I am asked to enter the text from a CAPCHA image. I could probably fight with the CAPCHA by using the audio challenge link but this is a nuisance. I have heard about a way around CAPCHAs in Firefox but don't know anything 
about it. Can anyone give me the details on this?
This might be doable, albeit very clumsily, but I think we need to find 
something different. If you get a CAPCHA every time you have to add a
comment, that is bad. It's not just John's problem with GUI web browsing.
Michael, have you added a comment? Any other blind users? What were your 
experiences?


Best regards from Ohio,

Vic



For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com <http://www.abilitiessoft.com/> 

For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com <http://www.abilitiessoft.com/> 

--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com <http://www.abilitiessoft.com/>
Madison, Wisconsin USA
Developing software for people with disabilities

For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com

Other related posts:

  1. Home
  2. liblouis-liblouisxml
  3. Archive
  4. 10-2013