Advice on the use of fieldsets in the new Update page

[hope]

Hi, dw_accessibility!

fu and I have been working on building the next version of the update page redesign, and making sure our markup is as accessible as possible.

With that in mind, we have a question with regards to the use of fieldsets that we hope you can help us with.


As you can see from the first mockup, the Update page is basically one big form, soon to have many more form elements added to it, grouped together in what fu and I have been calling "components".

For example, there is the grouping of the subject field and entry textarea, and the "Currents" component that comprises the select menu for mood, music text field, and location text field.

As far as fu and I can see, there are two options for the use of fieldsets on this page, detailed below:


Mockup 1: the form uses a single fieldset. The legend is the title of the page, and all form items occur in a useful order within the fieldset. The title of each component uses heading markup, e.g. <h3>


Mockup 2: the page contains multiple fieldsets. Each component has a fieldset of its own, and the title of each component is marked up as a legend.

So, our question is - which use of fieldsets is the most accessible to you, mockup 1 or 2? Or do you have a suggestion for a different use? Feedback is gladly welcomed :)

Thanks!

Update: This news post links to a live version of Mockup 1.

Comments

[codeman38]

Just found a keyboard accessibility issue with the new update page.

In the tags box, enter two tags, and then try to delete them with the backspace key. After deletion, the focus doesn't return to the entry box-- and the second backspace may even be caught by the browser as the keyboard shortcut for "back"!