FW: Proposed ROLE values to support WCAG 2.0 validation and AT user interface enhancements

Jon,

no I speak generally of Warning and Info states related to messages that appear anywhere on UI.
I think we have to decouple thinking from concrete examples here.
Warnings and Infos are in IDE’s for ages and Web-based Business Software makes extensive use of them, too.
Even the platform API’s support the different states (e.g. MSAA: alert_high, alert_low).
Frankly, I don’t want to sell a Warning as an Error just to be WCAG2-compliant.
People will feel confused and needless discussions may be caused.

For me the gap is within WCAG 2.0 Success Criteria (because it still doesn’t address all needs of Web-based Business Software)
but ARIA is there to close gaps, so I think we’re really along  the same lines.

Best Regards
Stefan

From: Gunderson, Jon R [mailto:jongund@illinois.edu]
Sent: Dienstag, 25. November 2014 21:30
To: Schnabel, Stefan; W3C WAI Protocols & Formats
Subject: RE: Proposed ROLE values to support WCAG 2.0 validation and AT user interface enhancements

Stefan,

I am interested in roles that could directly relate to WCAG 2.0 Success Criteria, I am not sure WCAG 2.0 has requirements for warnings, although they could be considered a type of error and the INFO role seems a little to generic, but I am assuming you mean the INFO icons near controls, these to me might be considered instructions.

But I think we are both thinking along the same lines,
Jon

From: Schnabel, Stefan [mailto:stefan.schnabel@sap.com]
Sent: Tuesday, November 25, 2014 2:04 AM
To: Gunderson, Jon R; W3C WAI Protocols & Formats
Subject: RE: Proposed ROLE values to support WCAG 2.0 validation and AT user interface enhancements

Jon,

some comments:

ROLE=”INSTRUCTIONS”

I second having that since we really need to announce in place typed instructions,. e.g.  for keyboard usage of custom elements.
But: Isn’t this a role equivalent to aria-help / aria-hint property?

ROLE=”ERROR”

Why just error, why not WARNING or INFO, too?

Best Regards
Stefan


From: Gunderson, Jon R [mailto:jongund@illinois.edu]
Sent: Montag, 24. November 2014 19:32
To: W3C WAI Protocols & Formats
Subject: Proposed ROLE values to support WCAG 2.0 validation and AT user interface enhancements

I would like to propose the following ARIA roles to help identify key features of a web page related to WCAG 2.0 success criteria.

The roles can be used by web accessibility evaluation tools to validate conformance and can help ATs identify certain types of information on a web page for meeting certain WCAG 2.0 requirements and improving the user experience of identify WCAG 2.0 required features.

Jon


============================================
ROLE=”MEDIA-ALTERNATIVE”

Marks a block of text as being a  media alternative for video or audio content.

Related to WCAG 2.0 Success Criteria
1.2.1
1.2.2
1.2.3

Example:

<audio aria-describedby=”id1”>

<div id=”id1” role=”media-alternative”>
<h2>Text Transcript</h2>

…..

</div>

============================================
ROLE=”INSTRUCTIONS”

Marks a block of text as being instructions for a form control or widget.

Related to WCAG 2.0 Success Criteria
3.3.2

Example:

<textarea aria-describedby=”id2”>

<div id=”id2” role=”instructions”>
<h2>Instructions</h2>

…..

</div>

============================================
ROLE=”ERROR”

Marks a block of text as being error information for a form control or widget.

Related to WCAG 2.0 Success Criteria
3.3.1
3.3.3
3.3.4

Example:

<input type=”date” aria-describedby=”id3”>

<div role=”alert”>
<span id=”id3” role=”error”>Invalid date, use YYYY-MM-DD format<span>
</div>