Accessibility Issue in Post Content Field (Discussion MFE)

Description:
The Post Content field is implemented using an iframe. This approach causes accessibility issues:

• Screen Reader Compatibility:

  • JAWS does not recognize a label for the iframe's edit area.
  • NVDA does recognize a label, but the overall implementation is inconsistent.

• Implementation Concerns:

  • The current iframe does not use a standard <input> or <textarea>, which limits the use of important ARIA attributes like aria-label, aria-invalid, and aria-describedby.
  • As a result, users relying on screen readers may have difficulty understanding and interacting with the field.

Recommendation:

• At minimum, add the aria-invalid attribute to the post content field when it is left empty.
• Ideally, replace the iframe with a proper <textarea> element that includes:
  • aria-label to describe the field,
  • aria-invalid to indicate errors,
  • aria-describedby linked to error messages for better context.

Action Needed:

• Implement aria-invalid on the post content field to improve accessibility for screen readers.

Post Content fields

Start by locating the Post Content iframe implementation in frontend-app-discussions and inspect how its empty-field state and validation errors are handled. Verify the result with a screen reader or the project's existing accessibility checks. Done means the empty post content field exposes aria-invalid and its error context remains understandable to screen-reader users.