Slides for a workshop session on "BS 8878: Systematic Approaches to Documenting Web Accessibility Policies and Practices" facilitated by Brian Kelly at the IWMW 2015 event held at Edge Hill University, Ormskirk on 27 July 2015.
See http://iwmw.org/iwmw2015/talks/systematic-approaches-to-documenting-web-accessibility-policies-and-practices/
How BS8878 relates to WCAG 2.0, PAS 78, Mandate 376 and UCD Standards
An updated summary of BS8878 from its lead author, Jonathan Hassell. Including: how it relates to international standards on accessibility (WCAG 2.0 and ISO 9241-210), usability and user-centred design; and how it allows you to embed accessibility concerns into production processes.
It also provides information on how the Standard updates the older PAS 78 UK specification that it supersedes, and how it relates to work on the forthcoming EU accessibility procurement standard Mandate-376.
More information, including case studies of organisations using BS 8878, detailed blogs on its use by SMEs, tools and training for applying the Standard, and news on its progress towards becoming an International Standard can be found at
http://www.hassellinclusion.com/bs8878/
The Internet Society works to promote an open and globally connected Internet through technology development, policy engagement, and operational best practices. It founded the Internet Engineering Task Force (IETF) and runs programs like Deploy360 and Best Current Operational Practices (BCOP) to help operators deploy new technologies and standards. A recent survey found that while many operators are interested in IETF standards work, they face challenges like lack of time and travel budgets in directly engaging with or influencing the IETF process. The Internet Society aims to address these issues and facilitate more communication between operators and the IETF.
Slides from the 14th August 2019 webinar presentation as part of the Best Practices for HPC Software Developers (Webinar) series - https://ideas-productivity.org/events/hpc-best-practices-webinars/ - more info at https://www.exascaleproject.org/event/smp-rp/ and a recording on YouTube is at - https://www.youtube.com/watch?v=7sELeZStzdY&feature=youtu.be
Abstract:
Software is a necessary by-product of research. Software in this context can range from small shell scripts to complex and layered software ecosystems. Dealing with software as a first class citizen at the time of grant formulation is aided by the development of a Software Management Plan (SMP). An SMP can help to formalize a set of structures and goals that ensure your software is accessible and reusable in the short, medium and long term. SMP’s aim at becoming for software what Data Management Plans (DMP’s) have become for research data (DMP’s are mandatory for National Science Foundation grants). This webinar takes you through the questions you should consider when developing a Software Management Plan, how to manage the implementation of the plan, and some of the current motivation driving discussion in this area of research management.
The document summarizes the key points of the British Standard BS8878 for accessibility of web products. It discusses the context and history that led to the creation of the standard, including the need for an updated British standard to address modern web uses. It then summarizes the main sections and recommendations of BS8878 for planning, designing, and maintaining accessible web products through their entire lifecycle.
This document discusses web accessibility and the challenges of implementing accessibility standards. It summarizes key aspects of web accessibility including:
- Laws requiring public websites to comply with accessibility standards
- The WCAG 2.0 guidelines which define principles, guidelines, and success criteria for accessible websites
- Tools like WAI-ARIA that add attributes to make websites accessible to assistive technologies
- A study that measured developers' awareness and use of accessibility standards, finding only partial compliance and awareness
- Challenges to wider adoption including lack of awareness, unclear responsibilities, and perceptions that standards are too time-consuming
Complementing Accessibility Standards with Evidence of Commitment and Progres...
Improving web accessibility can be challenging, particularly for organizations with large, complex digital estates and internal organizational structures. Efforts can be guided by technical standards, but there are shortcomings with treating accessibility for people with disabilities as a compliance effort. What if we take a process-oriented approach to accessibility, focusing on making a commitment and demonstrating progress? In this session we explore an approach to improving digital accessibility that places value on conscious, pragmatic decision-making and sharing of evidence of progress.
Presented as part of Inclusive Design 24 (#ID24), May 21, 2015: http://www.inclusivedesign24.org.
This presentation discusses technical product management. It summarizes a past BI product implementation for British Telecom that analyzed network usage. It also identifies three disruptive trends over the next five years: analytics, speed, and agility. Finally, it discusses three code coverage tools, the steps to build a successful product roadmap, and important checkpoints for constructing a product roadmap.
Access interrupted? How changes in browser technology may impact researchers'...
This document discusses how upcoming changes in browser technology aimed at improving user privacy could impact researchers' access to scholarly resources through federated authentication. The SeamlessAccess coalition is working to support continued identity federation by engaging with browser vendors, testing new proposed technologies like Federated Credentials Management, and raising awareness of these changes within the academic community. Resources are provided on understanding these changes and their potential effects.
The document outlines the WorldSkills Occupational Standards for Web Technologies. It details 7 sections that make up the standards, including work organization, communication skills, website design, layout, front-end development, back-end development, and content management systems. Each section lists the knowledge and skills required of an individual in that area. The standards provide a framework for the skill competition and reflect international best practices in web development.
KMWorld 2010_Building an Intranet Governance Strategy - Busch and Wahl_201011...
The document outlines an intranet governance strategy, including defining intranet governance, establishing a governance team, and developing policies. It discusses establishing a governance team charter that defines the team's scope, structure, and objectives. The team would include core members from IT, HR, and communications, as well as an extended team of content approvers. Job descriptions are provided for executive sponsors, a team lead, and core and extended team members. Content lifecycle and archiving policies are also part of developing an effective intranet governance strategy.
This document provides an introduction to cloud storage and summarizes a presentation on the topic. It discusses the history of storage systems and how cloud storage works. Popular cloud storage services like Google Drive, Dropbox, and iCloud are examined. The document outlines some risks of cloud storage like security and privacy issues. It also provides a framework for selecting cloud services and questions to consider regarding purposes, benefits, costs and risks.
BS8878 is a UK national standard created by the British Standards Institution to provide a framework for making digital accessibility and inclusion "business as usual" within organizations. It was created in response to changing technological, political, and legal landscapes to promote digital inclusion. The standard was written by industry professionals and disability organizations and offers guidelines for assigning responsibilities, creating policies, evaluating accessibility, and maintaining websites over their lifecycles to be accessible to all. While focused on UK law and culture, the core principles of BS8878 can be applied internationally.
Managing the Process of Providing an Inclusive Institutional Web Presence: Wo...David Sloan
Slides to support a workshop given at the 2012 Institutional Web Managers' Workshop (IWMW 2012), Edinburgh, June 19. The workshop focus was on institutional web accessibility policy, and the potential that British Standard 8878 may have in developing and strengthening accessibility policy.
Case studies of implementing BS 8878 (CSUN 2012)Jonathan Hassell
Why is embedding web accessibility into your organisation's culture and processes so important? And what do organisations who have done this using BS 8878 say are the benefits? In this presentation Jonathan Hassell, the Standard's lead-author, answers these questions and poses one of his own: should BS 8878 become an International Standard, and if so, how?
How BS8878 relates to WCAG 2.0, PAS 78, Mandate 376 and UCD StandardsJonathan Hassell
An updated summary of BS8878 from its lead author, Jonathan Hassell. Including: how it relates to international standards on accessibility (WCAG 2.0 and ISO 9241-210), usability and user-centred design; and how it allows you to embed accessibility concerns into production processes.
It also provides information on how the Standard updates the older PAS 78 UK specification that it supersedes, and how it relates to work on the forthcoming EU accessibility procurement standard Mandate-376.
More information, including case studies of organisations using BS 8878, detailed blogs on its use by SMEs, tools and training for applying the Standard, and news on its progress towards becoming an International Standard can be found at
http://www.hassellinclusion.com/bs8878/
The Internet Society works to promote an open and globally connected Internet through technology development, policy engagement, and operational best practices. It founded the Internet Engineering Task Force (IETF) and runs programs like Deploy360 and Best Current Operational Practices (BCOP) to help operators deploy new technologies and standards. A recent survey found that while many operators are interested in IETF standards work, they face challenges like lack of time and travel budgets in directly engaging with or influencing the IETF process. The Internet Society aims to address these issues and facilitate more communication between operators and the IETF.
Software management plans in research softwareShoaib Sufi
Slides from the 14th August 2019 webinar presentation as part of the Best Practices for HPC Software Developers (Webinar) series - https://ideas-productivity.org/events/hpc-best-practices-webinars/ - more info at https://www.exascaleproject.org/event/smp-rp/ and a recording on YouTube is at - https://www.youtube.com/watch?v=7sELeZStzdY&feature=youtu.be
Abstract:
Software is a necessary by-product of research. Software in this context can range from small shell scripts to complex and layered software ecosystems. Dealing with software as a first class citizen at the time of grant formulation is aided by the development of a Software Management Plan (SMP). An SMP can help to formalize a set of structures and goals that ensure your software is accessible and reusable in the short, medium and long term. SMP’s aim at becoming for software what Data Management Plans (DMP’s) have become for research data (DMP’s are mandatory for National Science Foundation grants). This webinar takes you through the questions you should consider when developing a Software Management Plan, how to manage the implementation of the plan, and some of the current motivation driving discussion in this area of research management.
The document summarizes the key points of the British Standard BS8878 for accessibility of web products. It discusses the context and history that led to the creation of the standard, including the need for an updated British standard to address modern web uses. It then summarizes the main sections and recommendations of BS8878 for planning, designing, and maintaining accessible web products through their entire lifecycle.
This document discusses web accessibility and the challenges of implementing accessibility standards. It summarizes key aspects of web accessibility including:
- Laws requiring public websites to comply with accessibility standards
- The WCAG 2.0 guidelines which define principles, guidelines, and success criteria for accessible websites
- Tools like WAI-ARIA that add attributes to make websites accessible to assistive technologies
- A study that measured developers' awareness and use of accessibility standards, finding only partial compliance and awareness
- Challenges to wider adoption including lack of awareness, unclear responsibilities, and perceptions that standards are too time-consuming
Complementing Accessibility Standards with Evidence of Commitment and Progres...Sarah Horton
Improving web accessibility can be challenging, particularly for organizations with large, complex digital estates and internal organizational structures. Efforts can be guided by technical standards, but there are shortcomings with treating accessibility for people with disabilities as a compliance effort. What if we take a process-oriented approach to accessibility, focusing on making a commitment and demonstrating progress? In this session we explore an approach to improving digital accessibility that places value on conscious, pragmatic decision-making and sharing of evidence of progress.
Presented as part of Inclusive Design 24 (#ID24), May 21, 2015: http://www.inclusivedesign24.org.
This presentation discusses technical product management. It summarizes a past BI product implementation for British Telecom that analyzed network usage. It also identifies three disruptive trends over the next five years: analytics, speed, and agility. Finally, it discusses three code coverage tools, the steps to build a successful product roadmap, and important checkpoints for constructing a product roadmap.
Access interrupted? How changes in browser technology may impact researchers'...OpenAthens
This document discusses how upcoming changes in browser technology aimed at improving user privacy could impact researchers' access to scholarly resources through federated authentication. The SeamlessAccess coalition is working to support continued identity federation by engaging with browser vendors, testing new proposed technologies like Federated Credentials Management, and raising awareness of these changes within the academic community. Resources are provided on understanding these changes and their potential effects.
The document outlines the WorldSkills Occupational Standards for Web Technologies. It details 7 sections that make up the standards, including work organization, communication skills, website design, layout, front-end development, back-end development, and content management systems. Each section lists the knowledge and skills required of an individual in that area. The standards provide a framework for the skill competition and reflect international best practices in web development.
KMWorld 2010_Building an Intranet Governance Strategy - Busch and Wahl_201011...andinieldananty
The document outlines an intranet governance strategy, including defining intranet governance, establishing a governance team, and developing policies. It discusses establishing a governance team charter that defines the team's scope, structure, and objectives. The team would include core members from IT, HR, and communications, as well as an extended team of content approvers. Job descriptions are provided for executive sponsors, a team lead, and core and extended team members. Content lifecycle and archiving policies are also part of developing an effective intranet governance strategy.
Similar to BS 8878: Systematic Approaches to Documenting Web Accessibility Policies and Practices (20)
This document provides an introduction to cloud storage and summarizes a presentation on the topic. It discusses the history of storage systems and how cloud storage works. Popular cloud storage services like Google Drive, Dropbox, and iCloud are examined. The document outlines some risks of cloud storage like security and privacy issues. It also provides a framework for selecting cloud services and questions to consider regarding purposes, benefits, costs and risks.
This document provides the agenda and brief technical tips for Wyld Morris Zoom Meeting No. 7, which is a new members evening that will include welcoming new potential members, learning about morris dancing from the squire, understanding the basic moves, and perspectives from a new dancer on why they enjoy morris dancing. The technical tips explain how to switch between speaker and gallery view and how to pin a video to focus on one participant.
The document provides information about an online meeting of the Wyld Morris group who enjoy morris dancing and singing. It outlines that the group will continue enjoying their interests during lockdown, support each other, and be even better when they next meet in person. The meeting agenda includes introductions, warm-ups, demonstrations, group dancing and music, an open discussion, and tips for using Zoom including muting audio when not speaking and only having one musician unmuted at a time. Links to online dance instruction videos and resources are also provided.
Predicting and Preparing For Emerging Learning Technologieslisbk
The document summarizes Brian Kelly's presentation on predicting and preparing for emerging learning technologies. It discusses identifying technology trends, drivers, and challenges through the Delphi process used by the NMC Horizon Report. It also provides tools and methods for institutions to plan for future technologies, including scenario planning, acknowledging risks, and engaging with challenges. The presentation aims to help attendees understand limitations of future forecasting and apply similar methodologies to plan locally.
Web Preservation, or Managing your Organisation’s Online Presence After the O...lisbk
Slides for talk on "Web Preservation, or Managing your Organisation’s Online Presence After the Organisation Ceases to Exist" given by Brian Kelly, UK Web Focus at the IRMS 2016 conference in Brighton on 17 May 2016.
See http://ukwebfocus.com/events/irms-2016-web-preservation
This document provides a summary and conclusions from a workshop on "Preparing for the Future: Technological Challenges and Beyond". It recaps the workshop which explored tools for thinking differently about the future, used a Delphi process to gather expert opinions, and developed an action brief planning template. It notes limitations in approaches and the importance of acknowledging risks while also learning from past examples. Contact details and additional resources are provided for those interested in further information.
This document discusses making a case to senior management for funding to explore innovative technologies. It provides guidance on identifying implications, risks, and risk management strategies for new technologies. It also presents an action brief statement template to convince management of a technology's potential benefits. The document concludes with an exercise where attendees in groups prepare a short presentation making a case for funding to investigate one technology.
This document discusses scenario planning as a strategic planning method. It describes the scenario planning process, which involves defining assumptions and drivers of change, developing initial scenarios, and identifying issues. The document then provides examples of scenarios for the library sector, including the effects of UK withdrawal from the EU or greater power for the European Court. Small groups are asked to develop scenarios focusing on alternative discovery sources, changed librarian roles, or other topics. Finally, the document summarizes scenarios developed in a previous workshop on commercialization of libraries, devolved ownership of services, universal skills, and niche librarians.
Slides "D1: The NMC Methodology" for a one-day workshop on "Preparing for the Future: Technological Challenges and Beyond" by Brian Kelly and Tony Hirst at the ILI 2015 conference. Held on Monday 19 October 2015
For further information see
http://ukwebfocus.com/events/ili-2015-preparing-for-the-future
Slides "C1: Future Technology Detecting Tools & Techniques" for a one-day workshop on "Preparing for the Future: Technological Challenges and Beyond" by Brian Kelly and Tony Hirst at the ILI 2015 conference. Held on Monday 19 October 2015
See http://ukwebfocus.com/events/ili-2015-preparing-for-the-future
This document discusses exploring emerging technologies. It provides information on discovering new technologies through peers, publications, experts, and online sources. The document outlines the ILI 2015 conference program and highlights some topics that may be relevant or surprising. It also describes the NMC Horizon Report, which is produced by an international community of experts and identifies important emerging technologies for libraries through a refined expert panel process. The conclusion emphasizes the importance of exploring emerging technologies through various approaches, but also understanding the wider context for implications and planning.
Preparing for the Future: Technological Challenges and Beyond A1 Introductionlisbk
Slides "A1 Introduction" for a one-day workshop on "Preparing for the Future: Technological Challenges and Beyond" by Brian Kelly and Tony Hirst at the ILI 2015 conference. Held on Monday 19 October 2015.
For further information seehttp://ukwebfocus.com/events/ili-2015-preparing-for-the-future
Slides for a talk on "Digital Life Beyond The Institution" given by Brian Kelly, UK Web Focus at the MmIT 2015 conference on “With Power Comes Great Responsibility – How Librarians can Harness the Power of Social Media for the Benefit of its Users” at the University of Sheffield on 14-15 September 2015.
See http://ukwebfocus.com/events/mmit-2015-digital-life-beyond-the-institution/
Developing an Ethical Approach to Using Wikipedia as the Front Matter to all ...lisbk
Slides for a talk on "Developing an Ethical Approach to Using Wikipedia as the Front Matter to all Research" given by Brian Kelly, UK Web Focus Ltd. at the Wikipedia Science 2015 conference at The Wellcome Trust, London on 3 September 2015.
See http://ukwebfocus.com/events/an-ethical-approach-to-using-wikipedia-as-the-front-matter-to-research/
Slides for a talk on "The Agile University" presented by Niall Lavery and Dan Babington, PwC at the IWMW 2015 event held at Edge Hill University, Ormskirk on 27-29 July 2015.
See http://iwmw.org/iwmw2015/talks/beyond-digital-the-agile-university/
This document provides information about the IWMW 2015 conference taking place from July 27-29 at Edge Hill University in Ormskirk. The conference theme is "Beyond Digital: Transforming the Institution" and will feature talks, workshops and master classes on digital transformation in higher education. Over the three days, participants can learn new skills, engage with peers, and identify new approaches for their institutions. Social events include a conference dinner and opportunities to explore Ormskirk and meet up in local bars and restaurants.
Preparing Our Users For Digital Life Beyond the Institutionlisbk
Sides for a talk on "Digital Life Beyond the Institution" given by Brian Kelly, Innovation Advocate at Cetis, University of Bolton at a seminar for the iSchool, University of Northumbria on 11 February 2015.
See https://ukwebfocus.wordpress.com/events/digital-life-beyond-the-institution/
Why and how librarians should engage with Wikipedialisbk
Slides for a talk on "Why and How Librarians Should Engage With Wikipedia" given by Brian Kelly, Innovation Advocate at Cetis, University of Bolton at the CILIPS Autumn Gathering 2014 event in Edinburgh on 30 October 2014.
See http://ukwebfocus.wordpress.com/events/why-and-how-librarians-should-engage-with-wikipedia/
Slides for a talk on "Working with Wikimedia Serbia" given by Brian Kelly, Innovation Advocate at Cetis, University of Bolton at the Eduwiki 2014 conference in Edinburgh on Friday 31 October 2013.
See https://ukwebfocus.wordpress.com/events/eduwiki-2014/
Major Technology Trends that will Impact Library Services?lisbk
Slides for talk on "What are the Major Technology Trends that will Impact Library Services and their Users?" to be given by Brian Kelly, Innovation Advocate, Cetis at the ILI 2014 conference in London on 21-22 October 2014.
See http://ukwebfocus.wordpress.com/events/ili-2014/
How to Configure Time Off Types in Odoo 17Celine George
Now we can take look into how to configure time off types in odoo 17 through this slide. Time-off types are used to grant or request different types of leave. Only then the authorities will have a clear view or a clear understanding of what kind of leave the employee is taking.
(T.L.E.) Agriculture: Essentials of GardeningMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏.𝟎)-𝐅𝐢𝐧𝐚𝐥𝐬
Lesson Outcome:
-Students will understand the basics of gardening, including the importance of soil, water, and sunlight for plant growth. They will learn to identify and use essential gardening tools, plant seeds, and seedlings properly, and manage common garden pests using eco-friendly methods.
Is Email Marketing Really Effective In 2024?Rakesh Jalan
Slide 1
Is Email Marketing Really Effective in 2024?
Yes, Email Marketing is still a great method for direct marketing.
Slide 2
In this article we will cover:
- What is Email Marketing?
- Pros and cons of Email Marketing.
- Tools available for Email Marketing.
- Ways to make Email Marketing effective.
Slide 3
What Is Email Marketing?
Using email to contact customers is called Email Marketing. It's a quiet and effective communication method. Mastering it can significantly boost business. In digital marketing, two long-term assets are your website and your email list. Social media apps may change, but your website and email list remain constant.
Slide 4
Types of Email Marketing:
1. Welcome Emails
2. Information Emails
3. Transactional Emails
4. Newsletter Emails
5. Lead Nurturing Emails
6. Sponsorship Emails
7. Sales Letter Emails
8. Re-Engagement Emails
9. Brand Story Emails
10. Review Request Emails
Slide 5
Advantages Of Email Marketing
1. Cost-Effective: Cheaper than other methods.
2. Easy: Simple to learn and use.
3. Targeted Audience: Reach your exact audience.
4. Detailed Messages: Convey clear, detailed messages.
5. Non-Disturbing: Less intrusive than social media.
6. Non-Irritating: Customers are less likely to get annoyed.
7. Long Format: Use detailed text, photos, and videos.
8. Easy to Unsubscribe: Customers can easily opt out.
9. Easy Tracking: Track delivery, open rates, and clicks.
10. Professional: Seen as more professional; customers read carefully.
Slide 6
Disadvantages Of Email Marketing:
1. Irrelevant Emails: Costs can rise with irrelevant emails.
2. Poor Content: Boring emails can lead to disengagement.
3. Easy Unsubscribe: Customers can easily leave your list.
Slide 7
Email Marketing Tools
Choosing a good tool involves considering:
1. Deliverability: Email delivery rate.
2. Inbox Placement: Reaching inbox, not spam or promotions.
3. Ease of Use: Simplicity of use.
4. Cost: Affordability.
5. List Maintenance: Keeping the list clean.
6. Features: Regular features like Broadcast and Sequence.
7. Automation: Better with automation.
Slide 8
Top 5 Email Marketing Tools:
1. ConvertKit
2. Get Response
3. Mailchimp
4. Active Campaign
5. Aweber
Slide 9
Email Marketing Strategy
To get good results, consider:
1. Build your own list.
2. Never buy leads.
3. Respect your customers.
4. Always provide value.
5. Don’t email just to sell.
6. Write heartfelt emails.
7. Stick to a schedule.
8. Use photos and videos.
9. Segment your list.
10. Personalize emails.
11. Ensure mobile-friendliness.
12. Optimize timing.
13. Keep designs clean.
14. Remove cold leads.
Slide 10
Uses of Email Marketing:
1. Affiliate Marketing
2. Blogging
3. Customer Relationship Management (CRM)
4. Newsletter Circulation
5. Transaction Notifications
6. Information Dissemination
7. Gathering Feedback
8. Selling Courses
9. Selling Products/Services
Read Full Article:
https://digitalsamaaj.com/is-email-marketing-effective-in-2024/
How to Handle the Separate Discount Account on Invoice in Odoo 17Celine George
In Odoo, separate discount account can be set up to accurately track and manage discounts applied on various transaction and ensure precise financial reporting and analysis
Join educators from the US and worldwide at this year’s conference, themed “Strategies for Proficiency & Acquisition,” to learn from top experts in world language teaching.
Understanding and Interpreting Teachers’ TPACK for Teaching Multimodalities i...Neny Isharyanti
Presented as a plenary session in iTELL 2024 in Salatiga on 4 July 2024.
The plenary focuses on understanding and intepreting relevant TPACK competence for teachers to be adept in teaching multimodality in the digital age. It juxtaposes the results of research on multimodality with its contextual implementation in the teaching of English subject in the Indonesian Emancipated Curriculum.
How to Add Colour Kanban Records in Odoo 17 NotebookCeline George
In Odoo 17, you can enhance the visual appearance of your Kanban view by adding color-coded records using the Notebook feature. This allows you to categorize and distinguish between different types of records based on specific criteria. By adding colors, you can quickly identify and prioritize tasks or items, improving organization and efficiency within your workflow.
Integrated Marketing Communications (IMC)- Concept, Features, Elements, Role of advertising in IMC
Advertising: Concept, Features, Evolution of Advertising, Active Participants, Benefits of advertising to Business firms and consumers.
Classification of advertising: Geographic, Media, Target audience and Functions.
How to Store Data on the Odoo 17 WebsiteCeline George
Here we are going to discuss how to store data in Odoo 17 Website.
It includes defining a model with few fields in it. Add demo data into the model using data directory. Also using a controller, pass the values into the template while rendering it and display the values in the website.
The membership Module in the Odoo 17 ERPCeline George
Some business organizations give membership to their customers to ensure the long term relationship with those customers. If the customer is a member of the business then they get special offers and other benefits. The membership module in odoo 17 is helpful to manage everything related to the membership of multiple customers.
How to Create Sequence Numbers in Odoo 17Celine George
Sequence numbers are mainly used to identify or differentiate each record in a module. Sequences are customizable and can be configured in a specific pattern such as suffix, prefix or a particular numbering scheme. This slide will show how to create sequence numbers in odoo 17.
BS 8878: Systematic Approaches to Documenting Web Accessibility Policies and Practices
1. BS 8878: Systematic Approaches to
Documenting Web Accessibility
Policies and Practices
Brian Kelly
Independent consultant
UK Web Focus
Contact Details
Email: ukwebfocus@gmail.com
Twitter: @briankelly
Blog: http://ukwebfocus.com/
1
Slides and further information available at
http://ukwebfocus.com/events/iwmw-2015/
A workshop session at the IWMW 2015 event
2. #IWMW15
#A3
About This Workshop
Structure:
• Introductions
• Current approaches to Web accessibility policies
• Limitations of current approaches
• How BS 8878 can help
• Using BS 8878 (group exercises)
• Reviewing what we’ve done
• What Next?
2
Introduction
3. #IWMW15
#A3
About You
• What is your interest in web accessibility?
• What are your responsibilities in this area?
• What knowledge of BS 8878 do you have?
• Do you have any specific issues you would
like to see addressed?
3
Introduction
4. #IWMW15
#A3
About Me
Brian Kelly:
• Longstanding #a11y
advocate &
practitioner
• Author of many peer-
reviewed papers on
#a11y
• In 2004 realised
limitations of WCAG
guidelines for
elearning
4
http://ukwebfocus.com/papers/#accessibility
5. #IWMW15
#A3
Institutional Accessibility Policies (1)
Survey of accessibility policies in 9 north west universities:
[Edge Hill] – [Liverpool] – [Liverpool John Moores] – [Liverpool Hope] –
[UCLAN] – [Bolton] – [Manchester] – [MMU] – [Salford]
• All linked from home page (and in navigation bars)
• Summarised at http://ukwebfocus.com/2015/07/14/
In brief:
• Aspirational: “The University is committed to*
making its website and the material provided on it
accessible to as many people as possible*”
• Aspirational to conform with WCAG: “All pages on
this site aim to* be accessible to W3C AA compliance
or better, complying with priority 1 & 2 guidelines of
the W3C Web Content Accessibility Guidelines”
5* My emphasis
CurrentApproaches
6. #IWMW15
#A3
Institutional Accessibility Policies (2)
• Specific WCAG conformance levels: “This central
site is intended to* meet at least level 2 (AA) of the
W3C’s Web Accessibility Initiative (WAI) Guidelines,
and as far as possible to meet level 3 (AAA)”
• Browser policies: “We try to* make our website
compatible with as many browsers as possible”
• Details of testing processes: “We have also tested
the site extensively in a wide range of browsers and
settings to ensure the site functionality is available to
as many users as possible*”
• Techniques for users: “You can increase or reduce
the text size by using your browser’s zoom function”
6* My emphasis
CurrentApproaches
7. #IWMW15
#A3
Institutional Accessibility Policies (3)
• Specific techniques for users: “Microsoft Internet
Explorer version 8 and above …; Mozilla Firefox: To
alter text size, select ‘zoom’ select zoom in (Ctrl+) or
zoom out (Ctrl-). To remove CSS stylings select …”
• Details of access keys: “Access keys for websites
are defined as: Access Key 1 – Homepage; Access
Key 2 – News;… Access Key 0 – Accessibility Help”
• Techniques used by content providers: “Steps
we’ve taken: Using alt tags on images; Using sufficient
contrast on colours; Using CSS to ...”
• Details of training and support: “Staff are offered a
comprehensive training programme”
7
CurrentApproaches
8. #IWMW15
#A3
Reflections
In brief accessibility policies:
• Typically go beyond statements of WCAG conformance
May include details of:
• Specific techniques for users & content creators
• Processes used to create web resources
• Testing processes used to ensure policies are being
implemented correctly
• Contact details in case of accessibility problems
However:
• Approaches are not taken in a consistent manner
• None describe maintenance of policies (or mentioned
mobile!)
8
Conclusions: There is a need for a consistent & standardised approach
to build on existing approaches.
CurrentApproaches
9. #IWMW15
#A3
Building on Research
“web accessibility is not
an intrinsic characteristic
of a digital resource but
is determined by
complex political, social
and other contextual
factors, as well as
technical aspects which
are the focus of WAI
standardisation
activities. It can therefore
be inappropriate to
develop legislation …
only associated with
properties of the
resource.”
9
Cooper, M., Sloan, D., Kelly, B. and Lewthwaite, S., 2012. A Challenge to Web Accessibility Metrics & Guidelines: Putting
People and Processes First W4A2012: 9th International Cross-Disciplinary Conference on Web Accessibility
It’s not just about the resource, it’s about people (wide range of stakeholders), policies (based on the context of
use, the environment, resources, …) and processes (used to ensure policies are implemented correctly)
10. #IWMW15
#A3
Is Accessibility Really Complex?
Is web accessibility really
“determined by complex
political, social and other
contextual factors”?
Surely it’s about:
• A simple set of rules to
be applied to web
resources
• Legislation which
mandates organisations
to use the rule
• Education on how to
implement the rules
10
Accessibility as purely a technical issue? Where’s the user? Where
are the blended solutions? How are contextual factors addressed? …
Limitations
11. #IWMW15
#A3
Challenges
Areas which may pose difficulties in ensuring WCAG
compliance e.g.
• Your corporate web site and the constraints of the
CMS
• Your VLE with the limitations provided by the vendor
• Your institutional repository with author-deposited
PDFs but no ALT text for images in MS Word master
• Your plans to digitise lectures, but no funding for
captioning
• Your MOOC plans and the accompanying
uncaptioned video resources
• ….
11
Limitations
12. #IWMW15
#A3
Enter BS 8878
BS 8878:
• Developed in UK in parallel with our
holistic accessibility work
• UK standardisation work aligned with ideas
described in “Accessibility 2.0: People,
Policies and Processes”, W4A 2007
• Work led by Jonathan Hassell,
Hassell Inclusion and former
Head of Usability & Accessibility,
BBC Future Media
• Costs £100
• See Getting Started Guide
and Hassell Inclusion
12
13. #IWMW15
#A3
BS 8878’s 16 Stages
BS 8878 describes 16 steps which cover 4 stages.
See BS 8878 in 88 Seconds video 13
14. #IWMW15
#A3
BS 8878’s 16 Steps
Step 1: Define the purpose of the web product
Step 2: Define the target audiences for the web product
Step 3: Analyse the needs of the target audiences for the web product
Step 4: Note any platform or technology preferences and restrictions of the web
product's target audiences
Step 5: Define the relationship the product will have with its target audiences
Step 6: Define the user goals and tasks the web product needs to provide
Step 7: Consider the degree of user-experience the web product will aim to provide
Step 8: Consider inclusive design and user-personalized approaches to accessibility
Step 9: Choose the delivery platforms to support
Step 10: Choose browsers, operating systems & assistive technologies to support
Step 11: Choose whether to create or procure web product in-house or contract out
Step 12: Define the web technologies to be used in the web product
Step 13: Use web guidelines to direct accessible web production
Step 14: Assure the web product's accessibility through production
Step 15: Communicate the web product's accessibility decisions at launch
Step 16: Plan to assure accessibility in all post-launch updates to the product
14
e.g. WCAG
15. #IWMW15
#A3
In Brief
At its heart, BS 8878 encourages organisations to make all
accessibility decisions based on the purpose of their
product, its specific audiences, and a clear, researched
understanding of the contexts in which those audiences will
use the product.
In the light of this research, organisations can then make high-
level decisions on the overall degree of accessibility they
wish the product to have, and more detailed decisions on the
accessibility of user journeys to each of its goals based on the
relative importance of the goals and the cost-benefits of
making it accessible to that degree.
From there organisations are advised on the relative cost-
benefits of different testing methodologies for them to use
across the lifetime of the product to assure themselves that
they have achieved the degree of accessibility they were
aiming for.
15
BS8878
16. #IWMW15
#A3
Group Exercises (1)
You will now use BS 8878 steps to document your policies
& practices for a web site product of interest to you e.g.
• Multimedia on the corporate web site
• Multimedia for use in a VLE
• The university prospectus
• Event amplification (e.g. for a conference, graduation
ceremony, etc.)
• The institutional repository (full of PDFs)
• The corporate web site
• A niche area (e.g. accessibility for blind maths
students)
• …
16
GorupExercises
17. #IWMW15
#A3
Group Exercises (2)
Working in small groups:
• Document the steps using the 16 steps
• Use a Google Doc:
bit.ly/iwmw15-bs8878-1
bit.ly/iwmw15-bs8878-2 (or iwmw15-a3-2)
bit.ly/iwmw15-bs8878-3
bit.ly/iwmw15-bs8878-4
• Give brief summary of your approaches at end of session
Note:
• Document will be world-writeable for another week
• Feel free to continue afterwards
• Content provided under a CC-licence
• Approaches will be documented on UK Web Focus blog
17
GorupExercises
19. #IWMW15
#A3
BS 8878’s 16 Steps
Step 1: Define the purpose of the web product
Step 2: Define the target audiences for the web product
Step 3: Analyse the needs of the target audiences for the web product
Step 4: Note any platform or technology preferences and restrictions of the web
product's target audiences
Step 5: Define the relationship the product will have with its target audiences
Step 6: Define the user goals and tasks the web product needs to provide
Step 7: Consider the degree of user-experience the web product will aim to provide
Step 8: Consider inclusive design and user-personalized approaches to accessibility
Step 9: Choose the delivery platforms to support
Step 10: Choose browsers, operating systems & assistive technologies to support
Step 11: Choose whether to create or procure web product in-house or contract out
Step 12: Define the web technologies to be used in the web product
Step 13: Use web guidelines to direct accessible web production
Step 14: Assure the web product's accessibility through production
Step 15: Communicate the web product's accessibility decisions at launch
Step 16: Plan to assure accessibility in all post-launch updates to the product
19
e.g. WCAG
20. #IWMW15
#A3
BS 8878 & Event Amplification for
IWMW 2015
20
http://iwmw.org/iwmw2015/technology/
accessibility-event-amplification/
Policy for event
amplification at IWMW
2015
Note:
• Difficulty in writing
this from scratch
• Policy available
under a CC licence
• How ‘patterns’ would
help identify
appropriate
practices
22. #IWMW15
#A3
What of the Risks?
22
Risk assessment available at
http://iwmw.org/iwmw2015/technology/accessibility-
event-amplification/#risks
23. #IWMW15
#A3
BS 8878 Elsewhere
BS 8878 steps may be
valuable for internal use,
but may be confusing for
end users
Accessibility statement on
Hassellinclusion site is
written for end users
(www.hassellinclusion.com/
accessibility/)
23
24. #IWMW15
#A3
Possible Accessibility Policy for an Institutional Repository
Possible accessibility policy for an institutional
repository. See blog post at
http://ukwebfocus.com/2011/01/24/web-accessibility-
institutional-repositories-and-bs-8878/
24
Statement Note
The repository service is an open-access information storage & retrieval system containing
the university’s research findings and papers, openly and freely accessible to the research
community and public. A full description of each item is provided, and where copyright
regulations permit, the full-text of the research output is stored in the repository and fully
accessible. Items are deposited in the repository from various sources including author
self-deposit, deposit by authorised staff in departments and deposits by repository staff.
Description of
the purpose of
the ‘web
product’
Items are normally provided in PDF format although other formats such as MS Word or
HTML may also be used.
Carry out audit
Items are normally deposited in the format required by the publisher. Popular formats
should be accessible using standard viewing tools. However some formats may require
specialist browsers to be installed.
Audit will show
unusual
formats
Items may not conform to appropriate accessibility guidelines due to the devolved
responsibilities for depositing items & complexities of implementing the guidelines across
the large number of items housed in the repository.
If so, details
should be given
Future developments to the service will include an "Accessibility problem" button which
will enable repository staff to be alerted to the scale of accessibility problems.
Include if
planned
Repository staff will work with the University Staff Development Unit to ensure that
training is provided on ways of creating accessible documents which will be open to all
staff and research students.
Include if true!
Repository staff will carry out periodic audits on the accessibility of repository items,
monitor trends and act accordingly.
Include if true!
The Web interface to repository conform with University Web site accessibility guidelines.
25. #IWMW15
#A3
Conclusions
To conclude:
• BS 8878 provides a standard to address
challenges in enhancing web accessibility
• Benefits in adopting common practices
25
What do you think we should do next?
26. #IWMW15
#A3
Book on BS 8878
See http://www.hassellinclusion.com/landing/book/
26
“I want you to imagine for a moment that,
Professor Jonathan Hassell's `Including your
missing 20% by embedding web and mobile
accessibility' is like a large set of well labelled
keys. Each chapter is part of that key set and
enables the reader, whether expert or layperson
alike, to unlock the power of BS8878, the British
Standard on Web Accessibility. If your
organisation is looking to embed web accessibility
from the outset or to adopt best practice then you
need go no further, this book is for you.”
Amazon review
27. #IWMW15
#A3
This presentation, “BS 8878: Systematic Approaches to Documenting
Web Accessibility Policies and Practices” by Brian Kelly, is licensed
under the Creative Commons Attribution 3.0 Licence
Note the licence covers most of the text in this presentation. Quotations
may have other licence conditions.
Images may have other licence conditions. Where possible links are
provided to the source of images so that licence conditions can be found.
27
Slides and further information available at
http://ukwebfocus.com/events/iwmw-2015/
Licence and Additional Resources
Editor's Notes
BS 8878 describes 16 steps which cover 4 stages : the research before you start the work; the strategic decisions you make based on the research; the delivery and launch of the Web site (which is where decisions on WCAG are made) and the ongoing maintenance of the Web resource.
Note a BS 8878 in 88 Seconds video is available at http://www.youtube.com/watch?v=GJ4MRCyMTRQ
The 16 steps in BS 8878 are shown. Note that step 13 includes the implementation of the web standards, such as WCAG, which have been selected. From this we can see that BS 8878 isn't intended as an alternative to WCAG, but a much broader approach which standardises processes when can help in the development of accessible services.
I've highlighted the key aspects. The standard:
"encourages organisations to make all accessibility decisions". These decisions are based on several contextual aspects including "the purpose of their product and the specific audiences".
Having carried out the research the organisation can then make the decision on overall degree of accessibility they wish the Web product to have.
Finally organisations should document methodologies for use across the lifetime of the product to ensure that we don't see "accessibility rot" after the launch of the product.
The 16 steps in BS 8878 are shown. Note that step 13 includes the implementation of the web standards, such as WCAG, which have been selected. From this we can see that BS 8878 isn't intended as an alternative to WCAG, but a much broader approach which standardises processes when can help in the development of accessible services.
To conclude:
If you care about accessibility you’ll think beyond the digital resource and the digital tools
You should engage with a wide range of stakeholders in enhancing accessibility
You should also consider alternative perspectives of ‘accessibility’ and disability
It’s OK to reject ‘universal accessibility’ and focus on ‘accessibility for these users in these circumstances’
WCAG is still relevant, but shouldn’t dominate
BS 8878 provides a standard for further work