Requirements/Analysis and Changelog for WAI-AGE Articles
General Notes
Overall purpose
Promote the findings and deliverables from the WAI-AGE project through a series of articles that target managers, developers and users respectively. These articles are envisaged to be such that they could be reproduced by other publications.
Format proposal
- a 750-word main article, with 2x125 word side-bars
- a 200-word mini article version
- a 50-word "availability" message, inviting editors to use the drop-in articles (with credit, etc).
Managers - business case article
Purpose
To present business case oriented material with an emphasis on older people in a long and a short article that can be reproduced by other publishers.
Audience
- Primary
- decision makers; site owners; commercial policy people; project managers
- Secondary
- developers; advocates
Tone
- business-ey
- formal
Key messages
- older people increasingly important market
- older people develop impairments
- accessibility works for older people as well as people with disabilities
- accessibility has broader benefits
- some orgs are getting positive return on investment (ROI)
Title options
- Older People Benefit from Web Accessibility
- Why Web Accessibility is Important
- Web Accessibility Pays Dividends for Older People
- Reaching Older users with your Web Business
Changelog:
EOWG Discussions
Changes 27 Sept 2010
- addessed considerations from EOWG 17/Sept
- modified Introductory para
- added references to Stats & Quotes in the Managers' article
Original content working notes:
Distribution possibilities
- AGE & EDF newsletters
- Headstar enewsletter
- IFA (International Federation on Ageing) - at least a pointer
- AARP
Base material:
Content ideas:
- statistics (minimal)
- b/case arguments
- quotes from the business case appendix (as call outs?)
Content details:
-
EU older population (over 65) to increase from 17% of total population to 29% in next 40 years
- Typically over 50% of population over 65yrs experiences age-related impairments that are classified as disabilities – hearing loss, vision decline, physical decline, cognitive decline
- Older users are an increasing market segment and an important target group for many businesses, governments, and other organizations
- Workplace - many EU countries are currently raising the retirement age and people are also choosing to work longer
- Community - increasing the ability for people to participate economically, civically and socially, and to age in place
- The Web provides older people with unprecedented opportunities
- Older people are experiencing a variety of web accessibility barriers
- Organizations can realize substantial ROI with accessible websites, including benefiting from better SEO, reduced legal risk, demonstration of CSR, and increased customer loyalty
- Corporate Social Responsibility (eg Legal & General? Providing “Access to our products and services in a variety of ways, enabling customers to choose the one best suited to them.” (PDF) And “Our customers are at the centre of our strategy. Our priority is to provide them with good value products, quality service and a choice of ways to buy through a wide range of distribution channels … We will always look for ways to improve the quality of our service.” )
- B/case – access for older people and other groups (http://www.w3.org/WAI/bcase/soc.html#groups)
- B/case – easier to maintain (http://www.w3.org/WAI/bcase/tech.html#maint & eg L&G )
- B/case – better SEO (http://www.w3.org/WAI/bcase/fin.html#increase-use, http://www.w3.org/WAI/bcase/resources.html#seo & eg L&G again)
- B/case – more visitors (http://www.w3.org/WAI/bcase/fin.html#increase-use & http://www.w3.org/WAI/bcase/resources.html#cases)
- B/case – legal and policy conformance (http://www.w3.org/WAI/bcase/pol.html)
Developers - "what developers can do" article
Purpose
To present primarily technical accessibility material along with user involvement oriented material to give "how to" with a few brief arguments about why developers should implement accessibility. The emphasis should be on older people's needs in long and short articles that can be reproduced by other publishers.
Audience:
- Primary
- developers
- Secondary
- trainers and educators (tertiary level + industry)
- purchasers/procurers
Tone:
- developer-y
- factual
- instructive
Messaging:
- accessibility makes sites more usable for older people
- older people with impairments have similar requirements to PWD
- WCAG 2 is the answer
- WCAG 2 application can be optimised for older audience
- additional benefits of accessibility (mobile, SEO, maintenance, ??)
- get older people (users) involved early
Title options:
- Optimising websites for older users
- Developing websites for older people
- Older people require acessibility too
- Websites that Work for Older People
Changelog:
EOWG Discussions
Changes Sept 2010
- considered TF discussion
- Notes:
- needs more concrete material
- needs to use BAD for illustration of requirements/solutions
Original content working notes:
Distribution possibilities:
- bloggers? - Chris Heilmann, Roger Johansson, Sitepoint, etc
- lists? e.g. WSG, WebDev, etc
- Headstar newsletters
Material:
- Developing websites for older users
- slides (WAI-AGE + WCAG 2.0)
- BAD - as example
- Involving Users in Web Projects for Better, Easier Accessibility
Content ideas:
- BAD to demonstrate that no/minimal difference in look'n'feel and functionality
- importance of WCAG 2.0 techniques
- ?? 10 top SC for older users (could be dangerous though)
- involve users (early and in evaluation)
- evaluation?
Content notes:
- Older users are an increasing market segment and an important target group for many businesses, governments, and other organizations
- EU over 65 pop'n to increase from 20% by 2020; Japan to 30% by 2020
- Typically over 50% of population over 65yrs experiences age-related impairments that are classified as disabilities – hearing loss, vision decline, physical decline, cognitive decline
- many of them experience multiple impairments
- can't address just one need and say "done"
- Older people are online - 30% of 65+ in UK in 2009; 27% of 75+ in US in 2008 (presentation)
- Older people tend not to use assistive technologies, but do employ adaptive strategies
- WCAG 2.0 meets the accessibility needs of older people
- equates to many of their usability needs
- Some techniques more applicable to older people than other techniques due to
- impairments experienced
- adoption of adaptive strategies
- Getting users (older people) involved in web projects will provide insights and additional benefits
- studies have also shown that [accommodating] older people's needs doesn't disadvantage other users
Users - adaptive strategies article
Purpose
To present material about adataptive strategies particularly relevant to older people and how to contact organizations with inaccessibles website in casual long and short articles that can be reproduced by other publishers.
Audience:
- Primary
- end-users in general
- older peoples' organizations
- trainers and supporters
- Secondary
- IT support people
Tone:
- really practical & friendly
- relaxed
Messaging:
- the web can be easy to use
- people browse the web in different ways
- adjustments make life easier
- if it doesn't work, tell them!
Title options:
- Get better web browsing
- Improve your web experience
- Getting more out of the web
Changelog:
EOWG Discussions
Changes Sept 2010
- incorporated TF discussion
- Notes:
- still very drafty with editor's notes
- switches between end user and other in who is being addressed
- 'problems' needs switching to a positive spin
Original content working notes:
Distribution possibilities:
- AGE newsletter
- National older-peoples orgs
- AGE-UK
- Age Action Ireland
- Others with translation
- EDF newsletter
- Ability magazine
- IFA (International Federation on Ageing) - at least a pointer
- Eseniors.eu
Base material:
Content ideas:
- impairments and barriers
- selected (most useful? / most used?) solutions
- if you find it's broke - complain
Content details:
- quick fact about growth in older people online to give encouragement
- summarise types of impairments to get connection "that's me"
- consider summary of what older are are doing on line (UK & US reports)
- avoid term 'disability' - at least early on
- summarise features of a good website (POUR)
- outline a few varied adaptive strategies & point to 'BWB' document (draft)
- explain that everyone should be able to use the web
- summarise the steps to complain & point to 'contacting' document
Background from WAI-AGE Deliverables
- Rationale
- The extent of coverage of the needs of older users in traditional and new media can be enhanced by provision of sample story material.
- Proposal
- This resource would be a set of at least three articles, paralleling some of the revised and new resources but in a story-line and/or blogging format, and addressing different aspects of the business case and user requirements of older Web users. Possible topics could include: “Is your organization meeting the needs of older Web users?” or “What role does usability play for older users with accessibility needs?