Planning/Personas
Summary
- Cedric - Development manager looking to address management concerns
- Hibah - Brand manager keen to instill accessibility in projects
- Jani - Small business owner commissioning accessible website
- Svetla - Keen to address low accessibility awareness
- Matt - Intranet manager reviewing internal systems
- Megumi - Head of Digital Propositions conscious of advantages of accessibility
Questions to consider
These have moved to the Feedback pages.
Tasks
What activities related to accessibility would this person be seeking to do as part of their role?
Needs
The needs section aims to capture the high level information that each of these users require. This can be used to inform the Possible Modules that will be developed.
Characteristics
The aim of the characteristics is to provide a summary of the personas that might be used later in the project when considering alternative user entry points. The characteristics try to cover the range of important factors that might influence what information would be important and at what level it should be delivered. The long term aim is that these may serve as filters for the information to provide a tailored response to the users specified needs.
- Organization size
- Provides an indication of the size of the organisation rated as Small, Medium or Large. This is rather arbitrary in nature as organization size can be rated in a wide range of ways.
- Organizational awareness
- To what extent is the organization aware of accessibility issues.
- Individual awareness
- To what extent is the individual aware of accessibility issues.
- Technical competence
- In terms of how to provide accessible solutions, how competent is the organization. This includes issues associated with design, content and code.
- Influence
- How much influence within the organization does the individual have to elicit change.
- Budget control
- Does the individual manage their own budget or are their significant constraints.
- Technical team location
- Again, technical could cover design, content or code. Are they predominantly In house, Out sourced or a mixed solution?
- Project stage
- Indicates at what stage is the project at. This is a general guide as for some use cases there may be multiple projects.
Cedric - Development manager looking to address management concerns
Cedric is the development manager of a small team of developers within a medium sized organization. He has responsibility for all the team activities. Any design work will be out sourced to a partner design agency but the team usually work from their design guidelines. Cedric recently had a meeting with the board who expressed some concerns about the accessibility of their various sites.
Tasks
- Find out more about what accessibility actually is.
- Create a design briefing incorporating accessibility for design agency.
- Organize accessibility training materials for technical team.
- Understand what the legal risks are associated with accessibility.
Needs
- Introduction to accessibility
- Training resources for technical team
- Quick start to accessibility
- Planning for a staged implementation
- Identifying low hanging fruit
- Developing organizational policy
- Roles that impact on accessibility
- Determining current level of accessibility
- Developing accessible project management processes
Characteristics
- Organization size: Medium
- Organizational awareness: Medium
- Individual awareness: Low
- Technical competence: Medium
- Influence: High
- Budget control: High
- Technical team location: In house
- Project stage: Retrofitting
Hibah - Brand manager keen to instill accessibility in projects
Part of a large organization where she is brand manager for a number of customer facing sites and services. Hibah is aware that accessibility is an important consideration and has tried to instill that in the various projects that she is involved with. She also feels that she will need to convince her management team of the value of accessibility to allow project budgets to extend.
Tasks
- Modify brand guidelines to build accessibility in.
- Prepare a business case for management highlighting the value accessibility brings.
- Communicate accessibility aims and value to wider organization.
Needs
- Accessibility business case
- Building accessibility awareness
- Communicating accessibility
- Quick start to accessibility
- Sharing accessibility knowledge across teams
- Developing organizational policy
- Integrating accessibility into project plan
- Procurement process
- Ongoing accessibility
- Determining current level of accessibility
- Building a cross organization accessibility team
Characteristics
- Organization size: Large
- Organizational awareness: Low
- Individual awareness: Medium
- Technical competence: Low
- Influence: Medium
- Budget control: Medium
- Technical team location: In house
- Project stage: Retrofitting
Jani - Small business owner commissioning accessible website
Jani owns a small business that provides organic and vegan products with a few shops in the city. He wants to have a website developed for him and wants to make sure it will be accessible. He has no knowledge about web development.
Tasks
- Find out what questions he needs to ask developers to ensure they are able to deliver an accessible website.
- Learn how to check for accessibility to confirm developer claims.
- Learn how content should be managed to ensure it stays accessible.
- Understand what to do when some web content isn't accessible.
Needs
- Commissioning accessible websites
- Procurement process
- Creating accessible content
- Roles that impact on accessibility
- Developing organizational policy
- Easy accessibility checks
Characteristics
- Organization size: Small
- Organizational awareness: Low
- Individual awareness: Low
- Technical competence: Low
- Influence: Medium
- Budget control: High
- Technical team location: Out sourced
- Project stage: New site
Svetla - Keen to address low accessibility awareness
Svetla has worked as project manager for a number of years. Having previously implemented a number of sites where accessibility was important, Svetla is comfortable with what is required. She is keen to address the low awareness of accessibility within the organization.
Tasks
- Prepare and communicate an introduction to accessibility resource.
[comment: I don't think we want to encourage people to create new intro resources, and instead use what we provide? {shawn}]
[response to Shawn: I would suggest that these tasks should not represent what we want to or do provide but should reflect what this person is seeking to do. How we go about supporting that or responding to that would be the next step? {kevin}]
[response to Shawn: Changed the word 'create' to 'prepare' to indicate that she may either create or borrow and adapt as needed. {kevin}] - Improve existing project management process to bake in accessibility.
- Develop a knowledge sharing process to spread understanding of accessible solutions throughout organization.
- Identify and assign responsibilities within the team.
Needs
- Commissioning accessible websites
- Procurement process
- Building accessibility awareness
- Sharing accessibility knowledge across teams
- Developing accessible project management processes
- Accessibility business case
Characteristics
- Organization size: Large
- Organizational awareness: Low
- Individual awareness: High
- Technical competence: Low
- Influence: Medium
- Budget control: Low
- Technical team location: In house/Out sourced
- Project stage: New site
Matt - Intranet manager reviewing internal systems
Having newly started as the intranet manager, Matt is aiming to review the existing internal systems to ensure they are fit for purpose. There are a few people on staff with disabilities and quite a few older members of staff. Matt is aware from previous roles that it is important to ensure that they are appropriately supported.
Tasks
- Understand the broad impact of accessibility and legal responsibilities.
- Create a policy to address accessibility of internal systems and tools.
- Identify and prioritize accessibility issues.
- Assess and track accessibility requirements.
Needs
- Procurement process
- Selecting the right management platform
- Introduction to accessibility
- Training resources
- Identifying low hanging fruit
- Developing accessible project management processes
- Determining current level of accessibility
Characteristics
- Organization size: Medium
- Organizational awareness: Low
- Individual awareness: Medium
- Technical competence: Medium
- Influence: Medium
- Budget control: Medium
- Technical team location: In house
- Project stage: Existing
Megumi - Head of Digital Propositions conscious of advantages of accessibility
Megumi is the Head of Digital Propositions. She is responsible for all customer facing web services including mobile applications. She is conscious that providing an accessible site brings advantages beyond the obvious. The board continually need reminding of this and she faces regular difficulties with third party suppliers who fail to prioritize accessibility.
Tasks
- Work with legal department to ensure accessibility is part of technology and design purchasing process.
- Create and track metrics on accessibility improvements and resulting corporate social and financial gains.
- Work with technical, design, and content teams to develop better understanding of accessibility.
Needs
- Commissioning accessible websites
- Procurement process
- Developing accessible project management processes
- Roles that impact on accessibility
- Accessibility business case
- Selecting the right management platform
- Building a cross organization accessibility team
Characteristics
- Organization size: Large
- Organizational awareness: Low
- Individual awareness: Medium
- Technical competence: Low
- Influence: High
- Budget control: High
- Technical team location: In-house/Outsourced
- Project stage: Existing
Redundant use cases
The following originally identified use-cases are considered to be covered adequately by the above:
- Jane is the web team leader at her organization and is passionate about web accessibility. She recently got green light from her management to develop a project and financial plan for making the organizational website (more) accessible.
- getting started
- frequent use case
- may have little experience
- org is in different stage
- James is the project manager for a new website that is about to be launched. He just learned that it has accessibility issues that need to be fixed. He does not know much about web accessibility except that he needs to have it now.
- still a getting started
- difference is: in late development phase, under time constraint
- who has he learned it from and what resources are available to him? if internal, he may be able to find internal resources in his company. If external he needs different support.
- Main point is that WAI resources should also address emergencies.
- Jules maintains a website with high commitment to accessibility. He is concerned that this accomplishment may deteriorate over time as the website evolves and responsible people change. He thinks a formalized policy and plan might help avoid this.
- how to formalize
- Julia is an experienced accessibility consultant who advises organizations on planning and managing accessibility. She wants to know about the advice provided by W3C/WAI to compare notes and make sure she is not missing anything.
- Likely not primary resource but one to be aware (secondary).
- Jack is the webmaster. He gets all the complaints about the website accessibility barriers even though others are equally responsible for them. He wants to know what he can do to get accessibility better managed at his organization.
- Point: Not person most responsible but is the one who gets all the grief.
- May need eval tool, responsibility distribution and management
- In stage just before Jane.
- Juliana will be procuring a web application that will become part of the website that she is responsible for. She wants to know what else she needs to consider besides putting accessibility requirements into the procurement contract.
- Something to consider, address in content, but may not be a separate use case