Entering content frame

Function documentation Accessibility Locate the document in its SAP Library structure

Use

The Accessibility Guidelines (Section 508) established in many countries are intended to enable partially sighted users to use software interfaces. In general, all texts on an interface are read out using an external tool, provided that all screen elements, such as symbols, pushbuttons and so on have been assigned quick infos.

In the context of BSP applications, you can use BSP extensions HTMLB, XHTMLB and PHTMLB to structure interfaces with the Tag Browser.

Caution

In particular, you should think about accessibility with BSP applications that contain tables, tabstrips and tree controls. These three types of interface elements are not always easy for Screen Reader to read out.

Integration

When developing BSP applications, you can specify whether or not you want to follow the accessibility rules.

The accessibility specification is integrated in the BSP runtime:

...

       1.      Specify the accessibility in the following URL:

...?sap-accessibility=X

Defining the accessibility is also part of the new system logon for SAP Web AS 6.40 SP2.

       2.      Query the accessibility in the BSP runtime:

runtime->with_accessibility( ) = 'X'
Accessibility is activated.

runtime->with_accessibility( ) = ''
Accessibility is not activated.

This option sets an internal flag in the BSP runtime, which can be used by BSP applications to output additional information in the HTML output stream, so that screen reader programs can better present the visual information on the screen.

BSP extensions HTMLB, XHTMLB und PHTMLB use this flag to change its rendering behavior.

These parameters are not used after the logon.

Caution

Note that setting this indicator does not make any statement about that application’s accessibility. The indicator merely indicates that additional help is required for that application.

 

 

Leaving content frame