Henning Nöth created TOBAGO-2535:
------------------------------------

             Summary: Aria label for message button
                 Key: TOBAGO-2535
                 URL: https://issues.apache.org/jira/browse/TOBAGO-2535
             Project: MyFaces Tobago
          Issue Type: Bug
          Components: Core
    Affects Versions: 6.11.0
            Reporter: Henning Nöth


If a info/warning/error Faces message has the ID for a specific component, a 
message button appears on this component (if configured).

This message button don't have an ARIA label.

A common case is if a required input field is submitted without being filled 
out. A "Validation Error: Value is required" message appears. This message has 
the severity "Error". Given that a label is set for the input field, for 
example "super important input field", the ARIA label should have the text 
"Show error message for super important input field". If no label is set, the 
ARIA label should be "Show error message".

The severity of a FacesMessage could be INFO, WARN, ERROR and FATAL.
There is alread a translation for this:
severity.fatal=Fatal
severity.error=Error
severity.warn=Warning
severity.info=Information


It is possible, multiple FacesMessages are set for a component. The message 
button has the color of the highest severity.
If an information and a warning FacesMessage is set, the color of the message 
button is yellow/orange and the ARIA label should be "Show warning message for 
...".
If a warning and a fatal FacesMessage is set, the color of the message button 
is red and the ARIA label should be "Show fatal message for ...".


I've been wondering if it would be better to implement a sophisticated ARIA 
label like "Show 2 information messages and 1 fatal message for ...", but I 
think it's sufficiant to just use the highes severity.


The FacesMessage.Severity severity attribute for the 
DecorationPositionRendererBase.encodeFacesMessagePopover() method is already 
the highest severity.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to