Site map
- Home
- News & events
- News archive
- Events archive
- SEMINAR: "Lifetime Homes in Policy & Practice"
- PRESENTATION: Accessiblity in the Context of the United Nations Convention on the Rights of Persons with Disabilities Transatla
- Seminar: "Better Design through User Participation", with Sean McDougall
- Design in 3rd level and CPD Education incorporating Outcomes Measurement
- 24 Hour Universal Design Challenge
- SEMINAR: Accessible ICT Procurement
- LAUNCH "Achieving Participation through Universal Design"
- Consultation: Curriculum for Training ICT professional in Universal Design
- Seminar-Universal Design in Legislation, Policy and Practice
- Shared Spaces Seminar 2010
- What is Universal Design
- Definition and overview
- Case studies & examples
- 7 Principles of UD
- Benefits and drivers
- 10 things about UD
- Award schemes
- UD Organisations
- History of UD
- Policy and legislation
- Conference Proceedings
- Universal Learning for the 21st Century
- Universal Design in the Irish Context
- Universal Design
- Designing a more Inclusive World
- Universal Learning for the 21st Century
- Designing as a Moral Enterprise: TRIL Researchers Reflect on the Centrality of the Person
- Universal Design in the Built Environment: The Irish Context
- MOSAIC - An Overview
- Supporting Industry in the Development of Design for All (DfA) curriculum
- Universal Learning for the 21st Century
- 24 Hour Universal Design Challenge 2009
- Courses & Teaching
- Guidelines & Standards
- About us
- Built environment
- Products & services
- ICT
- Web accessibility techniques
- Developers
- Content - Section 4
- Design Basics #1 (non technical)
- DEV 1.1 Be consistent throughout
- DEV 1.2 Enhance clarity with good design
- DEV 1.3 Do not convey information with colour alone
- DEV 1.4 Create contrast between foreground and background
- DEV 1.5 Avoid using flashing, flicker and unnecessary animation
- DEV 1.6 Use multimedia with care
- DEV 1.7 Create flexible width design if possible and appropriate
- Design Basics #2 (technical)
- Forms - Section 7
- HTML Coding - Section 5
- DEV 5.1 Include this information at the top
- DEV 5.2 Construct proper headings
- DEV 5.3 Define list and list items properly
- DEV 5.4 Use lang, abbr & acronym to embed useful information
- DEV 5.5 Use structural and semantic markup properly and validate code
- DEV 5.6 Use relative font sizing, not absolute units
- Images - Section 6
- Navigation and Orientation - Section 3
- Tables - Section 8
- Designers
- Design Basics (non technical) - Section 1 (of 6)
- DES 1.1 Be consistent throughout
- DES 1.2 Enhance clarity with good design
- DES 1.3 Do not convey information with colour alone
- DES 1.4 Create contrast between foreground and background
- DES 1.5 Avoid using flashing, flicker and unnecessary animation
- DES 1.6 Use multimedia with care
- DES 1.7 Create flexible width design if possible and appropriate
- DES 1.8 Avoid frames and pop-up windows, and be careful with image maps
- Design Basics (non technical) - Section 1 (of 6)
- Content editors
- Cross reference with web accessibility guidelines
- Content provider's introduction and index
- CP 1 Aim for maximum consistency between content pages
- CP 10 Data tables: simplify and mark up with special HTML
- CP 2 Write specifically for the web - use clear and simple language, provide 'metadata'
- CP 3 Structure and style to maximise readability and scanning
- CP 4 Provide accessible alternatives - don't rely on PDF/Word
- CP 5 Make links meaningful
- CP 6 For all images, specify alternative text to convey equivalent information
- CP 7 Specify full descriptions for informational images
- CP 8 Avoid using images to display text
- CP 9 Use the correct image format for the job
- Designer's introduction and index
- Developer's introduction and index
- Developers
- IT Accessibility Guidelines
- About these guidelines
- Application software
- About Application Software Accessibility
- Guidelines for Application Software Accessibility
- 1.1 Ensure that users have access to the operating system accessibility tools, without affecting application functionality
- 1.10 Ensure a logical tab order for controls, input fields and other objects
- 1.11 Provide descriptions and instructions for all accessibility features
- 1.12 Provide accessible documentation, training and support materials
- 1.2 Ensure compatibility with assistive technologies
- 1.3 Adhere to all user-selected system settings for input and output
- 1.4 Adhere to the standard keyboard access methods
- 1.5 Do not require use of a pointing device
- 1.6 Ensure that all information can be perceived by users with restricted or no vision
- 1.7 Ensure that all information can be perceived by users with restricted or no hearing
- 1.8 Do not cause the screen to flash at a frequency of above 2 Hertz
- 1.9 Use the simplest language possible for instructions, prompts and outputs and, where possible, supplement it with pictorial i
- Guidelines for Application Software Accessibility - Printable Version
- 2.1 Allow sufficient response time to accommodate the slowest users
- 2.2 Ensure that the user interface and task flow is similar across different functions
- 2.3 Adhere to the operating system user interface guidelines
- 2.4 Provide accessible packaging, installation and configuration tools
- 2.5 Provide for users with multiple impairments
- Guidelines for Applications Software - Priority 1
- Guidelines for Applications Software - Priority 2
- Planning and Procurement
- Testing, Assessment and Quality Assurance
- Guidelines for Public Access Terminals Accessibility - Printable Version
- About Public Access Terminals Accessibility
- Guidelines for Public Access Terminals Accessibility
- 2.1 Allow sufficient time to accommodate the slowest users
- 2.2 Ensure that the user interface and task flow is similar across different functions and remains the same across repeated visi
- 2.3 When deploying more than one version of a device, ensure that the user interfaces are similar
- 2.4 Ensure that videophones allow simultaneous text dialogue
- 2.5 Do not require users to remember a fixed supplied PIN
- 2.6 Provide for users with multiple impairments
- Public access terminals
- 1.1 Ensure that all operable parts are reachable by people of all heights and people sitting in a wheelchair or buggy
- 1.10 Use the simplest language possible for instructions, prompts and outputs and, where possible, supplement it with pictorial
- 1.11 If using cards, ensure that the card can be inserted into the card reader in its correct orientation without requiring visi
- 1.12 If using biometric identification, provide an alternative access security mechanism for users who do not possess the requir
- 1.13 Do not cause the screen to flash at a frequency of above 2Hz
- 1.14 When installing the terminal, ensure that users can get to it along an unobstructed path and operate it from a stable posit
- 1.15 Ensure that an equivalent service is available through an accessible channel for users who cannot use the terminal
- 1.2 Ensure that displays are within sight of people of all heights and people sitting in a wheelchair or buggy
- 1.3 Ensure that controls are adequately sized and sufficiently spaced to be operated by people with limited dexterity
- 1.4 Ensure that operation requires minimal strength, grip and wrist twisting
- 1.5 Ensure that the terminal can be operated using only one hand
- 1.6 If using a touchscreen or contact-sensitive controls, do not require that it is touched by a body part
- 1.7 Ensure that users with restricted or no vision can use all functions of the terminal
- 1.8 Ensure that all outputs can be perceived by users with restricted or no vision
- 1.9 Ensure that all outputs can be perceived by users with restricted or no hearing
- Public access terminals - Priority 1
- 2.1 Allow sufficient time to accommodate the slowest users
- 2.2 Provide a way for the user to cancel the whole transaction at any point and retrieve any items they have inserted
- 2.3 Ensure that the user interface and task flow is similar across different functions and remains the same across repeated visi
- 2.4 When deploying more than one version of a terminal, ensure that the user interfaces are similar
- 2.5 Do not require users to remember a fixed supplied PIN
- 2.6 Provide for users with multiple impairments
- 2.7 Provide training or assistance for new users
- 2.8 Ensure privacy and security during use
- Public access terminals - Priority 2
- Smart cards
- Guidelines for Smart Card Accessibility
- About Smart Card Accessibility
- About Smart Cards
- Making Smart Card Services Accessible
- Telecoms
- Design and Development
- Guidelines for Telecoms Accessibility - Printable Version
- Guidelines for Telecoms Accessibility - Priority 1
- 1.1 Ensure that all operable parts are reachable by people of all heights and people sitting in a wheelchair or buggy
- 1.10 Ensure compatibility with assistive technologies
- 1.11 If using telephone cards, ensure that the card can be inserted into the card reader in its correct orientation without requ
- 1.12 Use the simplest language possible for instructions and outputs and, in visual displays, supplement it with pictorial infor
- 1.13 Do not cause the display to flash at a frequency of above 2Hz
- 1.14 Ensure that users can get to the device along an unobstructed path and operate it from a stable position
- 1.15 For Interactive Voice Response (IVR) systems, provide an equivalent service through an accessible channel
- 1.2 Ensure that displays are within sight of people of all heights and people sitting in a wheelchair or buggy
- 1.3 Ensure that controls are adequately sized and sufficiently spaced to be operated by people with limited dexterity
- 1.4 Ensure that operation requires minimal strength, grip and wrist twisting
- 1.5 Ensure that the device can be operated using only one hand
- 1.6 Ensure that users with restricted or no vision can use all functions of the device
- 1.7 Ensure that all outputs under the control of the device can be perceived by users with restricted or no vision
- 1.8 Ensure that videophones provide accurate reproduction of text and sign language
- 1.9 Ensure that all outputs under the control of the device can be perceived by users with restricted or no hearing
- Guidelines for Telecoms Accessibility - Priority 2
- Web
- About Web Accessibility
- Design and development
- Guidelines for Web Accessibility
- Guidelines for Web Accessibility - Priority 1
- 1.1 Provide a text equivalent for every non-text element
- 1.10 For complex data tables, use mark-up to associate data cells and header cells
- 1.11 Add titles to frames
- 1.12 Ensure that documents can be read without style sheets
- 1.13 Provide text links to emulate server-side image maps
- 1.14 Use client-side image maps rather than server-side image maps where possible
- 1.15 Ensure that scripts and applets that provide the only source of important functionality are directly accessible or compatib
- 1.16 Ensure that pages are usable without support for scripts, applets, or other programmatic objects
- 1.17 If you cannot make a page accessible, provide an equivalent accessible page
- 1.2 Ensure that information does not rely on colour perception
- 1.3 Avoid causing the screen to flicker
- 1.4 Provide an auditory description of the visual information in multimedia presentations
- 1.5 For multimedia, ensure that timing of alternative descriptions is synchronised with the presentation
- 1.6 Use the clearest and simplest language appropriate
- 1.7 Identify language changes in text
- 1.8 Ensure that equivalents for dynamic content are updated when the dynamic content changes
- 1.9 For data tables, identify row and column headers
- Guidelines for Web Accessibility - Printable Version
- 2.1 Ensure that images have sufficient contrast for people with colour deficient vision
- 2.10 Do not use structural mark-up to format information laid out using tables
- 2.11 Describe the purpose of frames and how they relate to each other if it is not obvious by their titles alone
- 2.12 Clearly identify the target of each link
- 2.13 Provide information about pages and sites in metadata
- 2.14 Provide information about the general layout of a site
- 2.15 Use navigation mechanisms consistently
- 2.16 Associate labels explicitly with their controls
- 2.17 Properly position the labels of form controls
- 2.18 Ensure that user interfaces are device-independent
- 2.19 Use logical event handlers in scripts
- 2.2 Avoid causing content to blink
- 2.20 Use input device-independent event handlers in scripts and applets
- 2.21 Ensure that scripts and applets are accessible
- 2.22 When an appropriate markup language exists, use markup rather than images to convey information
- 2.23 Create documents that validate to published formal grammars
- 2.24 Mark up lists and list items using the proper HTML tags
- 2.25 Use quotation mark-up for quotations, but not for formatting
- 2.26 Where possible, use appropriate W3C technologies of the latest supported versions
- 2.27 Avoid deprecated features of W3C technologies
- 2.28 Do not periodically auto-refresh pages
- 2.29 Do not use mark-up to redirect pages automatically
- 2.3 Avoid movement in content
- 2.30 Do not generate pop-ups or other windows and do not change the current window without informing the user
- 2.4 Ensure that dynamic content is accessible or provide an alternative presentation or page
- 2.5 Use style sheets to control layout and presentation
- 2.6 Use relative rather than absolute units
- 2.7 Use header elements to convey structure
- 2.8 Break up large blocks of information where appropriate
- 2.9 Ensure that information laid out using tables make sense when linearised, or provide an alternative equivalent
- Guidelines for Web Accessibility - Priority 2
- 3.1 Ensure that text and background have sufficient contrast for people with colour deficient vision
- 3.10 Provide a linear alternative for parallel, word-wrapped columns of text
- 3.11 Create a logical tab order through links, form controls, and objects
- 3.12 Provide keyboard shortcuts to important links, form controls, and groups of form controls
- 3.13 Separate adjacent links with non-link, printable characters surrounded by spaces
- 3.14 Provide navigation bars
- 3.15 If search functions are provided, enable different types of searches for different skill levels and preferences
- 3.16 Provide information about documents comprising multiple pages
- 3.17 Provide a means to skip over multi-line ASCII art
- 3.18 Create a style of presentation that is consistent across pages
- 3.19 Include default text in form text boxes
- 3.2 Provide text links to emulate client-side image maps
- 3.20 Provide information to enable users to receive documents according to their preferences
- 3.3 Expand the first occurrence of any abbreviation or acronym
- 3.4 Identify the primary language of the document text
- 3.5 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
- 3.6 Supplement text with graphic or auditory presentations where they will facilitate comprehension
- 3.7 Provide summaries for tables
- 3.8 Provide abbreviations for table header labels
- 3.9 Identify groups of related links and provide a way to bypass them
- Guidelines for Web Accessibility - Priority 3
- Guidelines for Web Accessibility - Priority 1
- Planning and procurement
- Testing checklist for Web Accessibility
- Testing, Assessment and Quality Assurance
- Web accessibility auditing
- IT Procurement Toolkit
- Universal Design for ICT
- Web accessibility techniques
