Working with screen readers

Mobile Forms component renders XFA form template in HTML5 format. All standard browsers supporting HTML5 can render these forms. To support similar data capture experience across PDF and HTML5 forms, the layout of PDF forms is retained in HTML5 forms.

Mobile Forms uses standard HTML constructs allowing regular accessibility tools for HTML to be used with these forms. If a form is designed according to the best practices for accessible forms, it works with any supported screen reader. Additionally, such forms are enabled for keyboard navigation.

Accessibility standards

Mobile Forms comply to section 508 for accessibility with known exceptions. See VPAT for Mobile Forms for details.

Certified screen readers for Mobile Forms

  • JAWS 14.0 on Microsoft Windows
  • VoiceOver on Mac OS X and iPad


All default keystrokes and shortcuts work for Mobile Forms. For more information on using JAWS, visit


Mobile Forms support all the default keystrokes and gestures of Voice over. For more information on setting up and using VoiceOver, see

Known issues

  • (Internal Explorer 9 only) In Mobile Forms, the pages are loaded on demand (dynamically). On-demand page load causes issues with the functioning of screen readers. When focus of the screen reader is on the last field of the page and the user presses tab, instead of setting the focus on the first field of the next page, the screen reader returns focus to the first field of first page of the form. 
  • (Internal Explorer 9 only) The Date Picker control in Mobile Forms is not fully accessible with keyboard. In the Date Picker control, if you press Up/Down keys multiple times, the Date Picker control closes and focus moves to next/last field.
  • VoiceOver is unable to detect arrow keys on the date widget on iPad safari. 
Adobe logo

Sign in to your account