Ticket #6914 (closed enhancement: fixed)

Opened 2 months ago

Last modified 2 months ago

Add ARIA markup for required fields

Reported by: MarcoZ Assigned to: westi
Priority: normal Milestone: 2.6
Component: Administration Version: 2.5.1
Severity: normal Keywords: has-patch
Cc:

Description

Using ARIA (Accessible Rich Internet Applications) markup, it is possible to enhance WordPress' accessibility to indicate the "required" state of certain form fields. This is currently indicated visually through styling, and through adding an abbr with title "required" and a * as plain text. But using ARIA markup, screen readers that support this can do more with explicit state "required" for the form field accessibles, for example play a certain sound or the like.

ARIA is unintrusive: If a browser is used such as IE 7 or Safari, ARIA markup won't interfere, it will simply be ignored. Browsers however, that support the WAI-ARIA markup already, will automatically use the extra information, and as more browsers become available, they'll pick it up automatically as well.

Attachments

wp-6914.diff (11.9 kB) - added by MarcoZ on 05/04/08 16:44:22.
Add aria-required attribute to fields that are styled with the form-required style, or whose required state is indicated by an array parameter.

Change History

05/04/08 16:44:22 changed by MarcoZ

  • attachment wp-6914.diff added.

Add aria-required attribute to fields that are styled with the form-required style, or whose required state is indicated by an array parameter.

05/04/08 16:44:53 changed by MarcoZ

  • keywords set to has-patch.

05/04/08 21:26:19 changed by westi

  • owner changed from anonymous to westi.
  • status changed from new to assigned.

05/04/08 21:28:13 changed by westi

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [7888]) Add ARIA markup for required fields. Fixes #6914 props MarcoZ.

(follow-up: ↓ 5 ) 05/04/08 21:56:14 changed by Nazgul

  • status changed from closed to reopened.
  • resolution deleted.

This breaks XHTML validation.

The attribute "aria-required" is marked as an attribute that is not supported by the document type used. (XHTML 1.0 Transitional)

(in reply to: ↑ 4 ; follow-up: ↓ 6 ) 05/05/08 04:56:14 changed by MarcoZ

Replying to Nazgul:

This breaks XHTML validation. The attribute "aria-required" is marked as an attribute that is not supported by the document type used. (XHTML 1.0 Transitional)

I'm currently trying to find out how to solve this. Will get back asap.

(in reply to: ↑ 5 ) 05/05/08 05:07:14 changed by DD32

Replying to MarcoZ:

Replying to Nazgul:

This breaks XHTML validation. The attribute "aria-required" is marked as an attribute that is not supported by the document type used. (XHTML 1.0 Transitional)

I'm currently trying to find out how to solve this. Will get back asap.

I dont think there is a way to solve it and keep the same Doctype from my quick reading.

Using Namespaces would've solved the XHTML Validation AFAIK, however, They're[Mozilla] not wanting to support that method in FF3.

I personally think its either Break Validation, Or support a not-yet-standard which is implemented by 1 browser. But i admitably havnt looked too far into it.

05/05/08 06:03:21 changed by westi

  • status changed from reopened to closed.
  • resolution set to fixed.
  • component changed from General to Administration.

I think the best solution here is to be ahead of the curve and get better support for screen-readers into WordPress - leading in this area is something we should aspire to.

Reading through the W3C docs it looks like they have identified the validation issue and are working on a solution - http://www.w3.org/TR/wai-aria-primer/#ariahtml

I have opened a new ticket to track the validation issue - #6918