Andrew: Peruse the slides and email comments to the mailing list.
andrew: Updated the document and
added comments from previous meetings
... want to make sure technologies are up to date and are being used. Also ensure scenarios include older users too.
andrew: made some changes to this scenario
william: We don't want to force age into all of the scenarios but this might warrant having an age connection
alan: colour blindness combines two things at once. Colour blind and usage
william: If we have age there it will still cover anybody who is shopping
andrew: And mobility is an issue
for many older people
... though colour blindness is an ageless impairment
alan: They cover one disability per scenario and this one is more about colour blindness
andrew: removed access keys as they are specifically not in WCAG 2 and always been a topic of debate in the community
alan: Should also mention skip-link as this is more relevant. Access keys are only used on sites you use all the time, which fits this scenario. This is also covered by ARIA
william: We could insert a note
about ARIA in this scenario
... We could produce a list of features of Web technologies e.g. ARIA
michael: In this scenario it's appropriate to have access key features but we should focus on Web applications like email
alan: If he submits in HTML then this would assume that he is using a WYSWYG editor which will have access keys
andrew: agrees. We should not mention access keys for Web pages but could still talk about access keys in terms of Web applications
alan: The first paragraph should be changed so that "submit his articles in HTML" should be in the next paragraph
shadi: agrees with Alan and we
should clarify what he is doing to submit HTML.
... Likes the mention of skip links and ARIA.
... We could talk about access keys on Web Authoring tools and how Mr Jones likes ARIA in the page.
michael: ARIA landmarks will probably replace skip links but we should keep skip links as this is a common technique now.
andrew: ARIA is also not a published recommendation, although this may change by the time we have finished the document
alan: Although people are already starting to use ARIA
michael: We can mention ARIA here but don't talk about specific techniques
andrew: In section 5 we could point to ARIA
alan: Say that he uses short cut keys and that this is achieved using ARIA
andrew: previous comments included online media players that support captions.
alan: We could mention that captioned resources are searchable
michael: and also if you have hardware with no audio device then captions will be useful
andrew: or you're working where you can't use audio e.g. library
andrew: Previous comments
included headings and navigation links. Can we combine this
with Michael's suggested scenario?
... asked Sylvia about JAWS and she was interested in adding emphasis on heading navigation and playing down table mark-up, although this is still important for numeric data
andrew: We can maybe talk about input assistance such as filling in forms
shadi: There is a success criteria in WCAG 2 to provide alternative ways of navigation, including search [2.4.5 Multiple Ways], although it's not a requirement that applies to all kinds of Websites. Maybe we could reword this scenario slightly
andrew: We could look at alternative ways of navigation as well that would be a small but relevant change that ties directly to WCAG 2
shadi: agrees with suggestion
andrew: and for people with dyslexia then input assistance could be useful
michael: Input assistance could be helpful for people who have problems with writing and could improve the hit rate of searching.
shadi: We shouldn't focus only on search as input assistance is vital for all types of forms and so we should focus on search and also input assistance from another perspective
andrew: We could put form use in this scenario or try and slot general form use into another scenario. Maybe the next scenario that involves the retiree who is managing finances online
alan: Is it a good idea to say he is a retiree? Many people with age-related problems are not necessarily retired
andrew: Good point and has been
mentioned before. Will make the change in the next round [to 'older person']
... discussed previously that not may older users use screen magnifiers but do magnify the text
andrew: All the features that are mentioned make the site more usable for all customers but we only mention the improvement of usability in this scenario when all the other scenarios improve usability too. Should we draw this out at the start of the scenarios?
Jack: Leave it here and mention it at the start.
alan: It also comes up in the keyboard example with colleagues liking the key-stroke driven editor
andrew: last time discussed the use of mobile devices and going to the movies.
andrew: Civil engineer now mostly
office based. Any thoughts on this scenario?
... Older old person 85+ who is new to computers and the Web. Any thoughts on this scenario?
michael: We should focus more on forms here as she is booking travelling to visit family. e.g. proper labelling, error suggestions and other techniques
andrew: So we shouldn't place emphasis on the online booking aspect
michael: I don't know how realistic this scenario is as we have studies older people on the Web and not sure if people will actually book trips
Shadi: how about social networking?
michael: Information about trains and flights can be difficult for some people.
suzette: Agrees with Michael. We
should focus on the issues of form filling
... so planning travel and not booking it?
william: It's easier to call the
travel company and have somebody do it for you then do it
through the Website
... toll-free numbers are often searched for on websites
andrew: We can put that emphasis
in there. Planning travel and looking at timetables.
... Would also like to bring in social networking somewhere. This could be a good one as she is keeping in contact with family members
andrew: Some people are actively involves in publishing material to the Web so started a scenario that involves a person volunteering at a charity to set up a promotional Website. Any ideas are welcome
andrew: Older female person, about 55, blind since her youth
... could this scenario be combined with the accountant scenario or kept separate
michael: This scenario is based on a real person.
andrew: Could probably stay as a stand alone scenario as there is a lot of unique material in it
suzette: Good scenario with good issues being raised. Can we give it a better contrast with the other blind user scenario. One person having less experience and not being able to read braille so we have a range of impairments
michael: so a person who has become blind more recently and not from birth
suzette: I like that it is based on a real person so we can change the earlier one slightly
william: People who become blind later on tend not to read braille as well as those who learnt as children. Technology has allowed these people to have access to material that used to only be available in braille
shadi: Good point. We can also consider this for deaf people
andrew: How can we change the account scenario to de-emphasise the braille.
suzette: if we re-wrote the accountant we can make them into somebody who has lost functional sight more recently and is being supported by her workplace providing appropriate technologies and so is less experience. She knows her job well but is having to learn how to do it in a different way.
andrew: Any additional thoughts hare on the mailing list.
andrew: Any comments about this
... added comments from previous meeting.
... same for Assistive Technologies and Adaptive Strategies section
andrew: How do we update the
... Need to change from WCAG 1.0 to 2.0. Also references to WAI-ARIA. Should we mention UAAG 1.0 or 2.0?
... Also, add in where appropriate links to the understanding documents.
No Actions[End of minutes]