Coming from#20 in #1493324: Inline form errors for accessibility and UX think we need to add HTML5′s required attribute as well as ARIA’s "aria-required" to FAPI. More references on this and why it is a best practice:

http://www.w3.org/TR/2011/WD-html5-20110525/common-input-element-attribu...
http://www.w3.org/TR/wai-aria/states_and_properties#aria-required

This coming from @feather's articles on required field best practices:
http://simplyaccessible.com/article/required-fields-right/
http://simplyaccessible.com/article/required-form-fields/

And also worth pointing to:
http://www.alistapart.com/articles/aria-and-progressive-enhancement/

Comments

mvc’s picture

mvc
they
Primary language English
Location Montréal, CA
commented
Assigned: Unassigned » mvc
mvc’s picture

mvc
they
Primary language English
Location Montréal, CA
commented
Status: Active » Closed (duplicate)

i think this was resolved already: #1174938: Natively support the HTML5 required and aria-required FAPI properties