Jaws表单字段视图制表字段异常：JAWS 2018部分表单字段无法读取

Hey there! Sorry to hear you're having trouble with JAWS 2018 when using Insert + F5 to view forms—those unreadable, indented fields can be super frustrating. Let's walk through some practical fixes to get this sorted:

• Check JAWS Form View Settings
  Open the JAWS menu with Insert + F2, navigate to Settings > Forms, and look for options related to field indentation or form recognition. Try adjusting the indent level slider or resetting the form view configuration to default. Sometimes custom indent settings can cause JAWS to misinterpret field boundaries.

• Verify Webpage Accessibility Markup
  A lot of the time, this issue stems from poorly formatted HTML. Use JAWS' Insert + F6 to switch to the element list and inspect those problematic fields, or open your browser's dev tools (F12) to check:

  • Do fields have proper <label> elements associated with them?
  • Are there any CSS styles (like excessive padding/margin) that are pushing fields out of JAWS' detection range?
  • Are ARIA attributes (like aria-label or aria-labelledby) correctly implemented for dynamic fields?

• Tweak JAWS Voice & Language Configurations
  Sometimes language-specific voice packs can have bugs with form field parsing. Try switching to JAWS' default English voice temporarily to see if the fields become readable. You can also check under Settings > Voice > Form Field Processing to ensure all form recognition features are enabled.

• Reset JAWS Configuration Files
  Customized JAWS settings might be causing conflicts. Open the Configuration Manager via Insert + F2 > Configuration Manager, then select Restore Defaults to reset your profile. After resetting, test the Insert + F5 form view again to see if the issue clears up.

• Test Across Different Browsers
  JAWS 2018 has varying compatibility with modern browsers. Try testing the form in IE11 (which had tighter integration with older JAWS versions) or an older Chrome release—if the problem only occurs in one browser, it's likely a browser-JAWS compatibility quirk.

If none of these fixes work, keep in mind that JAWS 2018 is a fairly old version, and this might be a known bug that's been resolved in newer releases. If upgrading is an option, that could be a long-term solution. Otherwise, reaching out to the webpage's developer to fix accessibility markup would be the next step.

内容的提问来源于stack exchange，提问作者Harry L Respass