giving sap-accessibility=X from page a to page x ?

[daniel_humberg]

I recently came across the nice "sap-accessibility=X" - feature in HTMLB Design 2003, that peope use to get additionaly accessibility features.

My problem: when users call pageA.htm and add "?sap-accessibility=x" manually, how do I pass the parameter to all the pages that are called. If i just call navigation->goto_page( 'pageX.htm' ), the parameter would be gone.

Of course, I could check at every page change if the parameter is set and pass the parameter to the next page, but isn't there an easier way? Furthermore, there are more parameters like sap_xxx=x, right?

[former_member181879 · Accepted solution]

The sap-accessibility is mangled into the url as parameter 'a'. Once set, it sticks. The important aspect is that you must (as always) start the application with an unmangled URL.

Given such an URL, you can use BSP application DECODE to see that the attribute is actually set on any page.

As long as your navigation is with relative URLs, it will stick.

[former_member181879]

<i>Furthermore, there are more parameters like sap_xxx=x, right?</i>

Yes, there are a number more. You can try sap-rtl for fun, and sap-send-us-cookies=BAC-G5.01 to improve the handling of your OSS messages.

[thomas_jung]

This can also be set using the RUNTIME (IF_BSP_RUNTIME) object method SET_ACCESSIBILITY.

[daniel_humberg]

Thanks Thomas.

Do you know a simple test without a screen-reader to check if accessibility-features are really switched on on a HTMLB page?

[thomasalexander_ritter]

The runtime class has the method WITH_ACCESSIBILITY which tells you if accessibility is switched on.

[thomas_jung]

As stated you can check the value in code with the WITH_ACCESSIBILITY method. However if you are looking for visible signs that accessibility is turned on without having a screen reader, I can give you some hints. The main one I look for is the tool tips on buttons, links, tabs, etc. If accessibility is properly set, you should see a change in the tool tips. I assume this is information that the screen reader can process. For instance, the tool tip on my tab strip changes to: <b>Page Welcome selected</b> or <b>Page Events and News press spacebar to select</b>. On buttons I get a tooltip like the following: <b>Pushbutton Sumbit, To Activate, use spacebar</b>. These extra navigation descriptions are the main signs that I have noticed.

[thomasalexander_ritter]

Write this before you call the goto_page() method:

navigation->set_parameter( name = 'sap-accessibility' value = 'X' ).

Upps sorry didn't read the whole post. But I didn't find some sort of global flag either.

Message was edited by: Thomas Ritter