- Compliance; Quality Assurance; Impersonal
- Instead: Accessibility as User Experience
- Custom widgets (Google Maps) - Customized controls not available in html. Problem: voice recognition/keyboard tabbing does not recognize map controls. Ironfeathers.ca customized controls to allow this using button element (div onClick to buttononClick).; remember mouse/keyboard interaction.
- Inline editing - Requires fewer page refreshes, changing on the fly; Problem: requires mouse to expose controls. Flickr has solution (link).
- Live updates - Updates without refreshing. In some cases more accessible. Problem: (Twitter) Character count is always displayed (screen reader problems), how do we notify user update has occurred?
- Tree menus -
- Error/Advisory information - Each field has a label; some fields have additional info; errors/advisory info needs to be near the control to which it relates.
- Form linearization - Often we translate visual layout and effects into our code. Reconsider code to take into account intent and design. 1. Search field 2. Radio buttons 3. Search button.
- Search Results - Results are often below the fold; Repetition of the form can confuse people that have a limited view of the page; Many diff page elements require a mechanism to move around the page. Solution: submit form to name anchor or id.
- We need to translate the visual language that designers created to something meaningful in code.
- Nested lists for hierarchy/groupings.
Use alt tags! Label fields!
furtherahead.com
boxofchocolates.ca
ironfeathers.ca
No comments:
Post a Comment