Section 508 Compliance Guide Now Available
You can now request a copy of the 'HOW TO PLAN FOR SECTION 508 COMPLIANCE SUPPORT' which will serve as an executive level guide to reach Section 508 compliance for
Table of Contents
HOW TO PLAN FOR SECTION 508 COMPLIANCE SUPPORT
Disclaimer
INTRODUCTION
INDUSTRY STANDARDS
SECTION 508 STANDARDS
TECHNICAL STANDARDS
RECOMMENDATIONS AND BEST PRACTICES FOR DEVELOPING ACCESSIBLE APPLICATIONS
COMMON MISCONCEPTIONS AND MYTHS ABOUT USABILITY
VALIDATION APPROACHES
ACCESSIBILITY STATEMENT
CHECKPOINTS
Priorities
Priority 1 checkpoints
Priority 2 checkpoints
Priority 3 checkpoints
COMMON JAVASCRIPT ISSUES
Issue 1: Document.write
Issue 2: Window.status
Issue 3: Cursor position
Issue 4: JavaScript pseudo protocol links
Issue 5: DoubleClick event handlers
Issue 6: Pop-up windows / automatic opened windows
Issue 7: Drag-and-drop features
Issue 8: Tickers
Issue 9: Auto refresh feature
Issue 10: Forms without submit buttons
Issue 11: Links created with JavaScript or pointing to a JavaScript function
Issue 12: Event handlers
Issue 13: Error Messages
SAMPLE PROCESS FLOW TO HELP REACH SECTION 508 COMPLIANCE
TEMPLATE FOR ACCESSIBILITY EVALUATION REPORTS
GLOSSARY
REFERENCES
Disclaimer
INTRODUCTION
INDUSTRY STANDARDS
SECTION 508 STANDARDS
TECHNICAL STANDARDS
RECOMMENDATIONS AND BEST PRACTICES FOR DEVELOPING ACCESSIBLE APPLICATIONS
COMMON MISCONCEPTIONS AND MYTHS ABOUT USABILITY
VALIDATION APPROACHES
ACCESSIBILITY STATEMENT
CHECKPOINTS
Priorities
Priority 1 checkpoints
Priority 2 checkpoints
Priority 3 checkpoints
COMMON JAVASCRIPT ISSUES
Issue 1: Document.write
Issue 2: Window.status
Issue 3: Cursor position
Issue 4: JavaScript pseudo protocol links
Issue 5: DoubleClick event handlers
Issue 6: Pop-up windows / automatic opened windows
Issue 7: Drag-and-drop features
Issue 8: Tickers
Issue 9: Auto refresh feature
Issue 10: Forms without submit buttons
Issue 11: Links created with JavaScript or pointing to a JavaScript function
Issue 12: Event handlers
Issue 13: Error Messages
SAMPLE PROCESS FLOW TO HELP REACH SECTION 508 COMPLIANCE
TEMPLATE FOR ACCESSIBILITY EVALUATION REPORTS
GLOSSARY
REFERENCES
Understand How Cognos 8 is Different From Cognos Series 7
Understand How Cognos 8 is Different From Cognos Series 7
We recommend that you become familiar with Cognos 8 before you develop a migration plan.
Cognos 8 is different from Cognos Series 7. You should not use migration as a tool to educate you
on Cognos 8. If you do, your migration may simply re-create the same application in Cognos 8,
without taking advantage of new features and functionality.
Cognos 8 is built on the proven and scalable Web services architecture introduced with Cognos
ReportNet. This architecture supports a truly unified product suite, and it is the basis for future
development efforts at Cognos. Compared with Cognos Series 7, business users work differently
with Cognos 8:
• A single product provides all business intelligence capabilities: reporting, analysis, scorecards,
dashboards, business event management, and data integration. Users chose the capabilities
they need.
• Because metadata is defined once, users have a complete and consistent view of corporate
data. Users do not have to go to different products or locations to see different data.
• Individual users can choose the tools and information they need. They do not have to learn
generic tools designed for highly technical users. This flexible business intelligence meets the
needs of a greater variety of roles in the organization.
In addition to understanding the high-level concepts and benefits of Cognos 8, you should
understand the differences in features between Cognos Series 7 and Cognos 8. A direct mapping
for some features does not exist between Cognos Series 7 and Cognos 8. For example, in
PowerPlay, you can apply 80/20 suppression to data. Analysis Studio does not include this option.
However, the top and bottom filtering options in Analysis Studio provide greater control for
suppressing data and allow you to achieve similar results to 80/20 suppression in PowerPlay.
Assess the Size and Complexity of Your Cognos Series 7 Application
We recommend that you complete a detailed assessment of your Cognos Series 7 applications
before migration. The size and complexity of your Cognos Series 7 applications are important
factors to consider when planning the migration. The total size of the applications has a
significant impact on the time required to complete the migration. You must understand the
complexity of your applications to set appropriate and accurate expectations for the migration. A
detailed assessment can take several weeks to complete for large applications.
You likely will not want to migrate Cognos Series 7 content that is rarely or never used. You can
use the auditing tools included with Cognos Series 7 to identify how often content is used. The
audits provide an objective view of the applications. Assessing and reducing the size of the
applications is a useful exercise even if you decide to not migrate. Do not rely only on user
feedback to determine which content is used.
The complexity of your applications determines how much work is required to refine the content
in Cognos 8. What proportion of the reports are basic list or crosstab reports? What proportion of
the reports use advanced features, such as drill-through to other applications, or complex
formatting? For some types of reports, a relatively minor amount of work is required to refine the
reports after migration. For more complex reports, you may want to recreate the content from
scratch, or make significant changes to migrated content, to take advantage of new features and
functionality in Cognos 8. Your experience with Cognos 8 will help you to understand
functionality mapping between Cognos Series 7 and Cognos 8 and to decide if Cognos 8 offers a
better alternative for achieving the same results.
Identify How Cognos 8 Adds Value to Your Cognos Series 7 Application
We recommend that you work with your users to identify essential Cognos 8 functionality that
was not available in Cognos Series 7.
After you learn about Cognos 8 and assess your Cognos Series 7 applications, you will realize that
you do not want to use migration to simply replicate your Cognos Series 7 applications in Cognos
8. You want to take advantage of the benefits of Cognos 8 while leveraging the investment you
have in Cognos Series 7 applications.
• List the critical features in Cognos Series 7 applications. Are these features available in
Cognos 8? Do the migration tools map the feature to Cognos 8, or do you have to re-create
the feature after migration? If direct mapping in Cognos 8 does not exist, can you achieve
similar results in a different way in Cognos 8?
• List the essential Cognos 8 features that were unavailable in Cognos Series 7. Can you add
these features as enhancements to a migrated report? Should you create new reports that use
the features?
By comparing and listing important features with your users, you can start to identify which
Cognos Series 7 content is a good candidate for migration. You should migrate content if most
features map from Cognos Series 7 to Cognos 8, if the migration tools preserve all or most of the
feature, and if you find it easier to enhance the migrated report with Cognos 8 features than to
re-create the report.
We recommend that you become familiar with Cognos 8 before you develop a migration plan.
Cognos 8 is different from Cognos Series 7. You should not use migration as a tool to educate you
on Cognos 8. If you do, your migration may simply re-create the same application in Cognos 8,
without taking advantage of new features and functionality.
Cognos 8 is built on the proven and scalable Web services architecture introduced with Cognos
ReportNet. This architecture supports a truly unified product suite, and it is the basis for future
development efforts at Cognos. Compared with Cognos Series 7, business users work differently
with Cognos 8:
• A single product provides all business intelligence capabilities: reporting, analysis, scorecards,
dashboards, business event management, and data integration. Users chose the capabilities
they need.
• Because metadata is defined once, users have a complete and consistent view of corporate
data. Users do not have to go to different products or locations to see different data.
• Individual users can choose the tools and information they need. They do not have to learn
generic tools designed for highly technical users. This flexible business intelligence meets the
needs of a greater variety of roles in the organization.
In addition to understanding the high-level concepts and benefits of Cognos 8, you should
understand the differences in features between Cognos Series 7 and Cognos 8. A direct mapping
for some features does not exist between Cognos Series 7 and Cognos 8. For example, in
PowerPlay, you can apply 80/20 suppression to data. Analysis Studio does not include this option.
However, the top and bottom filtering options in Analysis Studio provide greater control for
suppressing data and allow you to achieve similar results to 80/20 suppression in PowerPlay.
Assess the Size and Complexity of Your Cognos Series 7 Application
We recommend that you complete a detailed assessment of your Cognos Series 7 applications
before migration. The size and complexity of your Cognos Series 7 applications are important
factors to consider when planning the migration. The total size of the applications has a
significant impact on the time required to complete the migration. You must understand the
complexity of your applications to set appropriate and accurate expectations for the migration. A
detailed assessment can take several weeks to complete for large applications.
You likely will not want to migrate Cognos Series 7 content that is rarely or never used. You can
use the auditing tools included with Cognos Series 7 to identify how often content is used. The
audits provide an objective view of the applications. Assessing and reducing the size of the
applications is a useful exercise even if you decide to not migrate. Do not rely only on user
feedback to determine which content is used.
The complexity of your applications determines how much work is required to refine the content
in Cognos 8. What proportion of the reports are basic list or crosstab reports? What proportion of
the reports use advanced features, such as drill-through to other applications, or complex
formatting? For some types of reports, a relatively minor amount of work is required to refine the
reports after migration. For more complex reports, you may want to recreate the content from
scratch, or make significant changes to migrated content, to take advantage of new features and
functionality in Cognos 8. Your experience with Cognos 8 will help you to understand
functionality mapping between Cognos Series 7 and Cognos 8 and to decide if Cognos 8 offers a
better alternative for achieving the same results.
Identify How Cognos 8 Adds Value to Your Cognos Series 7 Application
We recommend that you work with your users to identify essential Cognos 8 functionality that
was not available in Cognos Series 7.
After you learn about Cognos 8 and assess your Cognos Series 7 applications, you will realize that
you do not want to use migration to simply replicate your Cognos Series 7 applications in Cognos
8. You want to take advantage of the benefits of Cognos 8 while leveraging the investment you
have in Cognos Series 7 applications.
• List the critical features in Cognos Series 7 applications. Are these features available in
Cognos 8? Do the migration tools map the feature to Cognos 8, or do you have to re-create
the feature after migration? If direct mapping in Cognos 8 does not exist, can you achieve
similar results in a different way in Cognos 8?
• List the essential Cognos 8 features that were unavailable in Cognos Series 7. Can you add
these features as enhancements to a migrated report? Should you create new reports that use
the features?
By comparing and listing important features with your users, you can start to identify which
Cognos Series 7 content is a good candidate for migration. You should migrate content if most
features map from Cognos Series 7 to Cognos 8, if the migration tools preserve all or most of the
feature, and if you find it easier to enhance the migrated report with Cognos 8 features than to
re-create the report.
What to Expect When You Move Content from Cognos Series 7 to Cognos 8
Because of differences in product architecture and functionality, it is not possible to simply reuse
Cognos Series 7 metadata or applications in Cognos 8. Cognos provides migration and upgrade
tools to help you take advantage of investments you have made in Cognos Series 7. However, to
successfully move to Cognos 8, in addition to using the migration and upgrade tools, there is
additional work required to prepare for the migration, and to test and refine the migrated content
in Cognos 8.
As part of the migration planning process, we recommend that you move a subset of your
Cognos Series 7 content and then assess the results and the amount of work required to refine the
content in Cognos 8. Sometimes only minor updates, such as formatting changes, are required in
Cognos 8. In other cases you may find that a Cognos Series 7 feature that is important to you is
not available in Cognos 8.
Understand How Cognos 8 is Different From Cognos Series 7
Understand How Cognos 8 is Different From Cognos Series 7
We recommend that you become familiar with Cognos 8 before you develop a migration plan.
Cognos 8 is different from Cognos Series 7. You should not use migration as a tool to educate you
on Cognos 8. If you do, your migration may simply re-create the same application in Cognos 8,
without taking advantage of new features and functionality.
Cognos 8 is built on the proven and scalable Web services architecture introduced with Cognos
ReportNet. This architecture supports a truly unified product suite, and it is the basis for future
development efforts at Cognos. Compared with Cognos Series 7, business users work differently
with Cognos 8:
• A single product provides all business intelligence capabilities: reporting, analysis, scorecards,
dashboards, business event management, and data integration. Users chose the capabilities
they need.
• Because metadata is defined once, users have a complete and consistent view of corporate
data. Users do not have to go to different products or locations to see different data.
• Individual users can choose the tools and information they need. They do not have to learn
generic tools designed for highly technical users. This flexible business intelligence meets the
needs of a greater variety of roles in the organization.
In addition to understanding the high-level concepts and benefits of Cognos 8, you should
understand the differences in features between Cognos Series 7 and Cognos 8. A direct mapping
for some features does not exist between Cognos Series 7 and Cognos 8. For example, in
PowerPlay, you can apply 80/20 suppression to data. Analysis Studio does not include this option.
However, the top and bottom filtering options in Analysis Studio provide greater control for
suppressing data and allow you to achieve similar results to 80/20 suppression in PowerPlay.
Assess the Size and Complexity of Your Cognos Series 7 Application
We recommend that you complete a detailed assessment of your Cognos Series 7 applications
before migration. The size and complexity of your Cognos Series 7 applications are important
factors to consider when planning the migration. The total size of the applications has a
significant impact on the time required to complete the migration. You must understand the
complexity of your applications to set appropriate and accurate expectations for the migration. A
detailed assessment can take several weeks to complete for large applications.
You likely will not want to migrate Cognos Series 7 content that is rarely or never used. You can
use the auditing tools included with Cognos Series 7 to identify how often content is used. The
audits provide an objective view of the applications. Assessing and reducing the size of the
applications is a useful exercise even if you decide to not migrate. Do not rely only on user
feedback to determine which content is used.
The complexity of your applications determines how much work is required to refine the content
in Cognos 8. What proportion of the reports are basic list or crosstab reports? What proportion of
the reports use advanced features, such as drill-through to other applications, or complex
formatting? For some types of reports, a relatively minor amount of work is required to refine the
reports after migration. For more complex reports, you may want to recreate the content from
scratch, or make significant changes to migrated content, to take advantage of new features and
functionality in Cognos 8. Your experience with Cognos 8 will help you to understand
functionality mapping between Cognos Series 7 and Cognos 8 and to decide if Cognos 8 offers a
better alternative for achieving the same results.
Identify How Cognos 8 Adds Value to Your Cognos Series 7 Application
We recommend that you work with your users to identify essential Cognos 8 functionality that
was not available in Cognos Series 7.
After you learn about Cognos 8 and assess your Cognos Series 7 applications, you will realize that
you do not want to use migration to simply replicate your Cognos Series 7 applications in Cognos
8. You want to take advantage of the benefits of Cognos 8 while leveraging the investment you
have in Cognos Series 7 applications.
• List the critical features in Cognos Series 7 applications. Are these features available in
Cognos 8? Do the migration tools map the feature to Cognos 8, or do you have to re-create
the feature after migration? If direct mapping in Cognos 8 does not exist, can you achieve
similar results in a different way in Cognos 8?
• List the essential Cognos 8 features that were unavailable in Cognos Series 7. Can you add
these features as enhancements to a migrated report? Should you create new reports that use
the features?
By comparing and listing important features with your users, you can start to identify which
Cognos Series 7 content is a good candidate for migration. You should migrate content if most
features map from Cognos Series 7 to Cognos 8, if the migration tools preserve all or most of the
feature, and if you find it easier to enhance the migrated report with Cognos 8 features than to
re-create the report.
--
BI CENTRE
http://bicentre.blogspot.com
We recommend that you become familiar with Cognos 8 before you develop a migration plan.
Cognos 8 is different from Cognos Series 7. You should not use migration as a tool to educate you
on Cognos 8. If you do, your migration may simply re-create the same application in Cognos 8,
without taking advantage of new features and functionality.
Cognos 8 is built on the proven and scalable Web services architecture introduced with Cognos
ReportNet. This architecture supports a truly unified product suite, and it is the basis for future
development efforts at Cognos. Compared with Cognos Series 7, business users work differently
with Cognos 8:
• A single product provides all business intelligence capabilities: reporting, analysis, scorecards,
dashboards, business event management, and data integration. Users chose the capabilities
they need.
• Because metadata is defined once, users have a complete and consistent view of corporate
data. Users do not have to go to different products or locations to see different data.
• Individual users can choose the tools and information they need. They do not have to learn
generic tools designed for highly technical users. This flexible business intelligence meets the
needs of a greater variety of roles in the organization.
In addition to understanding the high-level concepts and benefits of Cognos 8, you should
understand the differences in features between Cognos Series 7 and Cognos 8. A direct mapping
for some features does not exist between Cognos Series 7 and Cognos 8. For example, in
PowerPlay, you can apply 80/20 suppression to data. Analysis Studio does not include this option.
However, the top and bottom filtering options in Analysis Studio provide greater control for
suppressing data and allow you to achieve similar results to 80/20 suppression in PowerPlay.
Assess the Size and Complexity of Your Cognos Series 7 Application
We recommend that you complete a detailed assessment of your Cognos Series 7 applications
before migration. The size and complexity of your Cognos Series 7 applications are important
factors to consider when planning the migration. The total size of the applications has a
significant impact on the time required to complete the migration. You must understand the
complexity of your applications to set appropriate and accurate expectations for the migration. A
detailed assessment can take several weeks to complete for large applications.
You likely will not want to migrate Cognos Series 7 content that is rarely or never used. You can
use the auditing tools included with Cognos Series 7 to identify how often content is used. The
audits provide an objective view of the applications. Assessing and reducing the size of the
applications is a useful exercise even if you decide to not migrate. Do not rely only on user
feedback to determine which content is used.
The complexity of your applications determines how much work is required to refine the content
in Cognos 8. What proportion of the reports are basic list or crosstab reports? What proportion of
the reports use advanced features, such as drill-through to other applications, or complex
formatting? For some types of reports, a relatively minor amount of work is required to refine the
reports after migration. For more complex reports, you may want to recreate the content from
scratch, or make significant changes to migrated content, to take advantage of new features and
functionality in Cognos 8. Your experience with Cognos 8 will help you to understand
functionality mapping between Cognos Series 7 and Cognos 8 and to decide if Cognos 8 offers a
better alternative for achieving the same results.
Identify How Cognos 8 Adds Value to Your Cognos Series 7 Application
We recommend that you work with your users to identify essential Cognos 8 functionality that
was not available in Cognos Series 7.
After you learn about Cognos 8 and assess your Cognos Series 7 applications, you will realize that
you do not want to use migration to simply replicate your Cognos Series 7 applications in Cognos
8. You want to take advantage of the benefits of Cognos 8 while leveraging the investment you
have in Cognos Series 7 applications.
• List the critical features in Cognos Series 7 applications. Are these features available in
Cognos 8? Do the migration tools map the feature to Cognos 8, or do you have to re-create
the feature after migration? If direct mapping in Cognos 8 does not exist, can you achieve
similar results in a different way in Cognos 8?
• List the essential Cognos 8 features that were unavailable in Cognos Series 7. Can you add
these features as enhancements to a migrated report? Should you create new reports that use
the features?
By comparing and listing important features with your users, you can start to identify which
Cognos Series 7 content is a good candidate for migration. You should migrate content if most
features map from Cognos Series 7 to Cognos 8, if the migration tools preserve all or most of the
feature, and if you find it easier to enhance the migrated report with Cognos 8 features than to
re-create the report.
--
BI CENTRE
http://bicentre.blogspot.com
What to Expect When You Move Content from Cognos Series 7 to Cognos 8
Because of differences in product architecture and functionality, it is not possible to simply reuse
Cognos Series 7 metadata or applications in Cognos 8. Cognos provides migration and upgrade
tools to help you take advantage of investments you have made in Cognos Series 7. However, to
successfully move to Cognos 8, in addition to using the migration and upgrade tools, there is
additional work required to prepare for the migration, and to test and refine the migrated content
in Cognos 8.
As part of the migration planning process, we recommend that you move a subset of your
Cognos Series 7 content and then assess the results and the amount of work required to refine the
content in Cognos 8. Sometimes only minor updates, such as formatting changes, are required in
Cognos 8. In other cases you may find that a Cognos Series 7 feature that is important to you is
not available in Cognos 8.
--
BI CENTRE
http://bicentre.blogspot.com
Cognos Series 7 metadata or applications in Cognos 8. Cognos provides migration and upgrade
tools to help you take advantage of investments you have made in Cognos Series 7. However, to
successfully move to Cognos 8, in addition to using the migration and upgrade tools, there is
additional work required to prepare for the migration, and to test and refine the migrated content
in Cognos 8.
As part of the migration planning process, we recommend that you move a subset of your
Cognos Series 7 content and then assess the results and the amount of work required to refine the
content in Cognos 8. Sometimes only minor updates, such as formatting changes, are required in
Cognos 8. In other cases you may find that a Cognos Series 7 feature that is important to you is
not available in Cognos 8.
--
BI CENTRE
http://bicentre.blogspot.com
Subscribe to:
Posts (Atom)