Formz javascript validation for modx manual#
Formz javascript validation for modx full#

The visual focus indicator on keyboard focus is either non-existent in some places or too hard to see.good, intuitive error recovery mechanisms.simplicity in the visual design, organization, processes, etc.Users with cognitive disabilities (including common reading disorders, ADD, and others) need:.easily visible :focus styles (some people cannot use a mouse at all, so they need to know where the keyboard focus is at all times).

Formz javascript validation for modx full#

full keyboard functionality (see above under blind users).Transcripts and captions for audio/visual content (not an issue with MODx manager).information presented in a way that does not depend on color.easily visible :focus styles, and preferably :hover styles too.good document structure (headings, table headers, lists, landmark regions).focus management with dynamic content such as error/feedback messages, dynamically-loaded AJAX content, etc.full keyboard accessibility of all functionality, including drop-down menus, tool-tips, tab lists, modals, etc.Background Information About Web Accessibility There are other issues too, but the above issues are pervasive and need to be addressed broadly across the MODx manager. Without a label or text alternative, screen readers have nothing to read, so users don't know what the elements are. Every active element (links, buttons, etc.) and every important image-like element (graphics and font icons) needs a text label or a text alternative.The keyboard focus needs to follow the action of dynamic scripts (modal windows, form validation, etc.).Many of the dynamic widgets (tablists, multi-select lists, etc.) need to be enhanced with ARIA attributes and ARIA-style keyboard patterns to enable effective screen reader interaction. It also makes it impossible for sighted keyboard users who can't use a mouse, perhaps because they have tremors in their hands, or have no hands and user a mouth stick, or they have another similar condition. This makes it impossible for blind screen reader users to use, because the mouse is not useful to someone who can't see where to click it. There are many, many places in the MODx manager where a mouse is required.This evaluation is still incomplete, but some trends have emerged: Government entities, in particular, would be legally at risk if they decided to use MODx because of the non-compliance of the manager interface with web accessibility guidelines. Background Information about Web AccessibilityĪccessibility to people with disabilities is critical not only for the individuals with disabilities themselves - who currently cannot use the MODx manager - but also for companies hoping to use MODx.

Formz javascript validation for modx manual#

Web Accessibility To-Do List for MODx Manager Web Accessibility To-Do List for MODx ManagerĮvaluation by Paul Bohman using automated tools such as FireEyes/WorldSpace by Deque, Wave by WebAIM, but mostly this is a manual evaluation comparing the actions of the web site against the Web Content Accessibility Guidelines 2.0 and web accessibility best practices.