Skip to:
Content

Opened 5 years ago

Last modified 4 years ago

#2636 new defect

Accessibility: Template Forms - Fieldset

Reported by: netweb Owned by:
Milestone: 2.8 Priority: normal
Severity: normal Version:
Component: General - Accessibility Keywords:
Cc:

Description

via Karl Groves bbPress Accessibility Feedback https://gist.github.com/ntwb/c8f99df8a714ed028e2d

Fieldset is generally best reserved for cases where you need to disambiguate sets of similarly named fields and/ or where clarification of the label is need. Perfect use cases would be shipping address vs. billing address.

Screen readers usually read the legend before each label. So, for instance:

"Create New Topic in “Developers – General” [pause] Topic Title (Maximum Length: 80)"

This is pretty verbose and, in this case, not necessary, because it is pretty obvious what the purpose of the form is.

A heading is better:

<h2>Create New Topic in “Developers – General”</h2>

Current:

<form id="new-post" name="new-post" method="post" action="http://wp-test:8888/forums/forum/test/">
    <fieldset class="bbp-form">
        <legend>
            Create New Topic in “test”
        </legend>
...

Change History (2)

#1 @johnjamesjacoby
4 years ago

  • Component changed from Theme Compatability to Accessibility
  • Milestone changed from Awaiting Review to 2.7

Bumping to 2.7 so we can clear out Awaiting Review and 2.6 milestones.

#2 @johnjamesjacoby
4 years ago

  • Milestone changed from 2.7 to 2.8

Bumping all 2.7 to 2.8 milestone.

Note: See TracTickets for help on using tickets.