Skip to:
Content

bbPress.org

Opened 10 years ago

Closed 10 years ago

#2866 closed defect (bug) (fixed)

On bbPress setting page. We should use setting field title as a label if we have single input in this section.

Reported by: ankit-k-gupta's profile Ankit K Gupta Owned by: netweb's profile netweb
Milestone: 2.6 Priority: normal
Severity: normal Version: trunk
Component: General - Accessibility Keywords: has-patch
Cc: ankit.himcs@…

Description

On bbPress setting page, title should have label for making the consistency through the admin.

In core WordPress settings, all input field titles have label but in bbPress, input field title doesn't have label.
It is creating the confusion the user, The input fields behavior should be consistent throughout the admin.

Attachments (4)

2866.patch (5.8 KB) - added by Ankit K Gupta 10 years ago.
Path file
WP-Core-settings.gif (147.8 KB) - added by Ankit K Gupta 10 years ago.
Label in Core WP settings
bbPress-settings.gif (129.8 KB) - added by Ankit K Gupta 10 years ago.
Label in bbPress Settings
2866.02.patch (10.9 KB) - added by thebrandonallen 10 years ago.

Download all attachments as: .zip

Change History (8)

@Ankit K Gupta
10 years ago

Path file

@Ankit K Gupta
10 years ago

Label in Core WP settings

@Ankit K Gupta
10 years ago

Label in bbPress Settings

#1 @Ankit K Gupta
10 years ago

  • Keywords has-patch added

This ticket was mentioned in Slack in #bbpress by ankitguptaindia. View the logs.


10 years ago

#3 @thebrandonallen
10 years ago

  • Milestone changed from Awaiting Review to 2.6

@Ankit K Gupta

Thanks for the patch. I've updated the patch to add missing labels for the rest of the settings page.

#4 @netweb
10 years ago

  • Owner set to netweb
  • Resolution set to fixed
  • Status changed from new to closed

In 5948:

Accessibility: Include input labels for field titles in bbPress settings

This changeset aligns bbPress input label fields with current WordPress standard for improved accessibility

Props ankit-k-gupta, thebrandonallen
Fixes #2866

Note: See TracTickets for help on using tickets.