[
https://issues.apache.org/jira/browse/TRINIDAD-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated TRINIDAD-62:
-------------------------------
Resolution: Fixed
Fix Version/s: 1.0.2-core
Assignee: Danny Robinson
Status: Resolved (was: Patch Available)
Checked in patch.
> Use of screen-reader accessibility mode should force client-side validation
> to use alerts
> -----------------------------------------------------------------------------------------
>
> Key: TRINIDAD-62
> URL: https://issues.apache.org/jira/browse/TRINIDAD-62
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.0.1-core
> Reporter: Danny Robinson
> Assignee: Danny Robinson
> Fix For: 1.0.2-core
>
> Attachments: ForceAlertValidationInScreenReaderMode.patch,
> ForceAlertValidationInScreenReaderMode.patch
>
>
> Snipped from emails between Adam and Gabrielle
> > > I'd very much like to switch the default validation mechanism
> > > from ALERT to INLINE, as I think that's the "killer feature"
> > > for this release.
> >
> > has this has any accessibility testing?
> >
> >
> > Good point - it hasn't. We should consider forcing
> > alerts when in screen reader mode, and it'd be good to have
> > some accessibility testing otherwise.
> Personally I think forcing alerts in screen reader mode should be fine for
> 1.0.1. Hopefully that's easy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
