Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Accessibility
Accessibility [message #664725] Mon, 11 April 2011 17:13 Go to next message
Jean Bovet is currently offline Jean Bovet
Messages: 34
Registered: September 2009
Member
Hi,

Is there any specific information about accessibility using RAP? In
particular, I am looking at what keyboard shortcuts are available to
navigate in the interface: for example, how do I select a non-selected
tab (in a CTabFolder) to make it the selected tab? Is that browser
dependent or is that something RAP is providing?

Thanks,

Jean Bovet
Re: Accessibility [message #664742 is a reply to message #664725] Mon, 11 April 2011 19:31 Go to previous messageGo to next message
Tim Buschtoens is currently offline Tim Buschtoens
Messages: 386
Registered: July 2009
Senior Member
Hello Jean.

In general all SWT/RWT widgets should be possible to use without the
mouse. However, in case of CTabFolder its key-handling implementation is
still missing in RAP. If you need this specific feature, open an
enhacment request on bugzilla.

Keyhandling in RAP is not browser-dependent. (Some very minor
differences might exit.) Also, you can define your own custom
keybindings (Ctrl/Alt/Shift + any alphanumeric key), which should make
it relatively easy to work around any issues that might still exist for
keyboard-controlling the UI.

We are actually doing some research on RAP and accessibility right now,
though any results are a few months away.

Greetings,
Tim

> Hi,
>
> Is there any specific information about accessibility using RAP? In
> particular, I am looking at what keyboard shortcuts are available to
> navigate in the interface: for example, how do I select a non-selected
> tab (in a CTabFolder) to make it the selected tab? Is that browser
> dependent or is that something RAP is providing?
>
> Thanks,
>
> Jean Bovet
>
Re: Accessibility [message #665257 is a reply to message #664742] Wed, 13 April 2011 21:32 Go to previous messageGo to next message
Jean Bovet is currently offline Jean Bovet
Messages: 34
Registered: September 2009
Member
Thanks Tim. I will open an enhancement request for that.

Jean

On 2011-04-11 12:31:02 -0700, Tim Buschtöns said:

> Hello Jean.
>
> In general all SWT/RWT widgets should be possible to use without the
> mouse. However, in case of CTabFolder its key-handling implementation
> is still missing in RAP. If you need this specific feature, open an
> enhacment request on bugzilla.
>
> Keyhandling in RAP is not browser-dependent. (Some very minor
> differences might exit.) Also, you can define your own custom
> keybindings (Ctrl/Alt/Shift + any alphanumeric key), which should make
> it relatively easy to work around any issues that might still exist for
> keyboard-controlling the UI.
>
> We are actually doing some research on RAP and accessibility right now,
> though any results are a few months away.
>
> Greetings,
> Tim
>
>> Hi,
>>
>> Is there any specific information about accessibility using RAP? In
>> particular, I am looking at what keyboard shortcuts are available to
>> navigate in the interface: for example, how do I select a non-selected
>> tab (in a CTabFolder) to make it the selected tab? Is that browser
>> dependent or is that something RAP is providing?
>>
>> Thanks,
>>
>> Jean Bovet
Re: Accessibility [message #780634 is a reply to message #664742] Wed, 18 January 2012 20:21 Go to previous messageGo to next message
Ronald So is currently offline Ronald So
Messages: 198
Registered: April 2011
Senior Member
Tim,

Is your research finished? I would love to know your findings on Accessibility on RAP.

Thanks,
Ronald
Re: Accessibility [message #780832 is a reply to message #780634] Thu, 19 January 2012 14:45 Go to previous messageGo to next message
Nick Mussin is currently offline Nick Mussin
Messages: 10
Registered: December 2011
Junior Member
Hello Ronald,

currently, we are implementing features that will help performing automated RAP UI tests. This includes support for W3C's accessibility framework WAI-ARIA.

WAI-ARIA's actual purpose is to make web applications accessible to screen readers by providing semantic information about their component's purpose and their current state.

However, it is not yet decided how the WAI-ARIA support will be made available. Probably it is going to be a commercial plugin.

Regards,
Nick
Re: Accessibility [message #780838 is a reply to message #780832] Thu, 19 January 2012 14:59 Go to previous messageGo to next message
Ronald So is currently offline Ronald So
Messages: 198
Registered: April 2011
Senior Member
Thanks Nick. I am aware of the WAI-ARIA effort. Before this commercial plugin becomes available, is there anything developer should do to make their RAP application Section 508 compliant? Are there best practices that we can follow?

Thanks again!
Re: Accessibility [message #782172 is a reply to message #780838] Mon, 23 January 2012 09:45 Go to previous messageGo to next message
Nick Mussin is currently offline Nick Mussin
Messages: 10
Registered: December 2011
Junior Member
Hello Ronald,

you're welcome!

No, currently there are no specific RAP accessibility guidelines. You could check this article to get a general overview of accessibility recommendations for Eclipse plugins. You could also take a look at WCAG 2.0 (web accessibility guidelines) or this comparison between Section 508 and WCAG.

Regards,
Nick

Re: Accessibility [message #1242756 is a reply to message #782172] Mon, 10 February 2014 03:36 Go to previous messageGo to next message
Barys Dubauski is currently offline Barys Dubauski
Messages: 33
Registered: July 2009
Member
Hi Nick / RAP gurus,

Can you please give an update on where the latest RAP release is in terms of supporting WAI-ARIA and WCAG 2.0 guidelines?

I'm tasked with determining if our RAP based application complies with web accessibility standards and would appreciate the definitive answer from RAP representatives. Is there something special extra that developers using RAP to build their web applications should do to comply or accessibility support is already there (since actual implementation is based on Eclipse/SWT which supports accessibility)?

Thank you,
Barys
Re: Accessibility [message #1243797 is a reply to message #1242756] Tue, 11 February 2014 13:02 Go to previous messageGo to next message
Ralf Sternberg is currently offline Ralf Sternberg
Messages: 1291
Registered: July 2009
Senior Member

Hi Barys,

WAI-ARIA support is not built into the web client directly, but it is
available as a commercial add-on from EclipseSource. This add-on has
been developed to support UI testing frameworks, but it can also be used
for adding accessibility to RAP applications. However, depending on your
application, some features may still be missing.

Please also note that the SWT accessibility API (Accessible,
AccessibleListener, etc.) is not yet implemented in RAP.

If you're interested in the ARIA add-on, please contact us at
info@xxxxxxxx.

Best Regards,
Ralf

--
Ralf Sternberg

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: Accessibility [message #1244092 is a reply to message #1243797] Tue, 11 February 2014 22:25 Go to previous messageGo to next message
Barys Dubauski is currently offline Barys Dubauski
Messages: 33
Registered: July 2009
Member
Thank you, Ralph. We will look into evaluating the WAI-ARIA commercial addon to see what accessibility violations will it fix for us and how many of them are still around. I'll post updates when I have results.
Re: Accessibility [message #1255814 is a reply to message #1244092] Mon, 24 February 2014 21:11 Go to previous message
Barys Dubauski is currently offline Barys Dubauski
Messages: 33
Registered: July 2009
Member
Unfortunately, WAI-ARIA addon that we've tried in our application didn't fix accessibility violations but instead introduced dozens more since the use of ARIA tags comes with its own set of guidelines/rules. We realize now that the addon was not designed to provide accessibility coverage but was used for UI testing purposes but it was worth a shot.

This puts even more emphasis on Accessibility: implement real Accessibility API for RAP.
Previous Topic:Sash with inner Buttons
Next Topic:Busy Indicator not updated correctly in IE10
Goto Forum:
  


Current Time: Fri Oct 24 15:28:37 GMT 2014

Powered by FUDForum. Page generated in 0.10114 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software