http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #1 from Tom Houlker <thomas.houlker@hibs.school.nz> --- Created attachment 24432 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24432&action=edit updated the accessability of opac-passwd.tt http://bugs.koha-community.org/show_bug.cgi?id=11558 -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #3 from Emma Heath <emmaheath.student@wegc.school.nz> --- Created attachment 24434 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24434&action=edit Bug 11566: Fixing accesssibility on OPAC in opac-memberentry.tt Removed unnecessary fieldset around save button -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #5 from Merllissia Manueli <manuelimel@gmail.com> --- Created attachment 24436 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24436&action=edit Improved accessibility by removing <fieldset> tags as they were unnecessary. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #7 from Merllissia Manueli <manuelimel@gmail.com> --- Created attachment 24438 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24438&action=edit Improving Accessability of privacy page by adding <legend> tags -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #9 from Emma Heath <emmaheath.student@wegc.school.nz> --- Comment on attachment 24434 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24434 Bug 11566: Fixing accesssibility on OPAC in opac-memberentry.tt Review of attachment 24434: --> (http://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=11566&attachment=24434) ----------------------------------------------------------------- *submit button -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #11 from Owen Leonard <oleonard@myacpl.org> --- (In reply to Aleisha Amohia from comment #2)

Removed unnecessary fieldset around Submit button

I assume these patches are based on recommendations that a fieldset not be used without a corresponding <legend>. In this case the fieldset is being used as a somewhat-semantic grouping element in order to provide a logical hook for CSS. Removing the fieldset doesn't solve any accessibility problem in my opinion. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 Marc Véron <veron@veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |veron@veron.ch --- Comment #13 from Marc Véron <veron@veron.ch> --- The first patch does not apply: CONFLICT (content): Merge conflict in koha-tmpl/opac-tmpl/bootstrap/css/opac.css Failed to merge in the changes. Patch failed at 0001 updated the accessability of opac-passwd.tt There seems to be no need to alter opac.css, the patch does not contain substantial changes for it, and the patch introduces a CSS error (stray word 'browsers'). -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #14 from Marc Véron <veron@veron.ch> --- (In reply to Owen Leonard from comment #11)

(In reply to Aleisha Amohia from comment #2)

...

Removed unnecessary fieldset around Submit button

I assume these patches are based on recommendations that a fieldset not be used without a corresponding <legend>. In this case the fieldset is being used as a somewhat-semantic grouping element in order to provide a logical hook for CSS. Removing the fieldset doesn't solve any accessibility problem in my opinion.

I did some research on the use of fieldsets: "Fieldset and legend should only be used to associate groups of controls when a higher level description (i.e., the legend) is necessary. Single checkboxes or basic radio buttons (such as male/female for gender) that make sense from their labels alone do not require fieldset and legend. Nested fieldsets should generally be avoided." Source: http://webaim.org/techniques/forms/controls "There are [in addition to radio or check boxes, MV] other use cases, and in general the <fieldset> element can also be used to strongly section a form. Because of its influence over assistive technology, the <fieldset> element is one of the key elements to building accessible forms; however it is your responsibility not to abuse it. If possible, each time you build a form, try to listen to how a screen reader interprets it. If it sounds odd, it's a good hint that your form structure need to be improved." Source: https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Forms/How_to_structu... My conclusion: If I look now at the results of http://wave.webaim.org/ for e.g. .../cgi-bin/koha/opac-memberentry.pl, it does not complain about fieldset tags around single controls (e.g. Submit button). It only complains about a missing legend for it. However, the fieldset has a style: <fieldset class="action"> This style used in opac.css: fieldset.action { border: 0 none; clear: both; float: none; margin: 0; padding: 1em 0 0.3em; width: auto; } Simply removing the fieldset tag would have an impact on the look and feel of the website. So in my opinion it is better to be very careful about removing tags and rather to add a legend where the validator complains about missing legends (as some of the patches do). -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11566 --- Comment #16 from Owen Leonard <oleonard@myacpl.org> --- (In reply to Marc Véron from comment #14)

So in my opinion it is better to be very careful about removing tags and rather to add a legend where the validator complains about missing legends

I think we need to use our best judgement in situations where a validator complains. Is the lack of a legend on the fieldset around a submit button really an accessibility problem, or is it just an item on a checklist? -- You are receiving this mail because: You are watching all bug changes.