How To Fix FPCHKACC100 - Table cell field without caption 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: 100

• Message text: Table cell field without caption has wrong Screen Reader precedence

What causes this issue?

If a table has a visible header and a field in the table body cell has
no caption nor an alternative text, the Screen Reader precedence must be
set to None. Otherwise, the technical name will be read by the Screen
reader.

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.
If the table has a visible header and the field in the body cell has no
caption nor an alternative text, the Screen Reader precedence has to be
set to None.

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 FPCHKACC100 - Table cell field without caption has wrong Screen Reader precedence ?

  The SAP error message FPCHKACC100 indicates an accessibility issue related to the use of screen readers in SAP applications. Specifically, it points out that a table cell field does not have a caption and has an incorrect precedence for screen readers. This can affect users who rely on assistive technologies to navigate and interact with the application.
  Cause:
  The error typically arises when:
  
  A table cell (or field) is missing an associated label or caption, which is essential for screen readers to provide context to users.
  The screen reader precedence is not set correctly, meaning that the order in which elements are read by the screen reader does not align with the visual layout of the application.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Add Captions/Labels:
  
  Ensure that every table cell or field has an associated label or caption. This can be done by using the appropriate HTML tags or SAP UI5 controls that support accessibility.
  For example, use the aria-label or aria-labelledby attributes to provide a descriptive label for the table cell.
  
  
  
  Check Screen Reader Precedence:
  
  Review the order of elements in the DOM (Document Object Model) to ensure that they are structured logically. The visual order should match the reading order for screen readers.
  Use tools like the Accessibility Checker in SAP or browser developer tools to inspect the accessibility tree and ensure that the elements are in the correct order.
  
  
  
  Testing:
  
  After making changes, test the application with a screen reader (such as JAWS, NVDA, or VoiceOver) to ensure that the changes have resolved the issue and that the application is now accessible.
  
  
  
  Consult Documentation:
  
  Refer to SAP's accessibility guidelines and best practices for developing accessible applications. This can provide additional insights into how to structure your UI components correctly.
  
  
  
  Related Information:
  
  SAP Accessibility Guidelines: SAP provides documentation on how to create accessible applications, which can be found on the SAP Help Portal.
  Screen Reader Tools: Familiarize yourself with popular screen readers and their functionalities to better understand how users interact with your application.
  SAP Community: Engage with the SAP Community for discussions and solutions related to accessibility issues in SAP applications.
  
  By addressing the issues highlighted by the FPCHKACC100 error message, you can improve the accessibility of your SAP application, making it more usable for individuals who rely on assistive technologies.