How To Fix FPCHKACC103 - Static text with/out alternative text has wrong Screen Reader precedence

SAP Error Message - Details

• Message type: E = Error

• Message class: FPCHKACC - Usability messages for FP internal use only

• Message number: 103

• Message text: Static text with/out alternative text has wrong Screen Reader precedence

What causes this issue?

Static text with/out an alternative text must never have the Screen
Reader precedence set to Name. Setting to Name will cause Screen Reader
to read only the technical name instead of the static text itself or the
alternative text (if maintained).

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

The following changes can be performed automatically right on the form
design. To do this, run the update with the Template Updater and then
select the appropriate update item.
The static text with/out alternative text will have its Screen Reader
precedence be set to Custom text.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FPCHKACC103 - Static text with/out alternative text has wrong Screen Reader precedence ?

  The SAP error message FPCHKACC103 indicates an accessibility issue related to the use of static text in a user interface. This error typically arises when the screen reader precedence of static text elements is not set correctly, which can hinder users who rely on assistive technologies from understanding the content properly.
  Cause:
  The error is caused by the improper configuration of static text elements in the SAP application. Specifically, it occurs when:
  
  Static text elements do not have the correct accessibility attributes.
  The order of elements is not logical for screen readers, leading to confusion for users with visual impairments.
  Alternative text is missing or not properly associated with the static text.
  
  Solution:
  To resolve the FPCHKACC103 error, you can take the following steps:
  
  
  Review Static Text Elements: Check the properties of the static text elements in your SAP application. Ensure that they are correctly labeled and that their purpose is clear.
  
  
  Set Accessibility Attributes: Ensure that all static text elements have appropriate accessibility attributes. This may include:
  
  Using the aria-label or aria-labelledby attributes to provide context.
  Ensuring that the text is descriptive enough for users who rely on screen readers.
  
  
  
  Logical Order: Ensure that the order of static text elements follows a logical sequence that makes sense for screen reader users. The reading order should match the visual layout of the application.
  
  
  Alternative Text: If static text is used in conjunction with images or icons, ensure that alternative text is provided. This helps screen reader users understand the context of the static text.
  
  
  Testing: After making changes, test the application with a screen reader to ensure that the static text is read in the correct order and that it provides the necessary context.
  
  
  Consult Accessibility Guidelines: Refer to accessibility guidelines such as the Web Content Accessibility Guidelines (WCAG) to ensure compliance with best practices.
  
  
  Related Information:
  
  SAP Accessibility Guidelines: SAP provides guidelines and best practices for developing accessible applications. Familiarizing yourself with these can help prevent similar issues in the future.
  Screen Reader Tools: Familiarize yourself with popular screen reader tools (e.g., JAWS, NVDA) to understand how they interpret static text and other UI elements.
  Training and Resources: Consider training for developers and designers on accessibility best practices to ensure that future applications are built with accessibility in mind.
  
  By addressing the issues highlighted by the FPCHKACC103 error message, you can improve the accessibility of your SAP application and ensure a better user experience for all users, including those with disabilities.