The methodology identifies and solves accessibility issues in CMS environments through an iterative process. It evaluates CMS configurations and sample web pages using ATAG and WCAG guidelines. A case study analyzed two CMSs, finding common errors like missing page titles and labels. Solutions like modifying templates and editors were applied, improving checkpoint compliance. While the methodology helps ensure accessibility, proper CMS configuration and user training is also needed.
This document provides an overview of why two university web developers, Shelley and Stephanie, chose to use WordPress for their institutions' websites. Some key points:
- Both previously struggled with limited resources and outdated CMS options at their schools, with many broken links, duplicate content, and lack of features.
- They tried alternatives like Drupal but found them too complex and difficult to use. WordPress offered an easy interface for content creation and management.
- WordPress allows them to easily create sites, blogs, and networks with thousands of free, high-quality plugins and themes. It also has a strong developer community and regular, stable updates.
- While it lacks some advanced features out of
Seamless Upgrade to 8.5 Version. Performance Testing Tuning of Ektron & the E...ameexusa
With the announcement of the 8.5 version by Ektron, we at Ameex being the accredited implementation partner of Ektron decided to perform a few upgrades and show some of the best practices in carrying out the upgrade. This ppt was received with great reception at the recently concluded Ektron Synergy 2011 conference. For more information, please contact us info@ameexusa.com
SPSDenver - Wrapping Your Head Around the SharePoint BeastMark Rackley
This document provides an overview of SharePoint and the path to becoming a SharePoint developer. It discusses why organizations implement SharePoint, defines common terminology, and reviews the logical architecture and taxonomy. It outlines the various roles in SharePoint development from end users to administrators to developers. It also discusses tools, debugging, deployment, and the importance of the SharePoint community.
Dos and Don'ts of Android Application Security (Security Professional Perspec...Bijay Senihang
Besides of strong Andorid Security model, android application is still unsecure. There exist lost of vulnerabilities in android application due to lack of secure coding and lack of proper secuity knowledge.
This document summarizes a presentation about rogue router firmware. It describes how over 10 major router vendors used the same firmware that contained a backdoor, exposing over 2 million online devices worldwide. The backdoor could allow the routers to be used for botnets, personal proxy networks, or free Wi-Fi mapping. The document discusses responsibilities of vendors, governments, and consumers in securing devices. It recommends disabling remote management if unused, using open source firmware if available, and using firewalls and antivirus software as defenses. Responsible disclosure was made to the affected vendors.
Wake-Up Call (Current IT Security Scenario of Nepal-2014)Bijay Senihang
With Rise if of IT related business, there is always rise of IT Security Risk. A presentation by Bijay Limbu senihang regarding current IT security scenario of Nepal.
This document provides an overview of why two university web developers, Shelley and Stephanie, chose to use WordPress for their institutions' websites. Some key points:
- Both previously struggled with limited resources and outdated CMS options at their schools, with many broken links, duplicate content, and lack of features.
- They tried alternatives like Drupal but found them too complex and difficult to use. WordPress offered an easy interface for content creation and management.
- WordPress allows them to easily create sites, blogs, and networks with thousands of free, high-quality plugins and themes. It also has a strong developer community and regular, stable updates.
- While it lacks some advanced features out of
Seamless Upgrade to 8.5 Version. Performance Testing Tuning of Ektron & the E...ameexusa
With the announcement of the 8.5 version by Ektron, we at Ameex being the accredited implementation partner of Ektron decided to perform a few upgrades and show some of the best practices in carrying out the upgrade. This ppt was received with great reception at the recently concluded Ektron Synergy 2011 conference. For more information, please contact us info@ameexusa.com
SPSDenver - Wrapping Your Head Around the SharePoint BeastMark Rackley
This document provides an overview of SharePoint and the path to becoming a SharePoint developer. It discusses why organizations implement SharePoint, defines common terminology, and reviews the logical architecture and taxonomy. It outlines the various roles in SharePoint development from end users to administrators to developers. It also discusses tools, debugging, deployment, and the importance of the SharePoint community.
Dos and Don'ts of Android Application Security (Security Professional Perspec...Bijay Senihang
Besides of strong Andorid Security model, android application is still unsecure. There exist lost of vulnerabilities in android application due to lack of secure coding and lack of proper secuity knowledge.
This document summarizes a presentation about rogue router firmware. It describes how over 10 major router vendors used the same firmware that contained a backdoor, exposing over 2 million online devices worldwide. The backdoor could allow the routers to be used for botnets, personal proxy networks, or free Wi-Fi mapping. The document discusses responsibilities of vendors, governments, and consumers in securing devices. It recommends disabling remote management if unused, using open source firmware if available, and using firewalls and antivirus software as defenses. Responsible disclosure was made to the affected vendors.
Wake-Up Call (Current IT Security Scenario of Nepal-2014)Bijay Senihang
With Rise if of IT related business, there is always rise of IT Security Risk. A presentation by Bijay Limbu senihang regarding current IT security scenario of Nepal.
This document provides a structural analysis of the offshore wind innovation systems in the UK, Denmark, the Netherlands, and Germany. It examines the key actors, networks, institutions, and infrastructure components that make up each system. The analysis focuses on identifying the main governmental agencies, knowledge institutions, educational organizations, industrial actors, and support organizations involved in each country's offshore wind sector. It also maps the knowledge networks, lobbying networks, and industrial collaborations that connect actors within each national system. Finally, it describes some of the policies, regulations, expectations, and physical infrastructure supporting offshore wind development across the four countries. The goal of this structural analysis is to understand the composition and interconnections of each innovation system as a foundation for a subsequent functional
AMEC is a large UK-based engineering firm with over 27,000 employees working in 40+ countries. It has extensive experience in nuclear power projects dating back to the 1950s, having played strategic roles in the design and construction of all civil nuclear power plants built in the UK. Some key points discussed include AMEC's involvement in introducing pressurized water reactor (PWR) technology to the UK through the Sizewell B project, changes made to generic nuclear designs through regulatory approval processes, and the importance of the licensee retaining primary responsibility for safety.
The document discusses several technology trends that will endure including Long Term Evolution (LTE), smart grids, software defined networks, NoSQL, Near Field Communication (NFC), Internet of Things (IoT)/Machine to Machine (M2M), big data, social networks, and cloud computing. It provides a high-level overview of each technology trend without going into detail about any specific one.
The document discusses the 7 Habits of Highly Effective People. It summarizes each habit in 1-2 sentences:
Habit 1 is about being proactive and recognizing we have control over our choices. Habit 2 is about beginning with the end in mind and envisioning goals and a personal mission statement. Habit 3 is about effective self-management and prioritizing important tasks. Habits 4-6 focus on interdependence - Habit 4 is thinking win-win in relationships, Habit 5 is seeking first to understand others, and Habit 6 is synergizing teamwork. Habit 7 is about self-renewal and sharpening skills through learning. The habits move from independence to interdependence and
The document discusses cloud computing, including what it is, why organizations use it, and its architecture. Cloud computing refers to shared computing resources and applications available over the internet on demand. It allows for flexible, scalable usage of resources and cost savings. Key aspects discussed include virtualization, hypervisors, multi-tenancy, cloud services like IaaS, PaaS and SaaS, and types of cloud architectures like public, private and hybrid clouds.
The document discusses the Internet of Things (IoT) and how it connects physical objects through sensors and communication technologies. It provides examples of current IoT applications like smart cities, smart grids, smart homes, and health monitoring. The IoT allows objects to sense their environment and communicate data in real-time, enabling more intelligent systems and actions. Companion technologies like cloud computing and big data are also needed to process and analyze the large amounts of IoT data.
The document discusses telecommunications topics including:
1. The agenda covers telecom basics, history, digital switching, signaling events, and wireless terminology.
2. Early switching exchanges used electro-mechanical technologies like Strowger and crossbar exchanges, while modern switches are digital.
3. In digital switches, voice signals are sampled, digitized via PCM, and transmitted through time slot interchange and multiplexing.
The document provides information about intelligent networks and CAMEL protocol. It discusses why intelligent networks were developed by removing service creation from switches to a remote Service Control Point node. It then gives a brief history of intelligent networks and provides details on the basics of intelligent networks including the network elements, relationship between elements, basic call state models for originating and terminating calls, and detection points.
The document discusses the growth of mobile data and the development of LTE technology. It notes that mobile data is growing exponentially, especially for mobile broadband. LTE was developed by 3GPP to handle this growing traffic and provide higher speeds and lower latency compared to 3G. LTE provides connection speeds of up to 100Mbps downlink and 50Mbps uplink using OFDM and MIMO technologies in a simpler network architecture than 3G.
This document discusses key principles of distributed systems, including that they are made up of many commodity servers, have no single point of failure, and make local decisions without a global view. It also covers characteristics like horizontal scalability. Specific examples like Amazon, Google, and Facebook are provided. Core concepts discussed include consistency models, replication, synchronization methods like vector clocks, and NoSQL databases using consistent hashing to partition data.
Cms & wordpress theme development 2011Dave Wallace
This document discusses content management systems (CMS) and why WordPress is a popular choice. It notes that more websites now feature dynamic, frequently updated content from multiple sources. CMS allow decentralized updating and reuse of common elements. WordPress is recommended for beginners due to its simplicity yet expandability through plugins. While initially a blogging platform, WordPress can be used to build many types of websites through themes. It has a large community and runs on common, well-supported technology.
The Great Consolidation - Entertainment Weekly Migration Case Study - SANDcam...Jon Peck
The migration project involved moving content from Entertainment Weekly's WordPress and Vignette systems to Drupal. A team of 4 developers from Four Kitchens and 1 from Time Inc worked on the migration over 17 sprints from April 2014 to January 2015. Key aspects of the project included theming the site with Aurora, implementing JavaScript standards, migrating over 100,000 posts, images and terms from WordPress and Vignette, improving performance, and collaborating with Time Inc on custom content types and workflows. Testing was done to ensure the migrated site met performance standards.
This is a very old presentation providing some tips on how to evaluate a web content management system (WCMS) along with some details on our in-house WCMS.
Content Management Systems (CMS) & Wordpress theme developmentDave Wallace
- WordPress is a popular content management system (CMS) that can be used to manage websites with frequently updated content from multiple sources. It allows both technical and non-technical users to manage content.
- While WordPress started as a blogging platform, it has evolved into a full-fledged CMS through the use of plugins and themes. Many websites built with WordPress do not look like blogs.
- Setting up WordPress involves downloading and installing the WordPress files, creating a database, editing configuration files, and creating an administrator account. Key interfaces include the public interface for visitors and the admin interface for content management.
IWMW 2003: b8 implementation of a commercial content management systemIWMW
Slides used in workshop session B8 on "Implementation of a Commercial Content Management System" at the IWMW 2003 event held at the University of Kent on 11-13 June 2003.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2003/sessions/#workshops-b
Enterprise WordPress - Performance, Scalability and RedundancyJohn Giaconia
Slides on how to build your WordPress site so that it performs like an enterprise application.
Associated video: http://wordpress.tv/2014/06/25/john-giaconia-enterprise-wordpress-performance-scalability-and-redundancy/
2/15/2012 - Wrapping Your Head Around the SharePoint BeastMark Rackley
The document discusses an introduction to SharePoint development, providing an outline of topics such as why SharePoint, what SharePoint is, the SharePoint overview, what SharePoint development entails, the steps to becoming a SharePoint developer, and the SharePoint community. It also addresses learning SharePoint development, the reasons for using SharePoint as a development platform, and terminology related to SharePoint.
This document summarizes Richard Esplin's presentation on content management. The presentation covered making the case for content management, best practices using a platform approach, introducing the CMIS standard, and providing live examples. Key topics included what constitutes content and content-centric applications, evaluating DIY content management versus a platform approach, components of content systems, evaluating open source platforms, and examples using Python, PHP, and the CMIS workbench.
Share was originally built as a collaboration application on top of the Alfresco Platform. Because Share is a more modern interface than Alfresco Explorer, many customers have adopted customizing Share as their strategy for building solutions on Alfresco. To be successful, such solutions need to understand that Share is a complete collaboration application with a specific Information Architecture. This session will explore leveraging the Share UI while creating your own Information Architecture, including for non-collaborative use cases.
This document provides a structural analysis of the offshore wind innovation systems in the UK, Denmark, the Netherlands, and Germany. It examines the key actors, networks, institutions, and infrastructure components that make up each system. The analysis focuses on identifying the main governmental agencies, knowledge institutions, educational organizations, industrial actors, and support organizations involved in each country's offshore wind sector. It also maps the knowledge networks, lobbying networks, and industrial collaborations that connect actors within each national system. Finally, it describes some of the policies, regulations, expectations, and physical infrastructure supporting offshore wind development across the four countries. The goal of this structural analysis is to understand the composition and interconnections of each innovation system as a foundation for a subsequent functional
AMEC is a large UK-based engineering firm with over 27,000 employees working in 40+ countries. It has extensive experience in nuclear power projects dating back to the 1950s, having played strategic roles in the design and construction of all civil nuclear power plants built in the UK. Some key points discussed include AMEC's involvement in introducing pressurized water reactor (PWR) technology to the UK through the Sizewell B project, changes made to generic nuclear designs through regulatory approval processes, and the importance of the licensee retaining primary responsibility for safety.
The document discusses several technology trends that will endure including Long Term Evolution (LTE), smart grids, software defined networks, NoSQL, Near Field Communication (NFC), Internet of Things (IoT)/Machine to Machine (M2M), big data, social networks, and cloud computing. It provides a high-level overview of each technology trend without going into detail about any specific one.
The document discusses the 7 Habits of Highly Effective People. It summarizes each habit in 1-2 sentences:
Habit 1 is about being proactive and recognizing we have control over our choices. Habit 2 is about beginning with the end in mind and envisioning goals and a personal mission statement. Habit 3 is about effective self-management and prioritizing important tasks. Habits 4-6 focus on interdependence - Habit 4 is thinking win-win in relationships, Habit 5 is seeking first to understand others, and Habit 6 is synergizing teamwork. Habit 7 is about self-renewal and sharpening skills through learning. The habits move from independence to interdependence and
The document discusses cloud computing, including what it is, why organizations use it, and its architecture. Cloud computing refers to shared computing resources and applications available over the internet on demand. It allows for flexible, scalable usage of resources and cost savings. Key aspects discussed include virtualization, hypervisors, multi-tenancy, cloud services like IaaS, PaaS and SaaS, and types of cloud architectures like public, private and hybrid clouds.
The document discusses the Internet of Things (IoT) and how it connects physical objects through sensors and communication technologies. It provides examples of current IoT applications like smart cities, smart grids, smart homes, and health monitoring. The IoT allows objects to sense their environment and communicate data in real-time, enabling more intelligent systems and actions. Companion technologies like cloud computing and big data are also needed to process and analyze the large amounts of IoT data.
The document discusses telecommunications topics including:
1. The agenda covers telecom basics, history, digital switching, signaling events, and wireless terminology.
2. Early switching exchanges used electro-mechanical technologies like Strowger and crossbar exchanges, while modern switches are digital.
3. In digital switches, voice signals are sampled, digitized via PCM, and transmitted through time slot interchange and multiplexing.
The document provides information about intelligent networks and CAMEL protocol. It discusses why intelligent networks were developed by removing service creation from switches to a remote Service Control Point node. It then gives a brief history of intelligent networks and provides details on the basics of intelligent networks including the network elements, relationship between elements, basic call state models for originating and terminating calls, and detection points.
The document discusses the growth of mobile data and the development of LTE technology. It notes that mobile data is growing exponentially, especially for mobile broadband. LTE was developed by 3GPP to handle this growing traffic and provide higher speeds and lower latency compared to 3G. LTE provides connection speeds of up to 100Mbps downlink and 50Mbps uplink using OFDM and MIMO technologies in a simpler network architecture than 3G.
This document discusses key principles of distributed systems, including that they are made up of many commodity servers, have no single point of failure, and make local decisions without a global view. It also covers characteristics like horizontal scalability. Specific examples like Amazon, Google, and Facebook are provided. Core concepts discussed include consistency models, replication, synchronization methods like vector clocks, and NoSQL databases using consistent hashing to partition data.
Cms & wordpress theme development 2011Dave Wallace
This document discusses content management systems (CMS) and why WordPress is a popular choice. It notes that more websites now feature dynamic, frequently updated content from multiple sources. CMS allow decentralized updating and reuse of common elements. WordPress is recommended for beginners due to its simplicity yet expandability through plugins. While initially a blogging platform, WordPress can be used to build many types of websites through themes. It has a large community and runs on common, well-supported technology.
The Great Consolidation - Entertainment Weekly Migration Case Study - SANDcam...Jon Peck
The migration project involved moving content from Entertainment Weekly's WordPress and Vignette systems to Drupal. A team of 4 developers from Four Kitchens and 1 from Time Inc worked on the migration over 17 sprints from April 2014 to January 2015. Key aspects of the project included theming the site with Aurora, implementing JavaScript standards, migrating over 100,000 posts, images and terms from WordPress and Vignette, improving performance, and collaborating with Time Inc on custom content types and workflows. Testing was done to ensure the migrated site met performance standards.
This is a very old presentation providing some tips on how to evaluate a web content management system (WCMS) along with some details on our in-house WCMS.
Content Management Systems (CMS) & Wordpress theme developmentDave Wallace
- WordPress is a popular content management system (CMS) that can be used to manage websites with frequently updated content from multiple sources. It allows both technical and non-technical users to manage content.
- While WordPress started as a blogging platform, it has evolved into a full-fledged CMS through the use of plugins and themes. Many websites built with WordPress do not look like blogs.
- Setting up WordPress involves downloading and installing the WordPress files, creating a database, editing configuration files, and creating an administrator account. Key interfaces include the public interface for visitors and the admin interface for content management.
IWMW 2003: b8 implementation of a commercial content management systemIWMW
Slides used in workshop session B8 on "Implementation of a Commercial Content Management System" at the IWMW 2003 event held at the University of Kent on 11-13 June 2003.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2003/sessions/#workshops-b
Enterprise WordPress - Performance, Scalability and RedundancyJohn Giaconia
Slides on how to build your WordPress site so that it performs like an enterprise application.
Associated video: http://wordpress.tv/2014/06/25/john-giaconia-enterprise-wordpress-performance-scalability-and-redundancy/
2/15/2012 - Wrapping Your Head Around the SharePoint BeastMark Rackley
The document discusses an introduction to SharePoint development, providing an outline of topics such as why SharePoint, what SharePoint is, the SharePoint overview, what SharePoint development entails, the steps to becoming a SharePoint developer, and the SharePoint community. It also addresses learning SharePoint development, the reasons for using SharePoint as a development platform, and terminology related to SharePoint.
This document summarizes Richard Esplin's presentation on content management. The presentation covered making the case for content management, best practices using a platform approach, introducing the CMIS standard, and providing live examples. Key topics included what constitutes content and content-centric applications, evaluating DIY content management versus a platform approach, components of content systems, evaluating open source platforms, and examples using Python, PHP, and the CMIS workbench.
Share was originally built as a collaboration application on top of the Alfresco Platform. Because Share is a more modern interface than Alfresco Explorer, many customers have adopted customizing Share as their strategy for building solutions on Alfresco. To be successful, such solutions need to understand that Share is a complete collaboration application with a specific Information Architecture. This session will explore leveraging the Share UI while creating your own Information Architecture, including for non-collaborative use cases.
The document discusses the challenges of content management for internal and customer users and how a content management system (CMS) can help address these challenges. It provides examples of challenges such as managing content in multiple formats, different user access levels and rights, and content from multiple sources. It then describes how a CMS can help with data management, web templating, personalization, syndication, and digital rights management. The document also compares features of different CMS platforms and argues that Drupal is a robust option as it is open source, customizable with many modules, and offers both content management and social software capabilities.
IWMW 2002: Portals and CMS:" Why You Need Them BothIWMW
Plenary talk on “Portals and CMS:" Why You Need Them Both” given by Paul Browning at the IWMW 2002 event.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/sessions.html#talk-browning
Makers Bay offers software development services including custom web applications, portals, search portals, and mobile applications. They recommend frameworks like Grails, Yii, and CodeIgnitor for Java/PHP development. Their solution delivery practices include agile development, continuous integration, and performance engineering through techniques like caching, scalable architecture, and cloud databases. They provide reference architectures for web 2.0, portal, and rich internet applications.
Website Archivability - Library of Congress NDIIPP Presentation 2015/06/03Vangelis Banos
Website Archivability (WA) captures the core
aspects of a website crucial in diagnosing
whether it has the potentiality to be archived
with completeness and accuracy.
This document discusses JavaScript unit testing adoption in the enterprise. It describes how the company Microlise transitioned to unit testing their JavaScript code. They had two large web applications with organically grown and unstructured JavaScript that was becoming more complex. They investigated various unit testing tools and chose Mocha to add tests. They created file structures and templates to facilitate testing. Their goal is to continue improving code quality and integrating tests into their development processes.
This document discusses JavaScript unit testing adoption in the enterprise. It describes how the company Microlise transitioned to unit testing their JavaScript code. They had large, organically grown web applications with unstructured JavaScript. Unit testing in C# provided benefits, so they wanted the same for JavaScript. They evaluated tools like QUnit, Jasmine and Mocha and chose Mocha with the Chutzpah test runner in Visual Studio. They implemented a file structure convention and added tests to their MVC applications and logic files. This brought success and they now look to improve techniques and continuous integration.
This document summarizes a Drupal beginner training session. It introduces Drupal and content management systems. It discusses the Drupal business model, users, and history. It covers installing Drupal, the admin area, content and module workflows. It also summarizes setting up themes, views, panels, users, and favorite modules. The document emphasizes practicing Drupal skills and provides several resource links.
This presentation will be useful to those
who would like to get acquainted with lifetime history
of successful monolithic Java application.
It shows architectural and technical evolution of one Java web startup that is beyond daily coding routine and contains a lot of simplifications, Captain Obvious and internet memes.
But this presentation is not intended for monolithic vs. micro services architectures comparison.
This document discusses considerations for designing and developing solutions for SharePoint. It covers team structures for SharePoint projects, designing sites, UI development approaches, required developer skills, development environments, execution models, logging and tracing, and deployment. It provides recommendations for team roles and structures, developing web parts and forms without code, and resources for SharePoint development.
Georgia Tech - College of Engineering Case StudyEric Sembrat
The document describes the 2014 redesign of the Georgia Tech College of Engineering website. It outlines the plan for the redesign which involved reorganizing content and structure, developing a new theme adhering to campus standards, and accommodating unexpected changes. The work was done by a consultant and web developer. Lessons learned included preparing for broken links during transition, clear communication during development, thorough testing before rollout, and a soft launch approach. The redesign aimed to modernize and improve the usability of the outdated website.
World trade center in kerala proposal- AR. DEEKSHITH MAROLI 724519251008 REPORTdeekshithmaroli666
World trade center live proposal in kerala.
Future of our nation is looking towards kerala..?
Yes, because the biggest sludge less port is going to open in kerala soon and also about the hidden massing growth of tourism, it , business sector
1. Methodology for identifying
and solving accessibility
related issues in Web
Content Management
System environments
Toni Granollers
University of Lleida
tonig@diei.udl.cat
University of Lleida University of the Basque country Lyon, 17 April 2012
2. Outline
• Introduction
• CMS environments
• Evaluating accessibility
• Proposed Methodology
• Case study
• Discussion
• Conclusions
3. Introduction
• Introduction
• “The power of the Web is in
its universality. Access by
• CMS
everyone regardless of
environments
disability is an essential
• Evaluating
aspect”
accessibility
Tim Berners-Lee
• Proposed
Methodology
• Accessibility is a legal
• Case study
requirement that should be Source: http://icons.anatom5.de/
• Discussion
integrated into Web
• Conclusions
development methodologies
4. CMS environments
Users Web Administrators
• Introduction
• CMS CMS environment
environments
• Evaluating
Data
+ Templates
accessibility
• Proposed
Web Page
Methodology
• Case study
• Discussion
• Conclusions
5. Evaluating accessibility
• Introduction
• Evaluate Web content with WCAG
• Determine the scope of the evaluation
• CMS
• Automatic evaluation
environments
• Use at least two Web accessibility
• Evaluating evaluation tools
accessibility • Validate markup (syntax and style)
• Proposed • Manual revision by accessibility evaluator
Methodology • Evaluate CMS environment with ATAG
• Case study
• Discussion But despite guidelines exist and
• Conclusions the process to evaluate web accessibility is clear
there are still accessibility errors!
6. Methodology (I)
Properties
• Allows identifying and solving
• Introduction
accessibility related issues in web
• CMS
pages using CMS environments
environments
• Iterative
• Evaluating
accessibility
• Includes ATAG and WCAG
• Proposed • Includes web content accessibility
Methodology evaluation methodology proposed by
• Case study
the W3C
• Discussion • Takes into account features
• Conclusions specific to CMS environments
7. Methodology (II)
Steps
Changes in the
1.Select CMS requirements 9. CMS capable of
• Introduction managing accessible
and configuration
web pages
• CMS 2. Sample of NO
representative web pages
environments Any accessibility
problem detected?
• Evaluating NO CMS capable of
producing the YES
sample of web pages?
accessibility All possible CMS YES
YES configuration options
• Proposed have been explored?
3. ATAG evaluation
of the CMS with NO
Methodology current configuration
6. Analysis of the causes
• Case study 4. Develop the sample of accessibility errors
of web pages with current
• Discussion CMS configuration 7. Identify solutions for
detected accessibility errors
• Conclusions 5. WCAG analysis
of the sample of web
pages 8. Apply identified
solutions to the CMS
8. Case study
Step 1. Select CMS and configuration
• 2 CMS environments analyzed
• Introduction
• CMS
• With standard configuration
environments
• Evaluating
accessibility Version 7.5.1 4.5.2
Editor web FCK editor Rich Text Editor (RTE)
• Proposed
Template Template one Default template
Methodology
• Case study
• Set of 10 web pages in an academic
• Discussion
environment
• Conclusions
9. Case study
Step 2. Sample of representatives Web pages (I)
10 Web Pages Content elements HTML HTML Element
• Introduction description
All pages • Headers and paragraphs <H1> and <p>
• CMS 1 - Presentation • No extra elements --
2 - Center • Bold text format <strong>
environments • No extra elements
3 - Academic --
• Evaluating authorities
• Internal links <a> <a name>
accessibility 4 - Mural of the • Images <img>
study room • Ordered lists <ol> <li>
• Proposed
5 – Syllabus • Tables <table> <caption> <thead>
Methodology • Different text formats <tbody> <th> <td> <tr>
<center>,<strong>,<span
• Case study style=”color:
rgb(255,255,255)”>,<span
• Discussion style="background-color:
rgb(255, 255, 0);>
• Conclusions
10. Case study
Step 2. Sample of representatives Web pages (II)
10 Web Pages Content elements HTML Element
• Introduction HTML description
All pages • Headers and <H1> and <p>
• CMS paragraphs
6 - Departments • Externals links <a> <a target=”_blank”>
environments • Unordered list <ul> <li>
7 - Official • Externals links <a> <a target=”_blank”>
• Evaluating registration • Image link <a><img>
• Externals links <a> <a target=”_blank”>
accessibility 8 – News • Emphasized text <em>
format
• Proposed 9 - Contact • Bold text format <strong>
information • Address <address>
Methodology • Email links <a href=”mailto:...”>
• Case study 10 - Questions & • Form elements <label> <input> <select>
suggestions <option> <textarea>
Step
• Discussion
• Conclusions
11. Case study
Step 3. ATAG evaluation of the CMSs
• Quantitative results
• Introduction
• CMS
A AA A AA
environments Percentage of correct 25,00 % 42,86 % 37,50 % 42,86 %
checkpoints
• Evaluating More errors Less errors
accessibility • Concrete checkpoints errors
• Proposed Checkpoints
Errors A AA
Methodology
No errors in both CMSs 1.1, 7.2 4.3, 7.5, 7.6
• Case study
• Discussion Errors found in both CMS 1.2, 2.2, 3.4, 6.1, 7.3 2.1, 5.1, 5.2, 6.2
• Conclusions Errors only on OpenCMS No errors 7.4
Errors only on Typo3 No errors
12. Case study
Step 4. Develop the sample of web pages
• Create 10 representative web pages in
• Introduction
both CMS environments
• CMS
environments
• Evaluating
accessibility
• Proposed
Methodology
• Case study
• Discussion
• Conclusions
13. Case study
Step 5. WCAG 2.0 evaluation of the CMSs
• Checkpoints with errors in the
• Introduction
• CMS WCAG evaluation for every web page
Checkpoints
environments Errors A AA
1.3.1, 2.1.1, 2.4.4,
• Evaluating
3.3.2, 4.1.1 2.4.5,
Errors found in both CMS
accessibility User errors: 1.1.1, 3.3.4 (only page 10)
1.4.1, 2.4.2, 3.2.3
• Proposed Common errors on
3.1.1, 2.4.1 No errors
OpenCMS web pages
Methodology Errors on some web pages 1.3.3,
1.4.4 (only pages: 2,
5, 8 and 9),
on OpenCMS 3.3.1 (only page 10)
• Case study 3.3.3 (only page 10)
Common errors on Typo3
• Discussion No errors 1.4.4, 2.4.6
web pages
Errors on some web pages
• Conclusions No errors No errors
on Typo3
14. Case study
Step 6. Analysis of causes accessibility errors
Checkpoint
• Introduction Level A
1.3.1. Info and Relationships Template, CMS Template, CMS
• CMS 1.3.3. Sensory Characteristics CMS -
2.1.1. Keyboard Template CMS
environments Template -
2.4.1. Bypass Blocks
• Evaluating 2.4.4. Link Purpose (In Context) Template Template
3.1.1. Language of Page Template -
accessibility 3.3.1. Error Identification Template, CMS -
3.3.2. Labels or Instructions Template, CMS Template, CMS
• Proposed Template, HTML Template, HTML editor
4.1.1. Parsing
editor
Methodology
Level AA
• Case study 1.4.4. Resize text HTML editor HTML editor
2.4.5. Multiple Ways Template Template
• Discussion 2.4.6. Headings and Labels - Template
3.3.3. Error Suggestion CMS -
• Conclusions
3.3.4. Error Prevention CMS Template, CMS
Errors made by users are not included
15. Case study
Step 7. Identify solutions of accessibility errors
• One representative errors of each
• Introduction
detected cause
• CMS
Source of Error Checkpoint Solution
environments
Template 2.4.4: Link Purpose Modify template to include the
• Evaluating (In Context) title arribute for HTML tags
accessibility HTML Editor 1.4.4: Resize Text Modify HTML editor to
generate correct
• Proposed
CMS 1.3.1: Info and Modify configuration from
Methodology Relationships CMS
User 2.4.2 Page Titled Depends on user formation
• Case study
• Discussion
• Conclusions
16. Case study
Step 8. Apply solutions and ATAG re-evaluation
• Quantitative results of ATAG
• Introduction
evaluation of the final configuration
• CMS
environments A AA A AA
Percentage of correct
• Evaluating checkpoints (Before)
25,00 % 42,86 % 37,50 % 42,86 %
accessibility Percentage of correct
checkpoints (After) 37.50 % 57.14 % 62.50 % 57.14 %
• Proposed
• Changes on CMSs have improve
Methodology ATAG checkpoints:
• Case study • 2.2. The tool automatically generates valid markup
(Level A)
• Discussion
• 7.3. Allow the author to edit all properties of each
• Conclusions element and object in an accessible fashion (Level A)
• 2.1. Use the latest versions of W3C Recommendations
(Level AA)
17. Case study
Step 9. CMS capable of managing accessible web pages
• The CMS provides a proper
• Introduction
environment for users to manage
• CMS
accessible web pages (for the kind of
environments
web pages in the sample)
• Evaluating
• Developing accessible web pages will
accessibility
depend on the users that use the CMS
• Proposed
Methodology
• Case study
• Discussion
• Conclusions
18. Discussion (I)
Commons errors in both CMSs
• Accessibility errors in both CMSs have
• Introduction
similar causes:
• CMS
• Structure of the CMS
environments
• In general, CMSs systems work in a
• Evaluating
similar way
accessibility
• Causes and solutions provided in the
• Proposed
study are supposed to be helpful for
Methodology other CMSs as well
• Case study
• Discussion And
others…
• Conclusions
19. Discussion (II)
Improve the accessibility of both CMSs (I)
• Errors in HTML template
• Introduction
• Correct unclosed tags and substitute «&»
• CMS
for «&»
environments
• Add «lang» attribute to the <html> tag
• Evaluating
• Modify sequence of headers:
accessibility <h1><h2><h3>
• Proposed • Associate label for each data input
Methodology elements
• Case study • HTML editor has not considered
• Discussion some accessibility aspects
• Conclusions • Install module to improve or substitute
some tags generate for the HTML editor
20. Discussion (III)
Improve the accessibility of both CMSs (II)
• CMS does not provide proper
• Introduction
mechanisms to generate accessible
• CMS
code
environments
• Install modules to improve accessibility
• Evaluating
• Users can manage Web content in an
accessibility
incorrect way or without taking
• Proposed
accessibility aspects into account
Methodology
• Introduce correct titles for the pages
• Case study regarding the content they have
• Discussion • An appropriate alternative text must be
• Conclusions provided for images
• Tables with headers that identify cells
21. Discussion (IV)
Helpful recommendations for users
• Provide access to an accessibility
• Introduction
evaluation service
• CMS
• Accessibility evaluation services that
environments
work inside the HTML editors to check
• Evaluating
accessibility errors within the HTML
accessibility
editor
• Proposed
• Education about how to develop
Methodology
accessible web pages in a CMS Users
• Case study
environment
• Discussion
• Conclusions
22. Discussion (V)
Helpful recommendations for administrators
• Users or administrators must be aware of
• Introduction
accessibility
• CMS
• Not always the accessibility evaluation
environments
report is understood !!!
• Evaluating
accessibility
Accessibility
• Proposed Report
Methodology Users
Administrators
• Case study
• Discussion
• Conclusions
23. Conclusions
and future work
Conclusions:
• Introduction
•The methodology presented is applicable to
• CMS every CMS.
environments •It provides the necessary mechanisms:
• Evaluating • to ensure accessibility for a given set of
representative web pages
accessibility
• to analyze various types of elements
• Proposed
•It is necessary configure properly a CMS to
Methodology make accessible
• Case study
Future work:
• Discussion
•Analyze others technologies
• Conclusions • HTML5 and RIA
24. Any questions?
• Toni Granollers
tonig@diei.udl.cat
• Juan Miguel López
juanmiguel.lopez@ehu.es
• Afra Pascual
apascual@diei.udl.cat
• Cristina Menduiña
cmenduinya@alumnes.udl.cat
University of Lleida University of the Basque country
Editor's Notes
Methodology for identifying and solving accessibility related issues in Web Content Management System environments GRIHO is an Computer-Human Interaction and Data Integration Research Group University of Lleida University of the Basque country Speaker: Toni Granollers University of Lleida [email_address] Conference: 9th International Cross-Disciplinary Conference on Web Accessibility Lyon, 17 April 2012 http://www.w4a.info/2012/
Outline : Introduction CMS environments Evaluating accessibility Proposed Methodology Case study Discussion Conclusions
Introduction “ The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect”. Tim Berners-Lee Accessibility is a legal requirement that should be integrated into Web development methodologies Legislation about the fulfilment of accessibility requirements is currently in force in many countries around the world. For instance, Section 508 requires federal agencies in the United States to make their electronic and information technology accessible for people with disabilities. These kinds of legislative changes have also been made in more countries around the world, such as European Union countries. These legal frameworks not only affect public administrations, they also affect corporations that develop software or provide services for their use in civil service.
CMS environments In this context, it must be taken into account that there are a growing number of institutions that use Web Content Management Systems (CMS henceforth) to manage the Web content on their websites. These kinds of systems are especially useful as they can be used by users with no Web programming skills to introduce or modify Web content in the website. This approach has some risks regarding accessibility. On the one hand, CMS themselves may not provide appropriate support for developing accessible websites. On the other hand, including or modifying Web content by unskilled users may lead to a situation in which accessible websites can turn into non accessible.
Evaluating accessibility Evaluate Web content with WCAG Determine the scope of the evaluation Automatic evaluation Use at least two Web accessibility evaluation tools Validate markup (syntax and style) Manual revision by accessibility evaluator Evaluate CMS environment with ATAG But despite guidelines exist and the process to evaluate web accessibility is clear there are still accessibility errors!
Methodology – Properties Allows identifying and solving accessibility related issues in web pages using CMS environments Iterative Includes ATAG and WCAG Includes web content accessibility evaluation methodology proposed by the W3C Takes into account features specific to CMS environments
Methodology – Steps Step 1) CMS environments with standard configuration Step 2) Sample of representatives Web pages Step 3) ATAG 1.0 evaluation (Levels A and AA) Step 4) Create Web pages on both CMS environments Step 5) WCAG 2.0 evaluation (levels A and AA) of content web pages analysis of causes accessibility errors Step 6) analysis of causes accessibility errors. Source of errors: User management, template, HMTL editor, CMS) Step 7) Solutions to provide better accessibility Step 8) Application solutions on CMS environment Step 9) Result Oks of accessibility pages
Case study - Step 1. Select CMS and configuration Two different CMSs, OpenCMS (version 7.5.1) and Typo3 (version 4.5.2), have been employed in the case study, both a with default configuration. An HTML editor was used on the front end of each CMS to create the content page and the templates are resources on the back end of the CMS (like HTML pages) that are used to separate content from design. With OpenCMS, its default HTML editor (FCKEditor) was used. A template named “Template one” was selected among the different templates available on the default configuration of OpenCMS. Regarding Typo3, its default HTML editor (RTE) and the default template were used. Set of 10 web pages in an academic environment
Case study - Step 2. Sample of representatives Web pages (I) All pages - Headers and paragraphs 1 – Presentation - No extra elements 2 - Center - Bold text format 3 - Academic authorities - No extra elements 4 - Mural of the study room - Internal links, Images and Ordered lists 5 – Syllabus – Tables, Different text formats: text centred, bold, color font, color background.
Case study - Step 2. Sample of representatives Web pages (II) 6 – Departments - Externals links and Unordered list 7 - Official registration - Externals links and Image link 8 – News - Externals links and Emphasized text format 9 - Contact information - Bold text format, Address and Email links 10 - Questions & suggestions - Form elements
Case study - Step 3. ATAG evaluation of the CMSs Quantitative results - Percentage of correct checkpoints: OpenCMS: 25% (Level A) - 42,86% (Level AA) Typo3: 37,50 (Level A) - 42,86% (Level AA) Concrete checkpoints errors No errors in both CMSs Level A ( 1.1, 7.2 ) Level AA ( 4.3, 7.5, 7.6) Errors found in both CMS Level A ( 1.2, 2.2, 3.4, 6.1, 7.3) Level AA ( 2.1, 5.1, 5.2, 6.2) Errors only on OpenCMS Level A ( No errors) Level AA ( 7.4) Errors only on Typo3 Level A and Level AA ( No errors)
Case study - Step 4. Develop the sample of web pages Create 10 representative web pages in both CMS environments (OpenCMS and Typo3)
Case study - Step 5. WCAG 2.0 evaluation of the CMSs Checkpoints with errors in the WCAG evaluation for every web page Errors found in both CMS Level A ( 1.3.1, 2.1.1, 2.4.4, 3.3.2, 4.1.1. User errors: 1.1.1, 1.4.1, 2.4.2, 3.2.3) Level AA ( 2.4.5, 3.3.4 (only page 10)) Common errors on OpenCMS web pages Level A ( 3.1.1, 2.4.1) Level AA ( No errors) Errors on some web pages on OpenCMS Level A ( 1.3.3, 3.3.1 (only page 10)) Level AA ( 1.4.4 (only pages: 2, 5, 8 and 9), 3.3.3 (only page 10) Common errors on Typo3 web pages Level A ( No errors ) Level AA ( 1.4.4, 2.4.6) Errors on some web pages on Typo3 Level A ( No errors ) Level AA ( No errors)
Case study- Step 6. Analysis of causes accessibility errors Errors made by users are not included Level A 1.3.1. Info and Relationships - OpenCMS: Template, CMS - Typo3: Template, CMS 1.3.3. Sensory Characteristics – OpenCMS: CMS - Typo3: - 2.1.1. Keyboard - OpenCMS: Template - Typo3: CMS 2.4.1. Bypass Blocks - OpenCMS:Template - Typo3: - 2.4.4. Link Purpose (In Context) - OpenCMS:Template - Typo3: Template 3.1.1. Language of Page - OpenCMS: Template - Typo3: - 3.3.1. Error Identification - OpenCMS: Template, CMS - Typo3: - 3.3.2. Labels or Instructions - OpenCMS: Template, CMS - Typo3: Template, CMS 4.1.1. Parsing - OpenCMS: Template, HTML editor - Typo3: Template, HTML editor Level AA 1.4.4. Resize text - OpenCMS: HTML editor - Typo3: HTML editor 2.4.5. Multiple Ways - OpenCMS: Template - Typo3: Template 2.4.6. Headings and Labels - OpenCMS: - - Typo3: Template 3.3.3. Error Suggestion - OpenCMS: CMS- Typo3: - 3.3.4. Error Prevention - OpenCMS: CMS- Typo3: Template, CMS
Case study - Step 7. Identify solutions of accessibility errors One representative errors of each detected cause Source of Error: Template Checkpoint : 2.4.4: Link Purpose (In Context) Solution: Modify template to include the title arribute for HTML tags Source of Error: HTML Editor Checkpoint : 1.4.4: Resize Text Solution: Modify HTML editor to generate correct Source of Error: CMS Checkpoint : 1.3.1: Info and Relationships Solution: Modify configuration from CMS Source of Error: User Checkpoint : 2.4.2 Page Titled Solution: Depends on user formation
Case study - Step 8. Apply solutions and ATAG re-evaluation Quantitative results of ATAG evaluation of the final configuration Percentage of correct checkpoints ( Before ): OpenCMS: 25% (Level A) - 42,86% (Level AA) Typo3: 37,50 (Level A) - 42,86% (Level AA) Percentage of correct checkpoints ( After ): OpenCMS: 37,5% (Level A) - 57,14% (Level AA) Typo3: 62,50 (Level A) – 57,14% (Level AA) Changes on CMSs have improve ATAG checkpoints: 2.2. The tool automatically generates valid markup (Level A) 7.3. Allow the author to edit all properties of each element and object in an accessible fashion (Level A) 2.1. Use the latest versions of W3C Recommendations (Level AA)
Case study - Step 9. CMS capable of managing accessible web pages The CMS provides a proper environment for users to manage accessible web pages (for the kind of web pages in the sample) Developing accessible web pages will depend on the users that use the CMS
Discussion - Commons errors in both CMSs Accessibility errors in both CMSs have similar causes: Structure of the CMS In general, CMSs systems work in a similar way Causes and solutions provided in the study are supposed to be helpful for other CMSs as well OpenCMS and Typo3 and others CMSs. For instance: Drupal, Jahia, Xoops, Wordpress, Zope, Joomla!, Plone.
Discussion - Improve the accessibility of both CMSs (I) Errors in HTML template Correct unclosed tags and substitute «&» for «&amp» Add «lang» attribute to the <html> tag Modify sequence of headers: <h1><h2><h3> Associate label for each data input elements HTML editor has not considered some accessibility aspects Install module to improve or substitute some tags generate for the HTML editor
Discussion - Improve the accessibility of both CMSs (II) CMS does not provide proper mechanisms to generate accessible code: Install modules to improve accessibility Users can manage Web content in an incorrect way or without taking accessibility aspects into account: Introduce correct titles for the pages regarding the content they have An appropriate alternative text must be provided for images Tables with headers that identify cells
Discussion - Helpful recommendations for users Provide access to an accessibility evaluation service Accessibility evaluation services that work inside the HTML editors to check accessibility errors within the HTML editor Education about how to develop accessible web pages in a CMS environment
Discussion - Helpful recommendations for administrators Users or administrators must be aware of accessibility Not always the accessibility evaluation report is understood !!!
Conclusions and future work Conclusions: The methodology presented is applicable to every CMS. It p rovides the necessary mechanisms: to ensure accessibility for a given set of representative web pages to analyze various types of elements It is necessary configure properly a CMS to make accessible Future work : Analyze others technologies: HTML5 and RIA
Any questions? Authors: Toni Granollers tonig@diei.udl.cat (speaker) Juan Miguel López [email_address] Afra Pascual [email_address] Cristina Menduiña [email_address] GRIHO is an Computer-Human Interaction and Data Integration Research Group University of Lleida University of the Basque country