Related Topics
Accessibility Principle 4 – Robust
This principle relates to making content robust enough to be interpreted by a wide variety of user agents, including assistive technologies.
Guideline 4.1 – Compatible
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing
Level A - In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements don't contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
This is a core feature of Process Director; however, designers must also ensure that the use of HTML controls uses raw HTML that is similarly parsable within the DOM.
4.1.2 Name, Role, Value
Level A - For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
This is a core feature of Process Director.
Tables manually inserted into a Form should have the Role attribute set appropriately, as outlined in the Online Form Designer topic.
4.1.3 Status Messages
Level AA - In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
This is a core feature of Process Director. Designer-configured status messages, such as validation errors, are always included in the existing, text-based, messaging system, which never received focus when error or other status messages are displayed.
Other Accessibility Principles
Principle 1 - Perceivable: This principle relates to making information and user interface components presentable to users in ways they can perceive.
Principle 2 - Operable: This principle relates to how user interface components and navigation operate.
Principle 3 - Understandable: This principle relates to making information and the operation of the user interface understandable to users.
Documentation Feedback and Questions
If you notice some way that this document can be improved, we're happy to hear your suggestions. Similarly, if you can't find an answer you're looking for, ask it via feedback. Simply click on the button below to provide us with your feedback or ask a question. Please remember, though, that not every issue can be addressed through documentation. So, if you have a specific technical issue with Process Director, please open a support ticket.