[sword-devel] Sword for the Blind

[Don Elbourne]

Thanks.

As far as I understand it, the main thing that a software needs to do is 
have keyboard shortcuts for any actions and to label everything. The 
users screen reader of choice will take care of the rest.

I will be glad to do the leg work to see if there are some standards 
that would give more concrete guidance. And if ya'll are open to it, I 
will even try to recruit some programmers to implement anything necessary.

I hear that the leading commercial Bible software out there is not very 
screen reader friendly.

The reason I bring this up is that I have just launched a new blind 
ministry and I would love to point my users to the Sword Project.

The John L. Dagg Resource Center for the Blind and Visually Impaired
https://www.facebook.com/blindministry/
(full web site coming soon)

The mission of the John L. Dagg Resource Center is  to make good 
theological books and material accessible to the blind and visually 
impaired.

Thanks, and keep up the great work.

-- 
by grace alone,

Pastor Don A. Elbourne Jr.
Lakeshore Baptist Church
http://lakeshorebaptist.net
http://rebuildlakeshore.com

On 2/24/2020 3:42 PM, Jaak Ristioja wrote:
> Hello,
>
> On 24.02.20 23:08, Don Elbourne wrote:
>> Have any of the Sword front-ends been tested to see how well they do
>> with screen readers, used by the blind and visually impaired?
> Being involved with the BibleTime frontend, I can say that to my
> knowledge BibleTime has not been tested.
>
> There is a long-standing low-priority issue for this thou:
>    https://github.com/bibletime/bibletime/issues/5
>
> We haven't given this issue much thought, but it would probably require
> a redesign of the BibleTime frontend, to the extent that writing an
> entirely new, a more accessible frontend, might be a better option,
> because it might not be straightforward to make some of our GUI flows
> usable with text-to-speech engines.
>
> While BibleTime uses the Qt toolkit for the GUI and the latter has at
> least some support for accessibility interfaces, we have not had any
> code changes being introduced for accessibility as far as I know.
>
> I guess many (including myself) don't have a much knowledge (let alone
> experience) about how to develop and test accessible frontends, so any
> guidance on this matter would be welcome. What environments, software or
> screen readers are used, are there any guides available for best
> practices (e.g. like Web Content Accessibility Guidelines are for the
> web) etc?
>
> Best regards,
> J
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page