Showing results for 
Search instead for 
Did you mean: 

BSP and Accessibility

Former Member
0 Kudos

I have a BSP Application using som plain html and htmlb. I am now trying to make my BSP application accessible.

What I found out up to this day:

You can use the 'BspAccessibility' and 'sap-accessibility'. The documentation at this point is a little bit confusing.

Here are my questions:

1.) If you set ?sap-accessibility=X in the URL you can use this parameter in the BSP runtime. So this parameter should be used, when creating an accessibility switch in applications? In my understanding with this parameter it is only possible to define the whole application as accessible or not. Is it possible to use it inidivually when log on like the next parameter.

2.) There is another parameter called BspAccessibility which can be set in SICF. You can also show this flag when using redirect to URL in SICF. Then you can set it individually for each logon. When this parameter is set, the htmlb changes its rendering behaviour: What does that exactly mean?

3.) Does this parameter have any impcat on the other parameter?

4.) Why are there two accessibility flags?

I would appreciate if anybody could give me more information about how making my BSP application accessible.


Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hello Daniel,

to make your handwritten html accessible consider the following link:



Active Contributor
0 Kudos


First I would recommend that you look at OSS/CSS note 517860. In the attachments tab, there is a 20 page document. This will explain it all.

Funny, Ulli asked my exactly the same questions. Now I understand why. So let me answer in short form again.

BspAccessibility is just one flag that is used to configure the SYSTEM logon application. This flag just tells the logon application, that during the time it is running, it must also offer a checkbox for the user to request additional accesibility help during rendering. This parameter plays NO role after login.

If that checkbox above is set, or if an application is started with sap-accessibility=X in the URL, the BSP runtime will pick up this flag, and make it internally available to the BSP application. This flag makes ZERO comments on the capabilities of the BSP application. All that this flag does, is tell the application additional help is required.

The BSP rendering libraries (HTMLB, XHTMLB & PHTMLB) does look whether this flag is set. If it is set, they do render out additional information to into the HTML stream. This is usually much more control over tabbing, plus much more detailed information in the tooltips, so that screen reading programs can read the content of the screen.

If you develop your own handwritten HTML code, then of course you should look during the runtime if this flag is set, and consider to render out additional help. A typical example: for a checkbox, the tooltip is extended with the current checked/unchecked state of the checkbox.

> "information about how making my BSP application"

All the information we have, was learned via a SAP University course. Maybe you can get internally a copy of the course material. I think that with this, and the referenced documentation, you should be able to place the four questions above into perspective. I am sorry, but we can not help you to make handwritten HTML code accessible. If you use our rendering libraries, you should be ok.